Performance
How every number on the Performance dashboard and in the weekly performance email is calculated.
The Performance dashboard shows how your support is doing: how fast you reply, how many tickets arrive and get resolved, how much is handled automatically, and how you compare with other companies on Elvo. This page defines every number, so you can use them in your own reporting and comparisons.
Which tickets count#
The dashboard measures customer conversations on all channels (email, chat, social media, phone). These are left out of every number, unless a metric below says otherwise:
- Ignored tickets (spam, and tickets that rules or AI intake filtered out as noise).
- Out-of-office replies and other automatic replies.
- Notifications and confirmations that were filed into Archive the moment they arrived and that nobody replied to.
- Deleted tickets, drafts and personal mailboxes.
- Internal team chat.
A reply means a reply from a person on your team that the customer can see. Replies you send from Outlook or Gmail count when the mailbox is connected to Elvo. Internal notes, forwards, deleted messages and AI replies do not count as a reply.
Started by the customer means the first message on the ticket is from the customer. Response metrics (time to first reply, time to resolution, first-reply resolution) only include tickets that the customer started, because a ticket you started has no customer question to answer.
Periods and comparison#
Choose a period at the top: this week, last week, last 7 days, 28 days, 90 days, all time, or your own dates. Each change is compared with the previous period of the same length, or with the same dates one year earlier. All times are Icelandic time.
The weekly performance email is sent to admins every Monday at 09:00. It covers the 7 days before it was sent (Monday 09:00 to Monday 09:00), with the same calculations as the dashboard.
Ticket volume#
- New: tickets created in the period.
- Closed: tickets resolved in the period, by the time they were resolved. This includes older tickets that were closed in the period, so New and Closed do not describe the same tickets. Tickets resolved by your own rules count here. Ignored tickets do not.
- Unresolved: tickets that are open or pending right now, including snoozed tickets and tickets waiting for the customer. This is a snapshot at the moment you look (in the weekly email, at the moment it was sent), not a number for the period. Archived tickets are not included.
The small arrow under Unresolved shows New minus Closed for the period, that is, whether the queue grew or shrank.
Time to first reply#
The median time from when a ticket is created until the customer gets the first reply from a person on your team. Half of the tickets got a reply faster, half slower. Only tickets created in the period, started by the customer and with at least one reply count.
- Real time counts all hours, also nights and weekends.
- Business hours counts only your business hours (by default Monday to Friday 09:00 to 17:00). Admins change them in Settings.
- P90 is the time within which 90% of tickets got a reply.
Time to resolution#
The median time from when a ticket is created until it is marked resolved. Only tickets resolved in the period and started by the customer count. Tickets closed instantly by rules or AI intake are left out, because they would pull the median down to zero. Tickets resolved by a person or by the chat or voice agent count.
First resolution measures to the first time the ticket was resolved, so later reopens do not change it.
First-reply resolution#
The share of tickets resolved in the period that needed exactly one reply from your team.
- Only tickets started by the customer count.
- AI replies, internal notes and forwards do not count as a reply.
- Resolved tickets with no reply in Elvo (for example handled by phone, or closed by a rule) are part of the total but can never count as resolved in the first reply. If much of your work happens outside Elvo, this rate will look lower.
Reopen rate#
Of the tickets resolved in the period: the share that has been reopened at least once in its lifetime, that is, gone from resolved back to open or pending.
- The most common cause is the customer replying to a resolved ticket. Any reply counts, also a short "thank you", and there is no time limit.
- The reopen can have happened before the period, if the ticket was resolved again in the period.
- A reopen does not count when an agent applied the acknowledgment suggestion (Elvo saw that the reply only said thanks, and the ticket was closed again), or when an admin undid a bulk close.
Automation#
The share of closed tickets in the period that a machine handled, without a person closing them. This metric has its own total, which is larger than Closed:
- Total: tickets resolved in the period plus tickets ignored in the period (ignored tickets are counted by when they arrived). Filtered spam and noise are part of this total, but not of New or Closed.
- Automated: tickets resolved or ignored by your automation rules, by AI intake (for example notifications and spam it filtered automatically), or by the chat or voice agent.
- Tickets that a person closes or ignores by hand do not count as automated.
Customer satisfaction#
The share of customer ratings in the period that were positive. Customers rate when a chat ends, or in an email after a ticket is resolved if the email survey is on. A rating is credited to the team member who replied last.
AI involvement#
The share of tickets created in the period that got at least one reply from AI or the system.
Elvo median#
Beside several metrics you see the Elvo median: the median of the same metric across all paying companies on Elvo. Each company counts as one data point, whatever its size.
- It is calculated every night for the last 7, 28 and 90 days. It is not shown for other periods.
- A company only contributes when it has at least 20 tickets behind the metric in the period, and a median is only shown when at least 5 companies contribute.
- It is shown for time to first reply, time to resolution, first-reply resolution, reopen rate, automation, customer satisfaction and AI involvement. Volume numbers (New, Closed, Unresolved) have no median, because they depend on company size.
Team comparison#
The team table shows the same metrics per team. New, time to first reply, first-reply resolution and reopen rate are based on tickets created in the period. Time to resolution is based on tickets resolved in the period, like the card at the top.
FAQ#
Why do the numbers change when I look at an old period again? Tickets change after the fact. A ticket that was resolved in the period and later reopened is no longer counted as closed in that period, and a ticket that a person un-ignores moves back into the numbers.
Why are Closed and the Automation total different? The Automation total also includes ignored tickets (filtered spam and noise), which are left out of Closed.
Where do the numbers come from? Straight from your tickets in Elvo. Each definition is also shown when you hover the ⓘ icon on a card.