Cost per resolution connects operations and finance, but it is comparable only when the denominator, period, and allocation remain stable. Read it with quality and repeat contact.
Choose one outcome unit
GOV.UK defines cost per transaction as total service cost divided by completed transactions and includes all channels and assisted support. Adapt the idea clearly: cost per resolved case = attributable operating cost ÷ eligible resolved cases. If the operation does not manage cases, use another unit and give the measure another name.
Contact, conversation, ticket, and resolved case are not synonyms. One case may have several contacts, and a conversation may end without resolution. Keep the cost period aligned with the denominator and explain how reopens and work in progress are treated.
What belongs in cost
Include pay and employment cost for dedicated staff, the relevant share of leadership and quality, software, telephony or messaging, recurring training, and suppliers. Allocate shared infrastructure and functions with a stable, visible rule. Show exceptional investment separately from recurring operations when needed.
Avoid costs already allocated by another function. Record the financial source, accounting period, currency, applicable tax, and allocation rule. Customer service should not invent finance numbers; reconcile them with the accountable finance team.
| Component | Recommended treatment | Safeguard |
|---|---|---|
| Direct team | Include period cost | Use the correct period and workload |
| Leadership, quality, training | Allocate with a documented rule | Do not exclude necessary work |
| Software and channels | Include attributable cost | Separate fixed, variable, and tax |
| Shared infrastructure | Allocate consistently | Prevent double counting |
| Exceptional project | Show separately | Do not hide recurring operations |
| Resolved cases | Use the eligible population | Define reopens and work in progress |
Read efficiency with outcome and risk
Lower cost may come from better knowledge, automation, or less avoidable demand, but it may also come from a larger queue, premature closure, or effort shifted to customers. Track repeat contact, reopen, quality, complaints, SLA, and backlog alongside cost.
Segment by reason and channel only when allocation is credible. Use the measure to test hypotheses—for example, whether fixing a frequent cause reduces contacts and total cost—without turning correlation into promised savings.
Write the metric contract before comparing results
Record the name, management question, numerator, denominator, start event, end event, observation window, calendar, exclusions, and owner. If two people cannot reproduce the same result from the same cases, the definition is not ready.
Keep the formula version with the report. A change in status, channel, business hours, or reopen policy can break historical comparability. Preserve the previous series or mark the break clearly whenever the rule changes.
- A management question written in one sentence
- An explicit numerator and denominator
- Documented eligible population and exclusions
- An observation window long enough for the measure to mature
- Segments for channel, queue, reason, and period
- A conversation sample that explains the change
- A named owner, expected action, and next review date
How to apply this with Signaldesk without claiming more than the data proves
In Signaldesk, use queues, owners, history, states, and conversation context as the operating record. Consistent fields let a manager trace a number back to the conversations behind it. AI can suggest reasons, summarise history, and flag review candidates, but people should validate classifications and decisions that affect customers or staff.
Confirm which events, reports, and exports are available in your workspace before making a formula depend on them. If a calculation needs financial cost, cohorts, or an external rule, combine the operating record with the right source and document the reconciliation. The aim is traceability, not artificial precision.
A four-week pilot
In week one, freeze definitions and establish a baseline. In week two, inspect a conversation sample and correct events or states. In week three, choose one priority cause and test a small change. In week four, compare the same segment, record side effects, and decide whether to keep, adjust, or remove the change. Four weeks is not a promised outcome; it is a practical period for validating the method and the team’s ability to act.