Support QBR deck outline

A QBR is not a status update. It is the one hour a quarter where you argue, with evidence, that support is worth what it costs — and ask for what you need next. Every slide should move that argument forward. If a slide doesn't change a decision or defend a number, cut it.

The spine of the whole deck: never show an efficiency number without its quality guardrail on the same slide. Faster-and-cheaper is only a win if the work still held. Handle time and QA score, cost per contact and CSAT, deflection and reopen rate — always in pairs. That pairing is the difference between a leader who's managing a support org and one who's quietly degrading it to hit a cost target.

Before you build it

Lock these before you open the deck. Half of bad QBRs are bad because the numbers weren't nailed down first.

• Pull the same metrics as last quarter, defined the same way (a changed definition is a lie by accident)
• Agree the date ranges — full quarter vs. quarter-to-date, and match last year's window for seasonality
• Write down the definition of every metric on the appendix slide (resolution, reopen, "touched by AI") so nobody relitigates it live
• Get one number you'd rather not show onto a slide anyway — the deck that only goes up isn't believed
• Decide your one ask before you build slide 2, and reverse-engineer the deck to support it
• Pre-share the deck 24h ahead so the meeting is a discussion, not a read-along

The one-sentence version

Before the slides, write the quarter in one sentence you could say out loud without notes: "We handled N% more volume at flat cost and held quality, but the backlog on [X] is becoming a risk, and we need [the ask] to keep it from breaking next quarter." If you can't write that sentence, you don't understand your own quarter yet. Everything after this is evidence for it.

Slide 1 — Title & TL;DR

What to show: The quarter and org. Three or four bullets: the headline result, the one number you're proudest of (paired with its quality guardrail), the one thing that's fragile, and the ask. A tiny scorecard strip: volume, cost per contact, CSAT, QA score, this quarter vs. last.

The story it tells: "Here's the whole argument in thirty seconds — the rest of this deck is why you should believe it." Executives decide how much attention to pay from this slide. Make it self-contained: if they read only this, they should still leave with the right conclusion and the ask.

Slide 2 — Agenda & time budget

What to show: The running order and roughly how long each block gets. Protect time for wins, risks, and the ask — those are the slides that change decisions, and they're always the ones that get squeezed when volume-and-trends runs long.

The story it tells: "This is a balanced account — efficiency and quality, good news and bad — not a victory lap." Setting the agenda openly buys credibility for the risks slide later.

Section A — Volume & trends

Slide 3 — Volume & demand

What to show: Total contacts this quarter vs. last three quarters and vs. same quarter last year. Break the change into demand (more customers, more usage) vs. failure (bugs, outages, confusing releases generating avoidable tickets). Contacts-per-active-account is often more honest than raw volume — it separates "we grew" from "we got worse."

The story it tells: "Volume went up because the business grew, not because the product got worse" — or the honest opposite. Naming avoidable volume here sets up the "reduce tickets at the source" ask later, and stops volume growth being read as pure success.

Slide 4 — Channel & contact-reason mix

What to show: Volume split by channel (email, chat, phone, self-serve, in-product) and the top 8-10 contact reasons with quarter-over-quarter movement. Flag the reasons growing fastest and the ones that are pure product friction.

The story it tells: "Here's what customers actually needed, and here's the shortlist that engineering or product could eliminate at the source." This is where support earns its seat as the company's earliest, cheapest signal of what's broken.

Slide 5 — What changed this quarter

What to show: A short annotated timeline — releases, incidents, policy changes, staffing changes, price changes — overlaid on the volume line. Every spike gets a labelled cause.

The story it tells: "Nothing here is a mystery; we know why the queue moved." Pre-empting the "why did X happen?" questions with causes already on the slide is what makes the room trust the rest of your numbers.

Section B — Quality

Slide 6 — The quality bar

What to show: Both sides of quality, together. Outcome quality (CSAT/NPS, reopen rate, repeat-contact rate) and conduct quality (internal QA score, and the sample size behind it). Trend each over four quarters. State the QA coverage — 2% of tickets or 100% — because a QA number is only as trustworthy as its sample.

The story it tells: "Customers were satisfied and the work was genuinely correct" — CSAT catches feeling, reopen/QA catch reality, and you need both. A high CSAT with a rising reopen rate means you're being liked and being wrong; say so.

Slide 7 — The efficiency-quality frontier (the money slide)

What to show: Put the efficiency metrics and the quality metrics on one slide, side by side, trended together: handle time and QA score; cost per contact and CSAT; automation/deflection rate and reopen rate. The claim you're making is that you moved efficiency without paying for it in quality.

The story it tells: "We got more efficient and the work still held — here's the proof they moved together." This is the single most important slide in the deck and the easiest to fake. If an efficiency gain did cost you quality this quarter, show it here honestly and own the trade — that candour is worth more than the metric. A frontier that only ever improves on both axes with no tension anywhere is the number nobody in the room believes.

Section C — Team health

Slide 8 — Team health & capacity

What to show: Headcount vs. plan, attrition (and regretted vs. non-regretted), tenure mix, occupancy/utilisation, absence, and a real engagement or eNPS signal. Pair it with ramp time for new hires. If you're using AI assist, show whether it's shortening ramp for your least-experienced agents — that's where the evidence says the gain lands.

The story it tells: "The people who delivered this quarter's numbers can deliver next quarter's" — or "we hit the numbers by running the team too hot, and here's the bill coming due." Occupancy at 90%+ with rising attrition is a quality and cost risk wearing a productivity costume. This slide is where you tell the truth about how the results were bought.

Section D — Cost

Slide 9 — Cost & efficiency

What to show: Fully-loaded cost of support (people, tooling, AI/LLM spend, overhead), total and per-contact, trended. Break out what's fixed vs. variable. If AI reduced cost per contact, show the reopen rate and CSAT next to it — an automated "resolution" that comes back is more expensive than the human answer you skipped.

The story it tells: "We scaled the work faster than we scaled the cost, without hollowing out the quality." Cost-per-resolved-contact (excluding reopens) is the honest denominator; cost-per-contact alone rewards you for cheap answers that don't stick.

Slide 10 — Support as a profit centre

What to show: The value support returned, in the finance team's language: retention/churn on customers who contacted support vs. those who didn't, expansion and renewals influenced by support, cost avoided by deflecting avoidable volume at the source, and revenue rescued (saves, at-risk renewals turned around). Be conservative and source every number — a defensible small number beats an impressive one nobody trusts.

The story it tells: "Support isn't a cost to be minimised; it's a margin lever." Even a partial, conservative version of this slide reframes every cost number in the deck from "spend to cut" to "investment with a return."

Section E — Wins

Slide 11 — Wins & proof

What to show: Three or four wins, each with a before/after number and a named quality or customer outcome — not just "we shipped X" but "we did X, which moved [metric] from A to B and held CSAT." One concrete customer story or verbatim quote to make it stick. Credit specific people or teams by name.

The story it tells: "Here's what your investment in this org actually bought." Wins tied to numbers fund next quarter; wins tied to activity ("we ran a project") don't. Naming people also does quiet retention work in a room that decides budgets.

Section F — Risks

Slide 12 — Risks & what's fragile

What to show: The three to five things most likely to break next quarter, each with likelihood, impact, the leading indicator you're watching, an owner, and your mitigation. Include the risks created by this quarter's own wins (automation you can't yet explain, a team run hot, a backlog you deferred). Be specific about what happens if nobody acts.

The story it tells: "I see the cliffs before we drive off them, and here's what I'm doing." The risks slide is where a support leader earns trust. A QBR with no risks isn't reassuring — it reads as either not paying attention or not being honest, and it makes the ask harder to grant.

Section G — The ask

Slide 13 — The ask

What to show: One primary ask, stated as a decision, with the number attached and tied straight back to the evidence: headcount, budget, tooling, an engineering commitment to kill an avoidable-volume driver, or a policy change. State what it costs, what it returns, what happens without it, and when you need the decision. At most one secondary ask behind it.

• The ask is a decision, not a discussion ("approve X", not "let's talk about X")
• It traces to a specific slide earlier (a risk to close or a win to scale)
• Cost, expected return, and the cost of inaction are all on the slide
• There's a date by which you need the answer

The story it tells: "Given everything you just saw, here's the one decision I need from you today, and here's what it buys." A deck that reports without asking wastes the audience; the QBR exists to get this yes.

Slide 14 — Appendix: definitions & sources

What to show: How every headline metric is calculated (resolution, reopen, repeat-contact window, what "AI-handled" counts, cost inclusions), QA sample sizes and methodology, and the source for any external benchmark you compared yourself to. Keep it out of the main flow; keep it one click away.

The story it tells: "Nothing here is smoke — here's how to check any number I showed you." The appendix is what lets you say "it's in the deck" instead of arguing definitions live, and it's what makes next quarter's comparison honest.