The five numbers worth putting on a wall
Five numbers: unanswered now, oldest unanswered, median and 90th percentile first reply, resolved without escalation, and reopened. The first two are actionable this minute; the rest tell you whether last week worked.
1. Unanswered right now
The only number that can be acted on immediately, and the one a phone cannot show you. Unread is not unanswered: a colleague opening a message marks it read and changes nothing for the customer.
2. Oldest unanswered
Your actual worst case, and somebody is living through it. A queue of forty with an oldest of nine minutes is healthy. A queue of three with an oldest of two days is not, and the count alone says the opposite.
These two together are the whole dashboard for a shift. Everything else on this page is for the meeting on Monday.
3. First reply, median and 90th
Always both. The median tells you what normally happens; the 90th tells you what your reputation is made of, because the people who talk about you are disproportionately in the tail.
| Reading | Means |
|---|---|
| Median low, 90th low | Working. Look at volume instead. |
| Median low, 90th high | Something specific is falling through - a channel, a shift, a topic |
| Median high, 90th high | Understaffed, or nobody owns the queue |
| Median high, 90th low | Almost impossible; check your measurement |
4. Resolved without escalation
What proportion of conversations the first person could finish. It is a measure of tooling and knowledge rather than of effort, and it is the number that improves when you fix the answers people keep having to go and find.
5. Reopened
A conversation marked settled that the customer came back to. This is the honest counterweight to speed: a team pushed on response time will close conversations faster and reopen more, and a metric that cannot see that is a metric that makes service worse.
What not to measure
- Messages per agent. You get short unhelpful replies.
- Read receipts. Staff open everything to clear the badge and you lose the signal that showed what needed attention.
- Time to close. Rewards closing, which is not the same as resolving.
- Anything a person can move without helping anybody. That is the test, and it disqualifies most activity metrics.
Questions people actually ask
What is a good response time for WhatsApp support?
Minutes during your stated hours, because customers treat WhatsApp like a conversation rather than like email. Consistency matters more than speed: an hour reliably beats five minutes sometimes and a day otherwise.
Why is average response time a bad metric?
Because it hides the tail. Ten seconds and six hours averages to three hours, which describes neither conversation and hides the one that lost you a customer.
Njiwa
One inbox for WhatsApp, Facebook and Instagram, and an API that sends over either WhatsApp rail. 7 days free, no card.