What the tool measures and what it costs
Almost every tool times from opening the conversation to sending the reply.
That leaves out two expensive things. The stretch spent hunting for the fact on another screen, and the cost of getting concentration back after the interruption. That is why a ticket logged as four minutes in the tool has cost a good deal more.
Why it matters
It is the multiplier in the sum.
Team cost per hour times average handle time times volume gives what support costs, which is the figure you use to decide whether to hire, automate or document. Without it, the only figure in play is the tool license, which is usually the small part of the total.
The formula, with an example
Total active working time on conversations divided by the number of conversations handled.
The figures in the example are illustrative.
- What it includes. Reading, finding the information, replying and logging. Waits are excluded.
- Example. 50 hours of active work in a week and 300 conversations give 10 minutes per conversation.
- From time to headcount. Those 50 weekly hours are a little over one full-time person just for replying.
Why driving it down at all costs is a bad idea
It is the easiest metric to game.
You lower it by answering shorter and worse. When it becomes a target on its own, reopens go up, first contact resolution goes down, and total cost rises even as the number improves.
Where the saving is
In looking up information before replying.
Having the plan, the usage and the billing of whoever is asking on the same screen takes out most of the time the metric never times.