August 2026 in customer support

From the editor

This issue gathers everything we published in August 2026 — the analysis, the numbers, and a benchmark worth keeping. Every figure traces to a named public source.

The one number

The month in numbers

Benchmark spotlight

Agent Occupancy

Occupancy has an optimum, not a maximum: the healthy consensus for inbound voice sits around 75-85%, but read it against your call type — transactional retail and predictive-dialer outbound run higher, while healthcare and technical support run lower because of longer after-call work — and treat anything sustained above 90% as a burnout-and-attrition signal rather than a win.

Term under the lens

Schedule Adherence

How closely agents follow their scheduled work and break times.

Steal this

Support hiring interview kit

A full interview loop for hiring frontline support reps — role scorecard, screening questions, a realistic ticket-response exercise, values/empathy questions, and a weighted scoring rubric — for when a vibe-based hire keeps burning you.

Dispatches this month

• QA & QualityAuto-QA scores 100% of tickets — should you trust it?AI quality scoring promises to grade every ticket instead of a thin sample — but coverage isn't accuracy, so here's where it helps, where it drifts, and how to calibrate it.
• QA & QualityCoaching conversations that don't feel like performance reviewsSlide a QA scorecard across the desk and the rep reads a verdict, not a lesson — here's how to turn the score into coaching that changes the next ticket instead of triggering a defence.
• Metrics & MeasurementDSAT: the signal your CSAT is buryingTop-box CSAT is an average, and an average of a lopsided distribution tells you almost nothing about the tail that leaves. Tracking dissatisfaction as its own line catches the problem weeks before your headline number moves.
• CX & TrustThe health score that predicts churn without the noiseA customer health score is either an early-warning system or a mood ring. What separates the two: which signals you weight, where you set the threshold, and whether you ever backtest it against who actually left.
• QA & QualitySampling math for small QA teamsSmall teams review a random slice of tickets and report it like it's precise. The math says it's mostly noise — here's how many you actually need instead.
• QA & QualityCalibration: why two reviewers disagree on the same ticketHand the same ticket to two reviewers and you'll often get two very different scores. Calibration is the unglamorous fix, and the spread between reviewers is the metric that matters.