“You can't improve what you can't measure.” When support teams are driven by data rather than intuition, improvement cycles speed up dramatically.Which KPIs to track, which dashboards to build and for whom, and which reports to bring to regular meetings?——Getting this design right will help you demonstrate support ROI to management, prioritize your team numerically, and detect problems before they occur. This chapter systematically explains KPI hierarchical design, dashboard mockups, standard report catalogs, and analysis cadences.
Not everyone needs to see every KPI. Management doesn't need to check ticket numbers every day, and agents don't need to track NRR (net revenue retention rate).By dividing the design into three layers to determine who looks at what, why, and which indicators, each role can focus on only the data necessary for decision-making.. A flood of KPIs is the same as "not seeing anything."
No one will use a dashboard full of KPIs. Management wants to know how support contributes to the company's revenue, not the average ticket response time.When designing each dashboard, first write a one-sentence statement that says, "What do you decide when you look at this dashboard?"This allows unnecessary indicators to be naturally excluded.
If KPIs are not accurately defined, the meaning of "resolution time" may differ depending on the team, or the starting point of measurement may shift, making data incomparable. Below, we have organized the definitions, calculation formulas, and industry benchmarks for the core KPIs that should be tracked with Service Hub.
HubSpot's dashboard is a "canvas for reporting." The setting location is Report → Dashboard → Create new. You can add each report as a widget and set it to automatically update and send regular emails. The completed mockup of the dashboard for managers is shown below.
| manager | Number of cases in charge | CSAT | FRT average | TTR average | SLA |
|---|---|---|---|---|---|
| Keiko Tanaka | 87 | 94% | 1.8h | 14.2h | achievement |
| Taro Yamada | 92 | 89% | 2.6h | 19.8h | achievement |
| Sakura Suzuki | 74 | 76% | 3.9h | 28.4h | Not achieved |
| Ken Sato | 68 | 91% | 2.1h | 16.7h | Partially unachieved |
When disclosing CSAT scores for each person in charge, the purpose is clearly stated to be ``to quickly identify and coach members who need support,'' rather than ``to have them compete in rankings.''For agents with low CSAT, check whether they are using Copilot's reply suggestions and whether they have a habit of referring to KB, and provide them with opportunities to acquire skills.The approach is productive.
HubSpot Service Hub comes with many standard reports, but many people say they don't know which one to use. Below is a summary of the 8 ready-to-use standard reports and the questions they answer. All settings are Report → Report → Service You can choose from categories.
Nothing changes just by looking at the data.Incorporate the cycle (cadence) of “who sees which report, when, and decides what” into the organization's calendar.is the only way to transform analysis into improvement actions.
Instead of reporting in your weekly review, “SLA was 91%, down from last week,”Deciding in the meeting, “What is the cause of the decline in SLA?” → “What should we change within the next week?” → “Who is the owner?”Structure the agenda. By confirming data and setting improvement actions in the same meeting, analysis becomes a tool for "decision making" rather than "reporting."
Management only tracks NPS, renewal rate, and NRR, managers track FRT, TTR, SLA, and CSAT, and agents only track their own tickets and SLA remaining time. “All metrics for everyone” results in dashboards that no one uses.
FRT, TTR, SLA, CSAT, AI resolution rate: The premise of analysis accuracy is that all the team members share the same understanding of these five definitions and calculation formulas. If the meaning of "resolution time" differs between members, data that cannot be compared will accumulate.
No one uses a dashboard full of KPIs. By clearly stating ``what decisions will be made by looking at this dashboard'' before designing each dashboard, unnecessary indicators can be naturally eliminated.
Ticket volume, FRT/TTR, SLA, CSAT, AI resolution rate, KB performance, person in charge, health distribution—By understanding the "question" that each report answers, you will be able to choose the report to bring to the meeting without hesitation.
Incorporate daily 5-minute, weekly 30-minute, monthly 2-hour, and quarterly executive reporting cycles into your organization's calendar. The process doesn't end with just ``looking at the data,'' but also decides in the same meeting ``who should change what, and by when.''
Rather than blaming agents with low CSAT, check their Copilot usage status, KB reference habits, and skill gaps and provide support. Creating a culture where data functions as a ``tool for growth'' rather than a ``fear'' will lead to a long-term improvement in the team.