In the work of optimising customer service, a central point is that there is a difference between having "met the SLA" and delivering a good customer experience. Technical compliance with Service Level Agreements (SLAs) does not in itself guarantee that the customer feels well treated, heard or helped. A one-sided focus on SLA metrics can lead to a culture where quantity is prioritised over quality, and where the results look good in the reporting but not in the customer's experience.
To support both operational excellence and strong customer experiences, two separate but complementary dashboards are used. This approach provides a more nuanced picture of performance and supports decisions that benefit both internal processes and customer satisfaction.
Two sides of the same coin: SLA vs. customer experience
The value of separate dashboards becomes clear when it is established what each dashboard represents. They act as two different lenses on the same service delivery. Each lens reveals different insights, and the full overview is achieved by using both.
What is an SLA dashboard?
An SLA dashboard acts as an operational compass. It focuses on internal, contractual and measurable targets. The purpose is to ensure compliance with agreements — either internally between teams or externally with customers. The focus is on efficiency, speed and resource management.
The dashboard typically answers questions such as:
- Is the workload under control?
- Where do bottlenecks arise in the process?
- Are the agreed reply times being met?
- Which agents or teams need support to reach their targets?
The dashboard is relevant for team leads, operations managers and agents who need a real-time picture of day-to-day operations.
What is a Performance dashboard?
A Performance dashboard acts as a strategic barometer. It measures the actual experience and the quality of the service delivered. The focus shifts from the pure numbers to the customer's experience, effort and loyalty. It is about quality, relevance and relationships.
The dashboard typically answers questions such as:
- Do customers genuinely feel helped?
- How easy or difficult is it for customers to get problems resolved?
- Does the service contribute to loyalty and trust?
- Which parts of the service create the greatest satisfaction or frustration?
The dashboard is relevant for managers, account managers, product teams and others who work with the long-term customer relationship and business health.
The critical gap: When numbers and experience do not match
The most valuable insights often arise at the intersection of the two dashboards — particularly when they do not match. This gap acts as a warning signal that requires attention.
Example 1: The fast but inadequate solution
- The SLA dashboard shows: 98% of all tickets were answered within the target of 8 hours.
- The Performance dashboard shows: Customer Satisfaction (CSAT) for the same tickets is only 65%, and many customers give low ratings.
Possible cause: Tickets may have been closed quickly with a standardised or inadequate reply in order to hit the SLA. The customer may have had to write again to get a satisfactory answer, which increases frustration and overall effort. The SLA is met, but the customer's trust is weakened.
Example 2: The slow but perfect solution
- The SLA dashboard shows: The SLA is breached on 15% of the complex technical cases.
- The Performance dashboard shows: For the same cases, CSAT is 95% and the reopen rate is low. Customers praise thoroughness and expertise in their comments.
Possible cause: Agents have spent the necessary time analysing complex problems and delivering a real solution rather than a quick temporary fix. The SLA is breached, but the result creates high satisfaction and loyalty.
With separate dashboards, these patterns can be identified quickly, the causes understood and the strategy adjusted. Without the separation, the first situation risks being assessed as a success and the second as a failure.
Build the right dashboards: Recommended structure
To achieve an overall overview, two dedicated dashboards in Zendesk Explore are recommended. Each dashboard is designed to answer specific questions and support different audiences.
Dashboard 1: The SLA compliance dashboard (the operational tool)
This dashboard is aimed at team leads, operations managers and agents who need to follow day-to-day operations. It should be easy to read and action-oriented.
Key figures to include:
-
Core SLA Metrics:
- Number of SLA met: The number of tickets that met the SLA.
- Number of SLA breached: The number of tickets that breached the SLA.
- SLA compliance percentage (%): A central KPI for overall performance relative to the target, broken down by channel, priority and team.
-
Efficiency Metrics:
- Average First Reply Time: Indicates response speed.
- Average Full Resolution Time: Indicates efficiency in resolving the case completely.
- Agent Handle Time: The time during which an agent is actively working on a ticket.
-
Diagnostic Metrics:
- Causes of SLA breaches: A qualitative analysis of why SLAs are breached. In Zendesk, this can be achieved by using macros to tag tickets with causes such as "Complex case", "Waiting for customer", "Missing information from a third party", etc. This supports targeted improvements.
- SLA performance per agent: Identifies top performers and areas in need of coaching.
Dashboard 2: The customer experience dashboard (the strategic tool)
This dashboard is aimed at managers, product teams and others who work with the long-term customer relationship. The purpose is to make visible how the service is actually experienced.
Key figures to include:
-
Direct Feedback Metrics:
- Customer Satisfaction Score (CSAT): Direct feedback after an interaction ("How satisfied was the customer with the support?"), broken down by topic, agent and channel.
- Customer Effort Score (CES): "How easy was it to get the problem resolved?" Low effort often correlates with high loyalty.
-
Behavioral Metrics:
- First Contact Resolution (FCR) rate: An indicator of quality. How many problems are resolved at first contact? This can be measured by looking at the number of public comments in a ticket.
- Reopen Rate: How often is a "solved" case reopened? A high rate indicates that the solution was inadequate.
-
Loyalty Metrics:
- Net Promoter Score (NPS): Measures general loyalty and willingness to recommend the company. Although it is often measured via periodic surveys, it can be integrated to provide an overall picture of the customer's attachment.
From insight to action: A strategic roadmap
Dashboards only create real value when data is actively used for improvements. The practices below support translating data into action.
1. Track both consistently and automatically
Data should be collected consistently across channels. Without reliable data, dashboards lose value. In Zendesk, this means ensuring correct SLA configuration and that CSAT/CES surveys are enabled on relevant email and web form tickets. It should be standard practice to follow both SLA status and customer feedback.
2. Analyse the gap systematically
Fixed time should be set aside (e.g. weekly or every two weeks) to compare the two dashboards. An effective method is to isolate cases where the results diverge:
- Filter in Zendesk: "Tickets where the SLA is met, but CSAT is bad (e.g. 1-2 stars)".
- Filter in Zendesk: "Tickets where the SLA is breached, but CSAT is excellent (e.g. 5 stars)".
The cases are reviewed with the team, focusing on:
- What common traits are seen across the cases?
- Is there a particular topic, a specific agent or a type of customer that recurs?
- Was the reply fast, but imprecise or impolite?
- What behaviour led to the positive result in the other group?
The analysis supports prioritising the right improvement measures.
3. Prioritise the customer experience and give agents autonomy
The results of the analysis should be used to adjust the focus. A persistent gap can indicate that SLAs are set inappropriately. An SLA should act as a minimum requirement, not a ceiling for good service.
- Create a culture that rewards quality: Recognise agents with high CSAT scores, even when SLA limits are approached in order to deliver the best solution.
- Allow breaking an SLA in special cases: It should be clear that extra time on complex cases may be necessary to ensure First Contact Resolution. Quality should carry more weight than speed when there is a conflict.
4. Adjust SLAs dynamically and data-driven
SLAs should be treated as living targets that reflect capacity and customers' expectations.
- Review SLAs quarterly: Use data from the performance dashboard to adjust SLAs.
- Too strict SLAs? If SLAs are consistently breached and the cause is unrealistic targets, they should be adjusted upwards to avoid demotivation and poor service.
- Too lenient SLAs? If SLAs are consistently met with a large margin, they may be too unambitious to drive improvement and efficiency.
5. Involve the whole team and make data transparent
Insights from both dashboards should be shared with the whole support team.
- Hold weekly "Dashboard Huddles": Review the most important figures from both dashboards in 15 minutes. Recognise results and discuss challenges.
- Use data in coaching: In coaching, both SLA performance and CSAT scores should be included, so that speed and perceived quality are assessed together.
- Celebrate "Quality Champions": Supplement recognition based on the number of closed cases with recognition for the highest CSAT or the best FCR rate.
The synergy: When both worlds meet
The goal is not high performance on one dashboard at the expense of the other. The strongest effect arises when the service is both fast and of high quality. By separating and, at the same time, analysing SLA and actual performance, a better basis is created for delivering customer service that is both efficient and builds strong, loyal customer relationships.
The overall measure of success is found in this synthesis — not only in the reporting, but in the customer's experience.