The unified inbox playbook for fast-growing teams
Channels, routing, SLAs, and knowledge — a 90-day sequence for taking support from chaotic to compounding.
There's a predictable inflection point in every growing company: support volume crosses a threshold where the existing setup — usually 'we all watch the inbox' — stops working. Tickets fall through cracks. Customers wait days. The team is busy but the metrics get worse.
The temptation is to hire. The right move is to instrument. Here's the 90-day sequence we use to take support teams from reactive to systemic.
Days 1–30: Consolidate
Goal: one queue, one customer record, zero context-switching. Most teams arrive with support spread across email, web chat, WhatsApp, Instagram DMs, and a few orphaned channels nobody admits to checking. Every channel has its own tab. Every tab has its own search. Customers get different answers depending on where they wrote in.
The consolidation checklist:
- Audit every channel where customers send messages today — including the ones nobody owns
- Pick one platform that ingests all of them into a single queue
- Unify on a single customer identifier (usually email + phone) so the same person doesn't appear as three different tickets
- Archive or close any channel you can't staff — fewer doors, better answers
This phase isn't glamorous. It also isn't optional. Everything in the next 60 days depends on it.
Days 31–60: Route
With one queue established, the bottleneck shifts. The team is no longer hunting for tickets — they're triaging them. Manually. All day. That's the next thing to automate.
We deploy intent classification to tag every incoming ticket (billing, technical, refund request, etc.) and skill-based routing to send each ticket to the right person or team. The goal isn't to remove humans — it's to remove the cognitive load of deciding who should handle what.
A well-routed queue cuts average handle time by 20–35% in our experience. The agents aren't faster — they're just spending their time on tickets they're equipped to solve.
Days 61–90: Knowledge
By day 60 the team has visibility and routing. What they don't have yet is leverage. Every ticket still gets answered from scratch. The hundredth password reset takes as long as the first.
The knowledge phase turns resolved tickets into reusable answers. We extract the highest-volume question patterns, write canonical responses, and wire them into both agent-assist (suggested replies) and customer-facing AI triage (deflection). By day 90, 30–50% of tickets should be answered without an agent typing a word.
"A support team without a knowledge layer is a team that solves every problem twice."
What changes after 90 days
The team stops being reactive. Volume can grow without headcount growing linearly. CSAT trends up because customers get faster, more consistent answers. And — critically — the team gets time back to work on the systemic issues that were generating tickets in the first place. That's where support stops being a cost center and starts being a product input.