A customer service organization is structured by two decisions: whether to tier and whether to specialise. Tiering splits by difficulty, so the first person triages and the second solves; specialising splits by product or channel, so each person goes deep on one thing. Most teams need one of the two by about eight people and both by about twenty. This page is those decisions with the headcount that triggers them, plus the span question that is sharper here than anywhere else in the company, because a support manager who also takes tickets is not managing.
One inbox, then a queue with an owner
Up to about four people the structure is a shared queue and a rota. The first real decision is who owns the queue's health, which is response time and backlog rather than any individual ticket. That ownership arrives before any tiering does, and putting it on the chart is what stops the queue being everybody's second priority.
Tiering: when the second line earns its place
Tier one triages, answers the common questions and escalates; tier two solves the hard ones and works with engineering. Tiering pays once the share of tickets needing deep knowledge is high enough that everyone learning everything is wasteful, usually around eight to ten people. Tier three, where it exists, is normally engineering on a rota rather than a support seat, and the chart should draw it as a dotted line into engineering rather than as a support box.
The span a support manager can actually carry
Six to eight is the same answer as everywhere else, with one difference: a support manager who is also on the queue effectively has half a week to manage, so the span should be halved or the queue time made explicit on the chart. A manager with ten reports and a ticket target is the most reliable way to lose both.
Questions people ask about customer service organizational structure
Should support specialise by product or by channel?
By product where the knowledge is deep, by channel where the tone and pace differ. Doing both under twenty people fragments the rota beyond repair.
Where does the escalation line to engineering go?
As a dotted line from tier two into engineering, with a named owner on the engineering side. An unnamed escalation path is an escalation path that ends in a group chat.
Does customer success belong in this chart?
Related but separate: success owns the relationship and the renewal, support owns the queue. Merging them on the chart hides which number each answers for.