Plain-language questions
Ask for average resolution time per month, customer or product in the SQL Explorer with AI. The AI writes the SQL, you see the query and run it yourself; the AI only receives metadata.
KPI · Customer service
Average resolution time is the average time between a ticket being created and it being marked as resolved. It shows how long customers wait in total for a solution, including time waiting on the customer or on other departments. Together with first response time, it is the core measure of service speed.
Sum of (time resolved − time created) across all resolved tickets ÷ number of resolved tickets
Acme Groothandel resolved 1,150 tickets in March. The total time from creation to resolution was 23,000 hours. Average resolution time is 23,000 ÷ 1,150 = 20 hours.
Fictitious figures for Acme Groothandel, a sample wholesaler.
A shorter resolution time means customers get help faster. Look at the median and the resolution time per category as well as the average, because a return or a technical fault simply takes longer than a question about delivery times. Track the trend by week or month and compare with your own service standards.
SQL & DAX
Two examples on a fictitious data warehouse for Acme Groothandel: a PostgreSQL query and a measure for a Power BI model. Adjust table and column names to your own model.
SELECT date_trunc('month', resolved_at)::date AS month,
COUNT(*) AS resolved_tickets,
ROUND(AVG(EXTRACT(EPOCH FROM resolved_at - created_at) / 3600)::numeric, 1) AS avg_resolution_hours,
ROUND((percentile_cont(0.5) WITHIN GROUP (
ORDER BY EXTRACT(EPOCH FROM resolved_at - created_at)) / 3600)::numeric, 1) AS median_resolution_hours
FROM tickets
WHERE resolved_at IS NOT NULL
AND resolved_at >= current_date - interval '12 months'
GROUP BY 1
ORDER BY 1;Resolved Tickets = CALCULATE(COUNTROWS(Tickets), NOT ISBLANK(Tickets[ResolvedAt]))
Avg Resolution (hours) =
DIVIDE(
SUMX(FILTER(Tickets, NOT ISBLANK(Tickets[ResolvedAt])),
DATEDIFF(Tickets[CreatedAt], Tickets[ResolvedAt], MINUTE)),
[Resolved Tickets]
) / 60In ENABLE
Ask for average resolution time per month, customer or product in the SQL Explorer with AI. The AI writes the SQL, you see the query and run it yourself; the AI only receives metadata.
Define the KPI as a measure in your Power BI model and show it in the portal, with "Last refreshed" next to it. Access profiles and optional row-level security decide who sees which figures.
Add the KPI as a tile to a custom dashboard, compared with last year. The Dashboard Builder is a pilot and can be switched on per client.
With the built-in Targets app you set a target for the KPI per month, so you see actuals and target side by side.
FAQ
For each resolved ticket, add up the time between creation and resolution and divide the total by the number of resolved tickets. With 23,000 hours across 1,150 tickets, average resolution time is 20 hours.
Resolution time is the total elapsed time of a ticket, including waiting time. Average handle time (AHT) is only the time an agent actively spends on a contact. A ticket can have a resolution time of two days and a handle time of ten minutes.
Route requests straight to the right person, handle common questions with standard answers and make waiting on other departments visible. Analyse where the time goes per category before you take action.
In an online demo we show how ENABLE makes your data securely available and how you build on it: describing an app in the AI Builder, plain-language questions, dashboards and APIs. And how we set it up and manage it for you.