How to explain customer support metrics in context
A support metrics report helps a team understand service activity and areas for review. The meaning of each metric depends on its definition, population and time window.
Start with the right material.
- What you provide
- a readable support metrics table.
- The intended result
- Summarize ticket counts, observed response metrics and definitions supplied on the page.
How the workflow works.
Preserve labels such as first response, resolution time and satisfaction, then report the supplied counts and units. Keep averages, medians and percentile measures distinct when they appear.
What to check in the result.
Check whether unresolved tickets and excluded channels affect the figures. A single aggregate should not become a conclusion about every customer's experience or an individual agent's performance.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.