Reading Your Support Inbox's Real Bottlenecks: Queue, Hourly Load, and Abandoned Chats
Chat's analytics expose specific, named operational metrics — not a vague dashboard — mapped to the real questions a support lead actually needs answered.
"Analytics" is one of the most overused words in support tooling — most dashboards show you a chart of volume over time and call it done. Chat's analytics endpoint is built around a narrower, more useful idea: a small set of specifically named metrics, each mapped to an operational question a support lead actually asks.
Queue metrics: what's waiting right now
Queue metrics answer the most immediate question — how many conversations are currently waiting, and for how long. This is the number you check when you want to know if today is fine or if you're behind, not a historical trend.
Hourly load: when you're actually understaffed
Hourly load breaks volume down by hour, which is the metric that turns "we need more coverage" from a guess into a specific, defensible claim. If your hourly load consistently spikes at a time your current shifts don't cover — see the routing and shifts guide for how shift scheduling works — that's a direct, visible mismatch between demand and staffing, not something you have to infer from anecdote.
Agent activity: who's actually handling volume
Agent activity tracks what each agent is doing, which is the metric for questions about workload distribution — whether volume is landing evenly across a team or concentrating on a few people, intentionally or not.
Abandoned but reachable: the conversations you can still save
This is the least obvious and most operationally useful metric on the list. "Abandoned but reachable" identifies conversations where a visitor left before anyone responded, but left contact information behind — meaning the conversation is lost as a live chat, but not lost as a lead or a support case. This is a genuinely different category from a conversation that simply timed out with no way to follow up; it's a specific, actionable list of people worth a follow-up email or a callback.
Response metrics: how fast you actually respond
Response metrics round out the set — the concrete numbers behind claims like "we respond fast," rather than a general sense of it. Pair this with the SLA tracking Chat runs by default (see the piece on the fixed 5-minute SLA clock) for the fuller picture of how responsiveness is measured.
Using these together
None of these five metrics answers "how's support going" on its own — that's the point of having five instead of one. Queue and hourly load tell you about staffing and timing; agent activity tells you about distribution; abandoned-but-reachable tells you about recoverable loss; response metrics tell you about actual performance against expectation. A support lead checking in weekly gets more from glancing at all five together than from watching any single number closely.