Did you catch our recent webinar with Ian Richardson of Doberman Technologies where he discusses how he uses BrightGauge to set his MSP up for success? During the chat, Ian shared that one of his ...
Did you catch our recent webinar with Ian Richardson of Doberman Technologies where he discusses how he uses BrightGauge to set his MSP up for success? During the chat, Ian shared that one of his go-to dashboards is one that tracks his team’s capacity for new projects. The dashboard shows the capacity each tech has in his or her schedule to take on projects, based on hours that have been scheduled for the current month and the next 3 months. Each tech has a predetermined max capacity, which is based on work roles. View this dashboard here. This critical dashboard is used for expectation management, both internally and with clients. It helps the Doberman Technologies teams make informed decisions about when projects can realistically be delivered and it helps them decide which projects to take on and when. Scheduling projects around known capacities also ensures that each team member has enough time for unexpected crisis items and for more long-term projects. For Doberman Technologies, this has been a really efficient way to grow their business and keep workload at a manageable pace and it's applicable to all teams across the board. Many of you showed interest in replicating this dashboard for yourselves, and we’re happy to share it with you now: Link to Team Capacity Dashboard Link to Dashboard Recreation Key Please feel free to reach out to success@brightgauge.com with any questions you have!
Within your organization, are there multiple departments, each housing multiple teams? How are you organizing your BrightGauge dashboards, reports, and gauges so that team members can easily find their respective data? Even with smaller organizations, implementing a proper naming convention to be used throughout BrightGauge can lead to quicker access and easier navigation of your data (think cluttered vs. uncluttered workspaces). In this edition of our user showcase webinars, Daniel Pop, Application Support Manager at Milner, Inc., shares his approach to a cohesive naming system within BrightGauge and talks about how staying organized feeds into managing teams, providing feedback, and monitoring who is under- or over-achieving. This clever, yet simple way to organize data has proven effective for Daniel and teams and has allowed them to seamlessly use every aspect of BrightGauge in their day-to-day. Click below to watch the webinar and if you've got questions, please don't hesitate to contact us!
Undoubtedly, one of the most important areas of business any owner or manager wants to keep an eye on is financial performance. Simply put, you need to know the status of your cash flow, revenue, expenses, and more at any given moment. Any executive or leadership team will look to view and analyze these kinds of metrics on a regular basis, to drive business decisions and forecast performance. So, when building a financial overview or leadership KPI dashboard, what are the key metrics you are choosing to display? There are some key performance indicators that will resonate across the board, but others may be specific to your organization. To help shed some light, and maybe some inspiration, we spoke to BrightGauge customer Dan Lattuada of Pinnacle Technology Partners to learn what their Leadership KPI Dashboard looks like. The following is a recreation of the dashboard they use: View this dashboard here. For Dan and PTP, it's important to see how the company is doing financially on a trailing 12-month basis to ensure that they are heading in the desired direction. To accomplish this, their BrightGauge dashboard is designed to look at specific areas of their business, such as sales, product, and managed services. For example, when it comes to sales, they want to make sure their commissions are in line with company performance. The most critical metric on their dashboard is their recurring revenue, which is the bread and butter of the PTP business. "We look at recurring revenue as our main KPI because, in any given month, we want to see that trending upwards," says Dan. "We're in the habit of optimizing the services our clients are consuming, but we want to make sure we are doing it in a way that makes sense for our overall business." Within BrightGauge, Dan builds his gauges with multiple layers to return that recurring information. He cautions that in order to do that, you need to organize yourself within Quickbooks (or other financial tool) first. When possible, gauges have thresholds set to them, which Dan sets based on a combination of where they think their business should be and past performance. So just how often is Dan using this leadership dashboard? Along with his accounting manager, he's looking at it on a daily basis. Given that this dashboard is meant to inform upper management on company performance, they share their metrics with the leadership team on a quarterly cadence. Interested in setting up a Leadership KPI dashboard like this for your business? Check out our Dashboard Key to recreate it yourself or feel free to reach out to success@brightgauge.com and we’ll be happy to help. Thank you to Dan and PTP for sharing your insights! Link to Public Dashboard Link to Dashboard Recreation Key
We’re excited to welcome Katarina Ondrejovicova to the team as a Customer Success Specialist! Join us in learning more about the newest member of our growing BrightGauge family… In the beginning Katarina is the first BrightGauger to come to us from Europe - she was born and raised in the country of Slovakia. Katarina graduated from Masaryk University in Brno, Czech Republic, which is the second largest city after Prague and is widely known for Moto GP. While in university, Katarina was lucky enough to study abroad in southern Spain, which helped to fuel her love of travel. She started off her career working for IBM, where she was tasked with improving the overall service level quality for their Sony account. About 5 years ago, Katarina moved to the US and worked for Itopia, a software company that partnered with Google Cloud to create a cloud automation tool for remote desktop provisioning and management. There, she was in charge of Customer Success and managing the support team. With that great experience, we were lucky to find Katarina and welcome her to BrightGauge. Joining BrightGauge Katarina was first intrigued by our software itself. Plus, in her words, “the company culture that respects individuality, promotes a stress free environment, and supports collaboration” helped to seal the deal. She’s really motivated to be part of the Customer Success team, especially because in her role she will work with both customers and internal teams like sales, support, marketing, and product. She’s excited about working across the board to improve our customer experience. We can’t wait to see what Katarina brings to the table. Out of office When Katarina has the time, she loves to travel and explore new places and cultures. Her love of photography means that her travels are well-documented, thanks to her Sony Alpha camera. Katarina strives to keep a zen state of mind through yoga, meditation, biking, and beach time. And she’s always down for some live music. Fun fact: Katarina speaks Slovak, Czech, English, and Spanish! What will she learn next?
When it comes to your key performance indicators, sometimes more is more. The deeper the insights, the better the decisions you can make. So, how can you get deeper insights from your BrightGauge? One way is to use dataset or datasource mashup*, which allows you to build gauges using data from more than one source. When doing this, the metrics that are displayed back to you are more complex and more granular, allowing you to be a bit more specific with your results. In this tutorial video, we show you how to utilize the data mashup function. If you have questions about doing this within your BrightGauge, please reach out to our support team. For more tutorial videos, check us out on YouTube. *Available on Enterprise Plans only.
70+ Metrics for MSPs
Key metrics and accompanying formulas to help MSPs skyrocket growth and success!
Get your KPIs
We frequently get asked how to choose the right metrics to report on, whether for client reports or internal ones. Ideally, any report you send out will be easily consumable yet impactful, so you want to be careful not to weigh it down with way too many metrics. Go for metrics that are direct and that clearly get your message across. When it comes to BrightGauge, a lot of our customers tell us how useful it is to see how their peers are using the app, so this month we’re highlighting Weston Technology Solutions’ internal Agreement Performance Report. Weston Tech has been in business for over 25 years and at the core of their managed IT solutions is a passion for being a true partner - not just a vendor - to their clients. Brock McFarlane, CEO and Founder of Weston, shared that their team works off of fixed-fee agreements, a departure from the hourly agreements they previously used. For Weston, fixed-fee contracts allow team members to be more valuable and efficient with time, but reporting on these contracts can get tricky since it’s not based on hour-by-hour work. What Brock has found is that looking at Gross Margin is a truer representation of how a contract is doing versus just how many hours were billed. Identifying their most important metric - Gross Margin - laid the foundation for how Brock and team would build reports moving forward. Brock also includes Hours by Tech within the reports, as any red flags in those hours can paint a picture as to why a margin percentage may be too low or too high. Reporting on a client’s margin percentage can pinpoint where inefficiencies lie - perhaps a tool a client is using is giving more trouble than it’s worth - so that they can operate at an optimal level. Also, by managing Gross Margin, Brock is sometimes able to avoid raising contract prices in the future, which his clients love and is a big reason why they repeatedly invest in Weston. This is a perfect example as to why consistent reporting is hugely important. We’ve recreated Weston’s Agreement Performance Report for your reference: Think this report would be useful for your team or want some more info? Check out our Report Key to recreate it yourself or feel free to reach out to success@brightgauge.com and we’ll be happy to help. Thank you to Brock and Weston Tech for sharing your insights! Link to Public Report Link to Report Recreation Key
In the last few months, we’ve added several new datasources to our stack, and here’s what you need to know! Now available to our customers: Liongard Roar, Solarwinds N-Central (previously N-Able), Simplesat, and PRTG. Keep reading for details on these integrations, which you can connect to at any time. Liongard Roar Liongard Roar is a documentation system that was specifically built for MSPs. Having important docs and processes documented is great for establishing accountability and understanding what actions took place when. For customers using Liongard Roar, integrating with BrightGauge provides a lot of flexibility in terms of the metrics and KPIs you can pull. There are several datasets customers can report on, including users, environments, agents, detections, timeline, and metrics. Within the metrics dataset, users can easily create custom metrics and report on Office 365 and Active Directory data. Lots of you have been asking for this, so we’re thrilled to make it available. The Liongard Roar integration comes with 56 default KPIs, two pre-built dashboards, and two report templates, conveniently categorized by Office 365 or Active Directory. To add Liongard Roar to your account, please follow the steps outlined in our support document. Solarwinds N-Central Formerly known as N-Able, we’re happy to report that Solarwinds N-Central is live. This RMM platform allows users to keep an eye on pertinent machine metrics. Paired with BrightGauge, users get real-time visibility into those metrics and are alerted to issues before they become any bigger. Plus, customizable, automated reports help customers prove their value to clients and show why they are trusted partners. Customers using the N-Central integration in BrightGauge are going to get 83 default KPIs right off the bat, pertaining to Devices, Servers, and Workstations. The integration also comes with 2 pre-built Machine Monitoring dashboards, and 2 Machine Monitoring report templates. This support doc guides you through the quick process of adding N-Central to your BrightGauge. Simplesat We’re excited to introduce yet another CSAT tool to our stack, as CSAT is at the forefront of metrics that business owners want to stay on top of. Simplesat was designed for small to medium sized MSPs and tech companies, and is a simple way to embed CSAT surveys into email signatures or helpdesks. Integrating BrightGauge + Simplesat allows you to see customer information, specifically how they rated, scored, and answered Simplesat questions. The ever important Net Promoter Score (NPS) is one of 19 default KPIs that are automatically included in this integration. There are also 2 built-out dashboards and reports each, one for CSAT scores and one for NPS. Follow these steps to add Simplesat to your BrightGauge account. PRTG Finally, we recently rolled out an integration with PRTG, a network monitoring tool. When you connect it with BrightGauge, you can easily keep track of metrics like sensor data, stale tickets, uptime, and active/inactive devices. The PRTG + BrightGauge integration comes with 27 default KPIs, one pre-built dashboard, and one report template. The kind of visibility you get with BrightGauge + PRTG allows you to stay proactive and keep the networks you monitor up and running. Adding this datasource to your account is easy - just follow these quick steps. For questions about any of our datasources or to chat with somebody about your BrightGauge account, contact us today. We’re always happy to talk shop!
We’re excited to welcome Jorge Rusiel to the team as a Senior Software Developer! Join us in learning more about the newest member of our growing BrightGauge family… In the beginning While so many members of our BrightGauge family hail from these South Florida parts, Jorge was born a bit further south. In Cuba, to be exact! He comes from Santiago de Cuba, which is the second largest city in the country. Jorge earned his Bachelor’s degree in Computer Science from Central University Marta Abreu de Las Villas in Cuba before jumping on the opportunity to move to Spain and obtain his Ph.D. from the Department of Computer Science & Artificial Intelligence at the University of the Basque Country. His Ph.D. research included the application of advanced image processing and statistical methods to computer-generated 3D models of the brain. Taking this research, Jorge moved to Boston, Massachusetts to work as a Postdoctoral Research Fellow at the Department of Radiology at Mass General Hospital/Harvard Medical School. His work included the development of an open source library used in longitudinal data analysis. Most recently, he worked as a Software Engineer - his true passion - at the Department of Radiology at Boston Children’s Hospital/Harvard Medical School, where he was the lead engineer in the design and development of an important scientific software platform. Fortunately for us, Jorge has brought his incredible wealth of knowledge to BrightGauge. Joining BrightGauge Jorge feels that BrightGauge will have a number of exciting technical challenges in the years to come and looking forward to being on the forefront of it all, whether this means integrating AI into the product or simply improving the software platform architecture. Our BrightGauge culture is just the cherry on top. “I’m excited to use my broad background to scale BrightGauge’s SaaS platform,” says Jorge. “This includes designing and implementing new REST APIs, writing high quality software that improves the existing platform, and implementing optimized workflows.” We’re confident that with Jorge on our team, the future of our product is very bright (pun intended). Out of office When Jorge isn’t living out his passion as an engineer, he’s spending time with family and friends by going running, salsa dancing, hitting the beach, and playing brain-intensive card games. Welcome to the fam, Jorge!
As an Account Executive at BrightGauge, I speak with dozens of potential and current customers each month. Each MSP comes from a different background, with varying goals and needs, but one universal struggle I hear is the need to show better value to customers. One of the paradoxes of the MSP world is that customers rarely need to see you when systems are running smoothly. When clients don’t hear much from you because things are working correctly, they might assume you aren’t delivering value. How can you solve this? One obvious way is through regular, automated reports, which is one of the main reasons companies hire BrightGauge. This may satisfy most customers, but there are still those for whom this will not provide enough insight into why they’re paying thousands of dollars each month for your services. For the clients that crave more up to the minute information, our Customer Facing Dashboards are a great solution. There are two main ways you can create live Dashboards for your customers - Add your client to your BrightGauge instance as a Viewer or utilize our new Public Dashboards. The first thing I would do in either circumstance is determine what metrics or KPIs you’d like your client to be able to access at any given time. Add the metrics you choose to a new dashboard Use the dashboard filtering option to filter down to that client. Clone the dashboard and title it accordingly. One good option is to create a master client dashboard, then filter and clone to each client that will have access to a dashboard. If you use ConnectWise Manage, AutoTask, Kaseya BMS, or TigerPaw as your PSA, you should have a default dashboard called ‘Client Dashboard Template’ that you can modify to your needs. Add Client as a Viewer The first way you can give your client access to the dashboard you’ve created for them is by adding them to your BrightGauge instance as a viewer. Every BrightGauge plan includes unlimited Viewer licenses. To create a new viewer, click on the admin button at the top right corner of your BrightGauge account, then select ‘Viewers’ from the dropdown. You simply need to provide their name and email address, then select the Dashboard you’d like to give them access to. They will then have a login to your BrightGauge instance, but the only thing they will be able to see is the dashboard you’ve given them access to. As a viewer, they won’t have any permissions on the dashboards or gauges except to drill down, and of course you’ll determine what, if anything, they’ll see on the drill-down. Provide Your Client with Public Dashboard Your other option is to utilize our new Public Dashboards feature, available on our Enterprise plan. To enable this, click on the ‘More’ button at the top right corner of the dashboard, and select ‘Public URL’ from the dropdown. This will provide you with a URL link you can copy and send to your client. Your client can bookmark the URL and will not need to log in to your BrightGauge instance. The Public Dashboards do not allow for drilldown. Again, your client will not have any permissions on this dashboard or on any of the gauges. There are a few great benefits to Customer Facing Dashboards: Customers receiving real time data on their tickets, machines, or projects will have less need to open tickets or call for status updates This shows a level of transparency most MSPs aren’t providing to their clients For your larger clients, this will show the extra benefits they gain by using your services rather than moving their IT operations in house Want help determining what metrics to share with your client, or how to build a great Customer Facing Dashboard? Contact BrightGauge for help with selecting relevant data that will show value to your customers!
We’re excited to welcome Natalie Dinkins to the team as a Customer Support Specialist! Join us in learning more about the newest member of our growing BrightGauge family… In the beginning Natalie was born in Brooklyn, New York, but grew up right here in South Florida. After graduating from Plantation High School, Natalie decided to stay local, attending Broward College for two years before earning her Bachelor’s degree from the University of Miami (C-A-N-E-S!). Later on, she also earned a Master’s degree from Florida International University. Since then, Natalie has explored several interesting avenues, working in energy conservation, higher education, and banking. Most recently, she was a Program/Project Manager for an all-women web development cohort. In that position, Natalie managed an all-women web development bootcamp, spearheading the project by recruiting students, providing input on the curriculum, and hiring teaching staff. That tech-focused role was the perfect springboard for the next opportunity in her career. Joining BrightGauge While going through the interview process here at BrightGauge, Natalie had a chance to meet several team members, who all talked a whole lot about how much they enjoyed their work. Plus, it was really clear that everyone truly loved working with one another, which gave Natalie the sense that this was a team she really wanted to be a part of. Aside from the culture, the opportunity to learn something new while applying her past skills and experience appealed to Natalie and solidified her decision to come on board! Next time you submit a support ticket, you may just hear from Natalie herself. Out of office Outside of work, you can find Natalie spending time with her siblings, whether they’re tailgating at a football game or barbecuing in the park. And recently, Natalie has rekindled her love for running, but it’s a love that sometimes goes unfulfilled. “Between the extreme heat and torrential downpours, running outdoors in South Florida can be a challenge,” says Natalie. Ain’t that the truth!
Dispatch data for amazing service delivery One of the keys to a high-performance help desk is managing the flow of tickets through the service queue. The quality of your service as an IT provider will often be judged not by if you can fix the issue, but the experience that the user has while you do your magic on the back end. Think about the last time you went out for a nice dinner. I’m sure the food was great - that’s why you choose a place with great reviews and a high price tag. So what differentiates fine dining from casual dining? It’s often the experience. Consider the user experience for your clients when they open a support ticket. Is it the equivalent of a casual diner or fine dining? BrightGauge can help ensure the client experience is managed like a 5-star restaurant, differentiating you from other IT providers that are simply providing a sandwich shop experience. Dispatch Role The first point of contact for your clients is usually managed by a dispatcher. I personally don’t support the idea of a pure dispatcher role like some in the industry advocate for. I find this is often an administrative crutch that is put in place to compensate for staff not being accountable for the ticket queues. Instead, the dispatcher role can simply be a designated role that is shared amongst the Tier 1 staff of the helpdesk. Each day or each week a person is designated as the dispatcher and they are responsible for ensuring that tickets get managed according to the expectations of the users and the IT provider. The dispatcher role as a shared responsibility does two things: 1. Helps everyone respect the role a little more When a single person is a dispatcher, especially a non-technical person, the techs have a habit of not respecting the direction of the dispatcher. This is cultural and can be changed, but it’s a persistent hurdle for implementing this role. If everyone does this role from time to time, they are likely to respect the direction of others that they view as peers, especially if they are going to be asking for similar things on a different day. 2. Avoids administrative waste Why have a non-technical dispatcher that can’t pitch in and help the team with tickets when it gets busy? A pure dispatcher role is a consideration when the scale of the team is so large that it becomes a full-time role. Properly structuring your tiers and distributing the dispatcher role within the technical team is far more cost-effective. Even if you have a team of 20 people, this still works. Dispatch Board The first two boards that I build for my clients in BrightGauge are the service manager board and the dispatch board. The dispatch board is a fantastic way for the person doing dispatch to have a 500-foot view of the ticket queue. The dashboard helps the person see the exceptions and can act quickly on those exceptions. Managing by exception is a key methodology for working with a high volume of information. Asking a person to know the status and juggle 100 tickets a day is a recipe for burnout. Humans are good at keeping 5-8 points of information in their heads. Here is an example of a dispatch board. There is a rule in the LEAN methodology that dashboards should follow the five-second rule. Meaning you should be able to glance at the dashboard and be able to understand it in five seconds. Less is more with dashboards. A great way to make the dashboards more readable in BrightGauge is to use size and color-coding. You’ll notice in the example dashboard graphic above the numbers on the left are black. This indicates that they are informational. The colored gauges moving to the right are coded to indicate the severity of their compliance with expectations. In this example dispatch board we have 6 gauges that are color-coded to manage the ticket queue and service the client experience. Unassigned/New Industry best in class response time to new tickets is 15 minutes, but 30 minutes is acceptable if you’re just getting started. Therefore, this number needs to be either 0 or 1. When the number is 0 the gauge is green. Once there is a new ticket, someone needs to respond immediately to acknowledge the ticket and set an expectation with the user of when that ticket will be scheduled. To be very clear, acknowledgment is NOT the autoresponder from the PSA. It is contact either via email or phone from a tier 1 resource or the dispatcher. Actioning the tickets immediately when they come in should help ensure the acknowledgment time stays under 30 minutes and users are given clear expectations about when they will get support. In the restaurant experience imagine this as how long it takes for you to wait at the door before you’re greeted. Nicer restaurants will have a greeter there all the time welcoming guests and setting expectations for when they will be seated. Even in a standard restaurant where you seat yourself, if a server doesn’t come by to welcome you and get you a water within 20 minutes, you would justifiably be annoyed with the experience. Stale A stale ticket means that it has not been touched for more than 3 days. The importance of this gauge is to ensure that there are no tickets left behind. Like the unassigned gauge, stale should be kept to zero. No tickets should go stale if they are assigned to a technician's queue. They should have a routine of touching each ticket every few days to reset expectations with the user about what is being done to resolve the issue. Nothing drives people crazier than to have their support ticket disappear into a black hole. If the technician is waiting on the user, they should be following up via email and phone calls to try to contact the user. This process can largely be automated by your PSA as well to take the load off the tech. If the tech is waiting for a 3rd party vendor or someone else, they should still be updating the user about what they are doing to progress the ticket to resolution. You can buy a lot of grace by just setting and resetting expectations. In the restaurant analogy, this would be how many times the server comes back to your table to see if you need anything while waiting for your meal. If the plates are delayed it’s much nicer to have someone come by and say, “So sorry, I realize you’ve been waiting a while. I just checked with the kitchen and I should have your plates out to you in 10 minutes.” Without this simple polite update, you may grow annoyed that you’ve waited over 30 minutes and not even seen the server. Past Due The past-due gauge indicates a technician was scheduled to work on a ticket and that schedule has not been updated. This either happens because they didn’t enter time on the ticket or they didn’t do the scheduled work at all. Like Unassigned and Stale, this number should be kept at zero and will be green when it is zero, but will change color to indicate it requires attention when the number starts to click higher and turn red. Tech scheduling and time entry is much easier to keep under control when done hour by hour. If you get to the end of the week to try and manage time entry and scheduling, you’re always going to be chasing your tail. The dispatcher role can assist the team by at least informing the user that the scheduling of their support has been pushed. This is not something you can do frequently as the person will grow more frustrated by the ticket being delayed, but communicating with them and setting expectations is better than them expecting to hear from someone at 11 am, and getting angry when they don’t hear from someone the rest of the day. The dispatcher can support the team by ensuring they reschedule their tickets and manage their time entry. This helps to re-enforce the growth of this habit over time. It’s IT, it gets busy, so having someone ping you on IM or tap you on the shoulder to ask you to reschedule your tickets helps drive individual accountability. SLAs The above metrics are important to ensure the tickets are moved into the service queue and kept current, so they can be resolved as soon as possible. These would be lead indicators. When they turn red you are more likely to fail on the associated lag indicators. SLA compliance is a lag indicator. If you manage the team accountability and the process is followed your lag indicators should be green. I have a detailed blog on SLA management on my website that you can see here. Average Time to resolution The average time to resolution indicates how long it took for the ticket to be resolved. This is not the elapsed time, but the SLA work time to complete the ticket. This should be under 8hrs and the lower the better. It’s important that techs don’t game this number by using statuses that park the ticket and turn off the SLA. The client experience is the goal. Not the number itself. Average Time to Acknowledgement This gauge is the lag indicator for the new/unassigned gauge. If someone is responsible for the acknowledgment and dispatching of tickets at all times, this SLA is extremely easy to achieve. The one caution here is to train the techs not to try and hero their way through tickets, especially if they are currently holding the dispatch role. If it’s a 5-minute fix, sure do it, but otherwise, queue up the tickets and answer the next call/email. Not Started This gauge indicates tickets that have not been started after being put into someone’s queue. Notice this number is yellow despite being quite high relative to the thresholds of the other gauges. The size is also smaller than the other gauges, which communicates its importance. In this case, it’s not necessarily a problem that these many tickets haven’t been started. The thresholds on this number will depend a lot on how many techs you have available to service the support queue. The gauge gives the dispatcher an indication if work is piling up and not moving through the Helpdesk. The number may ebb and flow, but if it steadily climbs, it would indicate to the dispatcher or service manager that someone is stuck on tickets and probably taking too long on a single ticket. This can be great for catching complex support issues before they get out of control. An escalation or a second set of eyes may be helpful. Arming Dispatch With The Right Data “Business, like life, is all about how you make people feel. It’s that simple, and it’s that hard.” - Danny Myer, famous restaurateur. A well-configured BrightGauge dispatch dashboard can support the person responsible for dispatch management to focus on the right things: Managing by exception, keeping support requests flowing, and ensuring users are being kept up to date on the status of their support requests. Danny Myer’s quote underlines the importance of any service based industry. Make no mistake IT support is a service industry. How the client feels about their support is equally if not more important than the actual service provided. The experience the users receive is key to creating a sense of value for the support they are receiving. They expect you to be smart and to be able to fix the issues, but actively managing the experience they receive during that support request is what will set you apart from other providers. BrightGauge dashboards are a much easier way to provide an overview of the key metrics required to deliver a high-end support experience for your clients.