Customer service org chart example
A customer service department of about twenty-five for a direct-to-consumer company, drawn the way a support floor actually runs: team leads with their agents stacked beneath them, a second tier for the hard cases, and the three small functions — quality, training, workforce management — that decide whether the floor is any good, kept beside the teams rather than under them.
How a customer service department is usually structured
Customer service reports to a chief operating officer in most companies, to a chief customer officer in the ones that have decided it is a growth function, and to sales or marketing in the ones that have not decided. Draw the executive either way. The head of customer service under them holds the floor through a support manager and holds the functions that judge the floor directly, which is the one structural decision that matters on this chart.
The floor is teams. A team lead holds twelve to eighteen agents, drawn stacked because a row of fifteen agents is a wall and a column is a team; two or three team leads report to a support manager, who owns the schedule and the service level for the day. Tier two — the agents who take the escalations, the refunds above a threshold, the technical cases — is a small team of its own under the same manager, and its title is the tier: it is not a layer above the frontline, and drawing it as one is the most common way a support chart invents a hierarchy the floor does not have.
Quality, training and workforce management are the department's instruments. Quality reviews calls and tickets and scores them; training turns the scores into the next class; workforce management forecasts the volume and writes the schedule. All three report to the head of customer service, not to the support manager whose teams they measure. Beside them sits the knowledge specialist who keeps the help center and the macros current, with a dotted line to product, because the answers change when the product does. The outsourced partner that takes overflow and the overnight queue is on the chart as a contractor under the support manager: it is a third of the volume and it should look like it.
Typical titles by level
The vocabulary these charts use, from the top down. Titles vary by country and by company; the levels don't.
| Level | Titles you'll see |
|---|---|
| Leadership | VP or Head of Customer Service, Director of Customer Support, Chief Customer Officer (where the function is executive) |
| Managers | Customer Support Manager, Contact Center Manager, Quality & Training Manager, Workforce Management Manager, Escalations or Tier 2 Manager, Customer Success Manager (B2B) |
| Leads and specialists | Team Lead, Supervisor, Quality Analyst, Trainer, Workforce Analyst or Scheduler, Knowledge Base Specialist, Escalations Specialist, Technical Support Specialist |
| Frontline | Customer Service Representative, Support Agent, Chat Agent, Tier 2 Agent; outsourced or overflow partner agents (as contractors) |
Where these charts go wrong
Support charts fail by drawing tier two as a layer above tier one; by splitting the floor into a phone department and a chat department; by putting quality under the support manager, so the scores grade the scorer's own teams; by leaving the outsourced partner off, so twelve people appear to answer a queue that needs twenty; and by giving one team lead twenty-five agents because the chart never showed the span.
Questions people ask
- How is a customer service department structured?
- Teams of twelve to eighteen agents under team leads, two or three team leads under a support manager, and a head of customer service above them who also holds quality, training and workforce management directly. Add a tier two team for escalations and technical cases as a peer of the frontline teams, and an outsourced partner for overflow marked as a contractor. Below about ten agents it is one team lead, one manager and everyone else on the floor.
- How many agents should a team lead have?
- Twelve to eighteen for routine, similar work, which is most of a support floor; eight to twelve for technical support where every case needs a decision. Above twenty the team lead is doing scheduling and nothing else, and the chart shows it as a column too long to read.
- Is tier 2 a level above tier 1?
- No. It is a team with a different skill set, drawn as a peer of the frontline teams under the same support manager, with the tier in the title. Escalation describes where a case goes, not who manages whom, and drawing tier two above tier one adds a layer that slows both.
- Where do quality and training sit?
- Under the head of customer service, beside the support manager whose teams they measure, never under them. Quality scores the floor; training acts on the scores; workforce management schedules it. All three need to be believed by the floor and by the manager, which they cannot be if the manager writes their reviews.
Other industries
- ManufacturingTwo shifts, and quality kept out of production's line.
- LogisticsDispatch runs the day; supervisors run the people.
- ConstructionOffice and field, meeting on every project.
- Software startupSquads under a CTO; product managers on a dotted line.
- NonprofitThe board on top, programs beside the money.
- Medical practiceA clinical line and a business line, crossing at nursing.
- SchoolDepartments led by teachers who also manage.
- HotelSix divisions around one general manager.
- Marketing agencyDisciplines own people; pods own the work.
- Security & facilities servicesSites stacked under supervisors; a 24-hour control room.
- Sales teamRegions for closers, a team for openers, RevOps beside them.
- Accounting firmA partner pyramid, three service lines.
- Law firmPractice groups, and the business side that runs the firm.
- ChurchA board that governs, a pastor who leads, ministries below.
- RestaurantFront of house and back of house, meeting at the pass.
- IT departmentRun, build and secure, under one director.
- HR departmentPartners, specialists and operations: the three legs.
- Local governmentElected above appointed, and two officers who answer to the council.
- Utility companyField crews, a 24-hour control center, and a regulator in the room.
- BankThree lines of defense, drawn as lines.
- Staffing agencySales desks, recruiting desks, and a back office that pays two thousand people.
- HospitalTwo hierarchies that meet at the bedside.
- Retail chainHead office, the field, and a store drawn once.
- Small businessOne owner, two managers, and the jobs the owner still does.
- Finance departmentAccounting closes the books; FP&A says what they mean.
- Marketing departmentDemand, product, brand, and the operations under all three.
- Engineering departmentProduct teams under a VP of engineering; platform, data and security under the CTO.
- Operations departmentSupply chain, fulfillment and the functions that keep both honest.
- Product departmentProduct, design, research and the operations that measure them.
- Consulting firmThree practices, one firm behind them, and no engagement on the chart.
- Real estate brokerageAgents who are not employees, on the chart anyway.
- Insurance agencySales on one side, service on the other, and the lines where they meet.
Or start from a structure — functional, divisional, matrix or flat — or from your own spreadsheet. The guides cover a reorg, a merger, an assistant's chart and a consultant's deliverable.
Make it yours
Download the spreadsheet, replace the names, import it — the chart redraws itself. Or start empty and drag people until it's true. Building is free at any size.