The help desk measures what it delivers: on each resolution, the requester can rate how their request was handled, and the performance pages bring together volumes, times, commitments met and satisfaction. This article explains the satisfaction survey and the performance screens.
Before you start #
- The performance pages are open to agents (their activity), to service managers (their services) and to help desk administrators (the whole help desk).
- The survey is set per service, by a help desk administrator.
The satisfaction survey #
On the service page, the Satisfaction survey section offers Satisfaction survey on resolution: Sent on every resolution (default) or Off: no survey is sent.
- When an agent moves the ticket to “Resolved”, the requester receives the survey by e-mail and in their request: a rating from 1 to 5 (from “Not satisfied at all” to “Very satisfied”) and an optional comment. This e-mail also announces the resolution.
- They have 14 days to answer, once per resolution. If the request is reopened and resolved again, a new survey goes out.
- Closing directly, without going through “Resolved”, sends no survey.
- A task of a service catalogue request sends no survey: the request sends it when it is resolved. A ticket resolved with a major incident sends none either: each person affected receives a single resolution notice.
- A rating of 1 or 2 alerts the service managers (otherwise the escalation readers), once.
The rating shows in the timeline and in the ticket’s Satisfaction card; the comment is read by the service’s agents only.

The dashboard #
Open Help desk › Performance, Dashboard tab. Choose the period (the last 30 days by default), the service and the agent. The indicators:
- Incoming, Resolved and Open today;
- Commitments met (first response and resolution);
- Median first response and Median resolution, in business hours;
- Average satisfaction, with the survey response rate;
- Requests avoided by the knowledge base (“My problem is solved” while filing).
Then come open tickets by age, incoming by channel, ratings received, and the By service and By agent tables.

The ticket list and export #
The Tickets tab shows the same rows as the dashboard, one per ticket: a ticket appears if it was filed, got its first response or was resolved in the period, or is open today. Break the indicators down by service, agent, channel or customer contract (Group by; the customer contract is that of the organisation linked to the requester, with or without the CRM, see The help desk and the CRM), filter by channel and download the list with Export. The same report, Help desk tickets, is available in People Analytics.

Who sees what #
| Reader | Scope |
|---|---|
| Agent | Their activity: the tickets assigned to them. |
| Service manager | The services they manage, and their activity. |
| Help desk administrator | The whole help desk. For tickets they do not read as an agent, the list shows neither the subject, nor the requester, nor the satisfaction comment. |
Good to know #
- Reporting times are fixed in business hours at the moment of the reply or resolution: changing a service’s hours does not rewrite the past.
- A ticket that went through an approval flow counts its times from the decision.
- The days of the period are read in the workspace’s display time zone.
- A ticket merged into another one counts among incoming tickets, never among resolved ones or in resolution times. After a merge, only the main ticket’s requester receives the survey; the requesters of grouped requests receive the resolution notice.
- Each task of a service catalogue request counts as a ticket of its service, and the request as a ticket of the service that coordinates it (see The service catalogue). A major incident’s common message does not give the attached tickets their first response (see Major incidents and problems).
