What is our primary use case?
There were two systems that the client was looking at creating some BI visualizations for. There was the system called ICE, which is a system that takes in automated calls, for service calls. They go into voicemail, however, if there's not an agent to take the call, it'll track statistics like how long a client was on hold, if an agent actually took the call, if the person hung up, et cetera. There are all of these different statuses and it would take all of those statistics. The product was used primarily to take that data in that case.
The other system was an ITSM system, which was the ticketing system. It would
it was my first time using Power BI, I can say that it was fairly easy to learn, especially if you already know BI-type tools. But the one thing that I noticed specifically was the graphical features, and some of the analytical features, I think they were stronger on the Tableau side. But the data preparation features, I much preferred the Power BI with the Power Query type features, at least for the datasets that we were working with. They were helpful in preparing the data.
combine those two data sets and reduce a merged analytical set of reports to just show when the call volumes were and what the performance rate was and the nature of the calls and things like that.
What is most valuable?
As it was my first time using Power BI, I can say that it was fairly easy to learn, especially if you already know BI-type tools.
The data preparation features were great. I much preferred the Power BI with the Power Query type features - at least for the datasets that we were working with. They were helpful in preparing the data.
What needs improvement?
The one thing that I noticed specifically was the graphical features, and some of the analytical features. They were stronger on the Tableau side.
There are two areas where the solution can be enhanced. One is natural language, where you can have third parties, however, it would be nice to have it built-in within Power BI, where a graph could be automatically explained in whatever language so that somebody can just kind of read through and have the graphic as an extra for exploring. That's something that I was looking at.
The other is the explained data, which is more of a lineage-type feature. My understanding is Tableau has that feature and Power BI doesn't. I was looking at a graph of comparisons and I noticed Tableau had this explained data feature, which gives, some lineage where data has come from, and Power BI doesn't have that. Or, if it does, it's not as well developed as Tableau.
For how long have I used the solution?
I used the solution a few months ago. I'm semi-retired, however, I did have a two-month contract and did some work with it. On the project, I did work a lot with Tableau, however, I also used Power BI, and would like to continue to use it more.
Buyer's Guide
Microsoft Power BI
June 2025
Learn what your peers think about Microsoft Power BI. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
861,524 professionals have used our research since 2012.
What do I think about the stability of the solution?
It was a short project on the Power BI side. I didn't really identify any glitches. Certainly, over time things might've come out, however, I enjoy doing experimenting and playing around with things. The one definite thing that I noticed, as I do art with Tableau, is some really neat art stuff, so I tried to replicate that with Power BI and the quality just wasn't there.
What do I think about the scalability of the solution?
With ITSM, there's a lot of data that they collect on that side. That could be an issue, scalability. It wasn't moved to production yet. I basically produced a report as there were some issues with the ICE data, the voicemail system, and data collection. They had some issues that they had to solve. However, they were collecting data on a daily basis. You get thousands and thousands of calls on a daily basis. It depends on how they want to store that data historically. There may be some performance issues and scalability issues, however, for me, I can't really address that, as I didn't see that side. There's always a potential for trouble.
How are customer service and support?
It was a really short project for me. I was really there just to analyze those two data sources and produce a report for them, with some examples, using Power BI. I was able to do that without getting tech support involved.
Which solution did I use previously and why did I switch?
I've used other solutions, such as Tableau and Power Query. Tableau from a graphical point of view is much better than Power BI, however, from a data manipulation standpoint and things like that, I prefer Power BI and Power Query to prep the data.
Tableau got bought out by Salesforce, which is a cloud-based company, so they're all going to push everything to the cloud. I'm sure they'll incorporate all these new features.
How was the initial setup?
I downloaded the solution from their website.
The server side was already set up, therefore, I don't know much about the initial setup process. As a contractor, I came in just on the development side, which was just downloading the Power BI tool as a client. It was fairly easy. That's the nice thing is it's easy to set up. It is similar to Tableau, in that Tableau is fairly easy to set up. It is all built towards this whole idea of self-service.
What other advice do I have?
I'm just a customer.
As I downloaded the solution right off the website, I assume it was the latest version. I don't know the version number off-hand.
I would do the development on-pre
There were two systems that they were looking at creating some BI visualizations for. So there was the system called ICE, which is a system that takes in automated calls, for service calls. And so goes into voicemail, but if there's not an agent to take the call, it'll track statistics like how long you were on hold, if an agent actually took your call, if you hung up. All of these different statuses would take all of those statistics. And so it was to take that data.
And the other system was the ITSM system, which is the ticketing system. And kind of combine those two data sets and reduce a merged analytical set of reports to just show when were the call volumes were, and what was the performance rate, and the nature of the calls and things like that.
It's easy to set up, however, regarding scalability and high-end analytical features, Tableau is still better on that. It's always important to keep up, as technology's changing all the time. They're always adding new features. There are no negatives in exploring these tools. In the end, you just want some visualizations that help you make decisions. Both Tableau and Power BI tools are great for that. However, if you want advanced stuff, then it's just about experimenting and seeing what will help you solve your problems.
I'd rate the solution at an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.