Mike HeapMike is an experienced Product Manager who focuses on all the “non-development” areas of My AskAI, from finance and customer success to product design, copywriting, testing and more.
Table of Contents
- The AI support staffing model at a glance
- Why does the agents-per-ticket ratio stop working at 60-80% AI resolution?
- How do you forecast support headcount when AI resolves most of the tickets?
- Line 1: the AI line
- Line 2: the escalation line
- Line 3: the owner line
- Line 4: the builder line
- What does the headcount curve actually look like?
- Putting a number on each line
- What does this look like in real rollouts?
- A high-volume prop-trading platform, about 5,650 hours back a month
- A digital-goods marketplace, 1,768 hours back a month
- YouGarden, 965 hours back a month
- Apartment List, 101 hours back a month
- What to do this week
- How do I get AI to split my tickets into the four lines?
- When does this model not apply?
- The takeaway
- FAQs
Created time
Sep 23, 2026 11:48 PM
Title length (<60)
Author
Last optimised
Ecomm?
Tags
Archived
Image
Publish date
Sep 24, 2026
Video
Slug
ai-customer-support-staffing-model
Featured
Type
Article
Ready to Publish
Ready to Publish
At high volume the headcount question is how many agents you stop adding. The number to forecast off is your escalation rate, because total ticket volume stopped describing human workload.
You are holding two numbers, and both of them look defensible. One is a volume forecast, and it says tickets double next year. The other is a staffing ratio that has served the team well for years, some version of agents per thousand tickets. Multiply the two together, and you get a hiring plan (the arithmetic is fine).
That plan is wrong by a long way. In the rollouts we run, companies at volume do not tend to shed support staff; they stop needing to hire as fast as they grow. They stop hiring for seasonal peaks too, because the AI flexes with demand, at no headcount cost.
Multiply volume by a ratio, and you price in people you will never need.
I am Mike, co-founder of My AskAI. We help 200+ ecommerce and SaaS businesses run AI customer service inside Zendesk, Intercom, Freshdesk, Freshchat, Gorgias and HubSpot. Our agents have resolved more than 1,000,000 tickets, and they hold a 72%+ resolution rate on a rolling 30-day basis across the customer base. We are rated 4.5/5 on G2 across 23 reviews.
The rollouts behind this post span about 1,582 tickets a month to about 105,000, and at both ends we sized the team off the conversations that reached a person.
The AI support staffing model at a glance
Here is a 20,000-ticket book that doubles over two years, forecast against the old ratio and against the escalation line.
Two-year plan | Today | Month 24 |
Tickets a month | 20,000 | 40,000 |
AI resolution rate | 60% | 75% |
Conversations reaching a person | 8,000 | 10,000 |
Agents the escalation line needs | 20 | 25 |
Agents the old ratio would call for | 50 | 100 |
Why does the agents-per-ticket ratio stop working at 60-80% AI resolution?
TL;DR: Support headcount has been planned off one number for decades, and that number still works for the tickets a person touches. It stops working the moment most tickets never reach one, because total volume and human workload have come apart.
The conventional model is correct for the operation it was designed for. One help desk staffing guide writes it out as two formulas: "Staff hours required per month = Calls per month X Avg. call duration (min/call) / 60 minutes/hour", then "Avg. number of agents required = Total hours required / Actual hours available per agent".
That is volume multiplied by handle time, divided by the hours an agent really has. On a desk where every contact reaches a person, it is the right sum.
Larger operations reach for a heavier version of the same idea. A call center staffing guide sends the same inputs through an Erlang calculator: "Once you've collected this data, put it into an online Erlang Calculator, a tool designed to calculate the number of agents an organization needs to maintain adequate staffing." Neither the formula nor the calculator has a term for the conversations we close without a person.
The category definitions rest on the same assumption. A contact center glossary describes a call center staffing model as a framework for adding staff against call volumes and hold times.
The help desk staffing guide is candid about the limits of its method, conceding that "it is important to understand that there is no simple formula for calculating staffing levels for most help desks". It adds that while "Large call centers (greater than 25 agents) can actually use formulas developed by A. K. Erlang, a Danish mathematician", "This methodology is valuable, but it does not go far enough for the more complex Help Desk environment."
Every model above starts by multiplying total volume, and our agent resolves a large share of it before a person sees it. Total volume stops being the correct first term.
Workforce management calls this containment, and the planners who came up through IVR have been netting contained contacts out before they size a team for years. The ratio most support teams plan with has not caught up, and still multiplies the whole ticket book.
A resolution, in the way we count it, is a conversation that was never escalated to a person. Across the four rollouts in this post, the resolved share is between 58% and 76%, which is roughly three fifths to three quarters of the first term in the help desk staffing formula above. None of it is human work.
We use resolution rate, and your reporting may show a deflection figure beside it, counting the tickets nobody picked up, answered or not.
Our metrics decoder post sets containment, deflection and resolution side by side. Resolution rate here means conversations closed without a person.
A team handling 20,000 tickets a month forecasts 40,000 in two years (a normal enough two-year plan), and the ratio says double the volume, double the agents.
But if the AI resolves three quarters of that book by then, only 10,000 conversations reach a person. That is barely more than the number reaching a person today, so the team hires against 40,000 and staffs for a workload that never arrives.
The field median AI-handling rate is around 70%, and our published resolution rate is 72%. Those are two different measures: on the resolution label alone the field median is 72.5%, which puts our rate below it. Treat all of them as directional only.
Three caveats travel with any benchmark figure, ours included. They are aggregates, so nobody measured these vendors head to head. Vendors count resolutions differently, so the numbers are not strictly comparable. Published rates are a self-selected ceiling, because every vendor publishes its best rollouts.
Our AI resolution rate benchmarks post has the full corpus and those caveats. Treat a borrowed rate as an assumption to test before you plan on it.
Measure the rate you forecast off. My AskAI's Insights scores 100% of conversations for AI CSAT, where a manual review process gets through 2% to 10%.
How do you forecast support headcount when AI resolves most of the tickets?
TL;DR: The Four-Line Forecast splits support headcount into an AI line, an escalation line, an owner line and a builder line. Only the escalation line converts into hires.
We plan these rollouts off four lines, and we call the model the Four-Line Forecast. Only one of them ever turns into a hire. Another absorbs work with no hire behind it, and a third is part of one person's week.
The fourth is engineering time, measured in hours. Size the four separately, because the hiring number comes out of the escalation line.
Line 1: the AI line
This is the share of conversations the agent resolves without a person (the largest line in the forecast, and the only one that grows without a hire).
A Monday morning, a product recall or a 3am question from Australia all land on this line. Every one of them costs the same per conversation as a quiet Tuesday.
That is why the line never shows up in a requisition, and why the teams we run agents for stop staffing up for the seasonal peak. You are buying capacity by the conversation.
Line 2: the escalation line
This is everything that still reaches a person, and the only line in the forecast that hires. The old ratio works fine here, as long as you run it on just the conversations a human handles. It is the one place I still use that ratio.
Complexity drives the escalation line. Refunds outside policy, angry customers, regulated advice, the ambiguous case, anything needing a judgment call: those do not double because your marketing worked. They grow with the product and the customer base, much more slowly than the ticket count does.
The first consequence an Ops leader should price in is that the work left behind is harder. In our rollouts, the AI taking the monotonous repeats has put more intensity into the work that is left, because the people on it now only have difficult questions and problems to solve. Agents also handle more conversations each, because the volume thins before it reaches them.
The second consequence changes who does tier 1, and in our rollouts offshore teams are often doing exactly that work. When the AI absorbs it, those teams become less necessary, and escalations move to tier 2 and tier 3 inside the company. Our post on building an AI-first support team covers who you hire and what the roles become.
One implementer published a six-month field report covering SDR and level 1 support pilots across three SMB stacks, with the figures given as averages across those pilots:
"12–19% human-handoff rate with >90% CSAT on those handoffs." - u/Wednesday_Inu, r/AI_Agents
The numbers are self-reported and the businesses are unnamed: one practitioner's six-month account of a narrow, high-quality escalation line under a wide AI line.
Line 3: the owner line
Somebody has to own the AI agent, and it costs you a percentage of one person's role.
Every company we onboard needs someone to manage the agent, with a little understanding of how these systems work. They do not need to be technical, only to have time carved out and protected, written into the job as an explicit share.
Ongoing, we put that at roughly 30 minutes a week, or up to an hour if you are very involved.
The wider field has started naming this function. On r/customerexperience, one practitioner listed what the job involves:
"Someone has to monitor performance, improve prompts and knowledge, tune workflows, measure outcomes, and ensure AI is actually helping customers instead of creating more friction." - u/CryRevolutionary7536, r/customerexperience
Another in the same thread described the shift falling on people already in post:
“a few mates in CX have gone from "I handle escalations and tweak the knowledge base" to "I spend half my week babysitting the chatbot's tone of voice."” - u/PerspectiveSea9666, r/customerexperience
Half a week is more than this line should cost you. Budget it at a few hours a month and name the person. In our rollouts it stays there.
Line 4: the builder line
The fourth line is development time, counted in hours. It raises Line 1 and shrinks Line 2. Hour for hour, it is the highest-return item in the forecast.
The work your developers do here is connecting data: order status, delivery state, account and billing records. Our agent then answers from that live data. A knowledge-only agent gets between 40% and 70% resolution.
Connecting live account data takes a rollout above that band, and letting the agent perform actions takes it higher again. Those actions can run on their own, or they can propose a step for one of your people to approve. You choose that per action.
You can buy this line two ways, and we have seen both work. Carve hours out of the existing development team, or put a developer inside the support team.
Either works, and the first data connection your team builds is usually one to three hours of work.
What does the headcount curve actually look like?
Once the four lines are separate, headcount stops following volume, and the hires we do see are more senior.
In the table below we take a team from 20,000 tickets a month to 40,000 over two years, with the resolution rate climbing as the builder line delivers. One agent covers 400 escalated conversations a month: 160 hours of availability at 24 minutes of handling per escalated ticket.
We use 24 minutes as an illustration, so substitute your handle time before you use any of this. We also hold that 24 minutes constant while the resolution rate climbs, and it will not stay constant: once the repetitive tail goes, the conversations left are the hard ones. The agent counts below are a floor.
Point in the plan | Tickets a month | AI resolution rate | Conversations reaching a person | Agents the escalation line needs | Agents the old ratio would call for |
Today | 20,000 | 60% | 8,000 | 20 | 50 |
Month 12 | 30,000 | 68% | 9,600 | 24 | 75 |
Month 24 | 40,000 | 75% | 10,000 | 25 | 100 |
That is five new agents over two years. The old ratio would have had you hiring fifty.
The middle column climbs, because your resolution rate is a moving input (the builder line keeps moving it). A twelve-month plan built on today's rate over-hires.
Putting a number on each line
Four sums, in units you already have.
- The AI line - total tickets multiplied by your measured resolution rate. Price it per conversation, which is a different order of magnitude from an agent-hour. We charge a monthly plan fee, plus a per-ticket rate above an included allowance. At the volumes in this post that is the Scale plan: $499 a month, the first 2,000 credits included, and $0.10 a credit after that, where a chat ticket is about one credit and an email ticket about one and a half, with add-ons charged separately. Our first 30 days are free, with all features unlocked, unlimited tickets and no credit card.
- The escalation line - total tickets minus the AI line, divided by the conversations one agent handles a month. That second number is your real handle time, set against 160 hours of availability. It is the old ratio applied to the right numerator.
- The owner line - a few hours a month of one named person, held as a fixed share of their role. If it is growing past that, our agent needs knowledge work.
- The builder line - engineering hours, scoped as a small number of integrations. Built once, it pays back on every conversation afterwards.
Then re-read the resolution rate every quarter. It moves, and everything else in the forecast hangs off it.
On raising Line 1, the single biggest lever we see across rollouts is connecting live account data. Our User Data feature links a billing system, order database or CRM to the agent, and Tasks & Tools then lets it act on what it finds. That combination is what lifts a resolution rate above the knowledge-only band.
What does this look like in real rollouts?
TL;DR: YouGarden gets 965 hours a month back at 66% AI resolution, and Apartment List 101 hours at 76%. Across four rollouts the AI line returns 8,484 hours a month, about 53 agent-months nobody had to hire.
The four rollouts in this post run on Intercom, Freshdesk and Zendesk, at four very different volumes. Each figure below comes from that rollout's case study.
The right-hand column converts hours into agent-months. On our YouGarden write-up, 965 saved hours a month is six full-time agents, which puts the divisor at 160 hours to the agent-month.
Rollout | Helpdesk | Tickets a month | AI resolution | Hours back a month | Agent-months at 160 hours |
Intercom | ~105,000 | 73% | 5,650 | 35.3 | |
Intercom | ~36,400 | 58% | 1,768 | 11.1 | |
Freshdesk | ~12,000 | 66% | 965 | 6.0 | |
Zendesk | ~1,582 | 76% | 101 | 0.6 | |
Total | 8,484 | 53.0 |
A high-volume prop-trading platform, about 5,650 hours back a month
This one handles roughly 105,000 Intercom tickets a month, of which "roughly 76,500 are resolved by the AI with no human involved." AI CSAT holds at 68%. The rollout is anonymized at the customer's request.
For a headcount plan, the figure we care about is 5,650 hours a month, or about 35 agent-months. No hiring plan was going to produce that. At this volume the escalation line is the only staffing conversation available.
A digital-goods marketplace, 1,768 hours back a month
About 36,400 tickets a month on Intercom, 58% of them resolved by our agent, and 1,768 hours back. AI CSAT is 92% across 36,413 conversations in a 30-day window.
This is the lowest resolution rate in the set, and still the second-largest hours figure, because volume does the work. That is about 11 agent-months.
YouGarden, 965 hours back a month
YouGarden handles about 12,000 Freshdesk tickets a month at 66% AI resolution, with a peak around 82%, and 78% AI CSAT across the 11,785 tickets our agent answered. That is 965 hours a month, or six full-time agents' worth of work.
Their Head of Customer Service, Mamunur Rahman, describes the effect in staffing terms:
"My AskAI has fundamentally changed how we support our customers. The quality and consistency of responses are extremely high, and it's allowed us to scale support without compromising the experience we're known for at YouGarden." - Mamunur Rahman, Head of Customer Service, YouGarden
Apartment List, 101 hours back a month
The smallest book in the set at about 1,582 Zendesk tickets a month, and the highest resolution rate at 76%, with 97% AI CSAT. That is 101 hours a month, roughly 0.6 of an agent.
We run the same four lines on a book this small. At this size the AI line buys you cover and consistency, and the headcount decision has not arrived yet.
A resolution rate between 58% and 76% holds across a 66-fold difference in ticket volume, and the hours it returns scale straight with the book. Our case study index has the rest of them.
That hours-saved figure is ours, measured on each of the four rollouts against the conversations the agent handled.
What to do this week
TL;DR: Split last month's tickets into the four lines before you touch the hiring plan. Every other number in the forecast follows from that one.
Four actions, in order. The timings assume you export the raw data and let whichever AI tool you already have open do the sorting and grouping. That used to be an afternoon of spreadsheet work (and not a fun one).
- Split last month's tickets into the four lines - export the tags and classify each ticket against the framework: resolved without a person, escalated, owner work, builder work. About forty minutes. Outcome: you have your real escalation line, which across the four rollouts in this post is between a quarter and two fifths of total volume.
- Rebuild the hiring plan off the escalation line only - rerun your existing ratio on that numerator and nothing else. About twenty minutes once step 1 is done. Outcome: the number of hires your forecast supports, which is well below the volume-derived one. Our ROI calculator will do the same sum on your figures if you would rather not build it yourself.
- Name the AI owner and book the weekly slot - carve a share of an existing role, with 30 minutes to an hour a week in the calendar. Ten minutes to decide, five to book. Outcome: somebody owns the resolution rate, the input the whole forecast rests on. If you have not stood an agent up yet, our implementation timing post covers what the first month looks like, and the install itself is an approved helpdesk marketplace app.
- Get one data connection onto the development roadmap - pick the single question your agents answer most often from another system, usually order or account status, and scope the connection for it. An hour to specify. Outcome: a climbing resolution rate, and a twelve-month forecast that holds.
All four are tool-neutral, and you can do them inside Zendesk, Intercom, Freshdesk, Freshchat, Gorgias or HubSpot with no purchase and no vendor conversation. Our post on scaling support without hiring covers the triggers that force each hire.
How do I get AI to split my tickets into the four lines?
Step 1 is the part an AI assistant can do for you in minutes. Export last month's tickets with their tags and outcomes, paste the list into this prompt, and it will sort them into the four lines and work the escalation ratio on your own handle time. It only sees what your export records, so we ask it to mark anything your tags do not cover as unclassified and count those for you.
You are helping me rebuild a customer support staffing plan.
Here is last month's ticket export, one row per ticket, with whatever
tags, outcomes and handling times I have:
[paste your export, or the columns you can get out of your helpdesk]
Here is my support team today:
[number of agents, the hours each works a week, and who owns the AI
agent if anyone does]
Sort every ticket into one of four lines.
1. The AI line: closed without a person ever touching it.
2. The escalation line: a person handled it, including anything the AI
started and then handed over.
3. The owner line: work on the AI agent itself, such as knowledge edits,
escalation guidance changes, or reviewing what the agent answered.
4. The builder line: development work, such as connecting an order,
billing or account system to the agent.
Then give me four things.
- The count and the percentage share of each line.
- My real handle time on the escalation line only, and how many
conversations one agent covers a month against 160 hours of
availability.
- The agents my escalation line needs today, next to the agents a
total-volume ratio would have asked for.
- Those same two numbers at double my current ticket volume, first
holding my measured resolution rate flat, then with it five points
higher.
Where a ticket's tags do not tell you which line it belongs in, label it
"unclassified" and tell me how many of those there are, rather than
guessing.
Give me one table, with the assumptions you used listed underneath it.If you are already running an agent and you want to know why a given conversation went the way it did, ask Echo. It is an in-dashboard assistant that explains what the agent did and why. That beats reading transcripts, and it gets you to the answers step 1 needs.
When does this model not apply?
TL;DR: The model assumes your resolution rate can climb. Four situations where it cannot, or where the climb costs you something else, and one where the whole framework is too big for the team.
First, a low resolution rate is often a policy choice. Sofar Sounds is at 26%, and the live write-up is explicit about the mechanism: "the biggest move Sofar made was to tune our Handover & Escalation Guidance so the AI escalates ~74% of tickets to a human by design."
If your organization wants a person on most conversations, the AI line stays narrow, the curve does not flatten, and the forecast above does not describe you. Choosing that is legitimate, and the rollout is working as designed.
Second, the human job gets harder, and our model is quiet about that cost. Once the repetitive tail goes, every remaining conversation is a difficult one, so the intensity goes up and the easy tickets that used to break up a shift are gone. Price senior attrition into the escalation line.
Third, some work needs a person present, whatever your resolution rate. Voice at volume, licensed or regulated advice and thin-coverage languages all still need people, and so does a sudden seasonal surge that needs trained staff inside two weeks. Our comparison of AI against outsourcing has the numbers on those, and our post on multilingual support covers the language case.
Fourth, and the most common in our rollouts, is having nothing for the agent to read. A guide to AI support agents names the constraint: "An AI support agent is only as good as the documentation it reads."
That constraint has two parts. The first is how the agent reads your help center:
"It answers from passages, not articles. Retrieval pulls chunks of text, not whole pages." - The same guide to AI support agents
The second is what the agent does when two passages disagree:
"If retrieval surfaces contradictory passages, there is no editorial judgement available to it. It picks one, and it sounds equally certain either way." - The same guide to AI support agents
For a team with no help center, the AI line starts near zero, and the first quarter is documentation work. Training on your historic tickets gives our agent a starting point while the help center gets written. The writing still has to happen.
Last is team size. On a small team there is no curve to flatten and no hiring plan to change. The gain there is out-of-hours cover and a survivable Monday morning, which our post on AI as a shield for support teams covers.
Where the escalation policy is deliberately wide, our Internal Note Replies setup drafts a reply for one of your people to send.
The takeaway
TL;DR: Forecast four lines, hire off one of them, and expect the headcount curve to flatten.
The agents-per-thousand-tickets ratio multiplies your whole ticket book, most of which now never reaches a person.
The teams we run agents for tend to keep the staff they have. They stop adding, and the seasonal peak stops showing up in the hiring plan.
Our Four-Line Forecast is how you plan that. The AI line takes the volume, peaks included, and no part of it is a hire. The escalation line is the only one that converts into headcount, and the owner line is a share of one person's week.
The builder line is engineering hours, and we spend them pushing the resolution rate up over time.
If you do one thing this week, split last month's tickets into those four lines before you touch the plan. We plug into your existing helpdesk, and we report the resolution and handover split for you. Our page for CX and Ops leaders shows what that looks like on your volume.
FAQs
How many support agents do I need at 50,000 tickets a month?
There is no single answer, because the question depends on how many of those 50,000 reach a person. Run the standard calculation, which one help desk staffing guide writes as volume multiplied by average handle time and divided by the hours an agent has. Apply it to your escalation line. At the resolution rates we measured across the four rollouts in this post, between 58% and 76%, somewhere from 12,000 to 21,000 of those tickets reach a human. The same formula on that numerator gives a headcount a fraction of the volume-derived one.
What happens to my support headcount when AI resolves 60-80% of tickets?
It flattens. In our experience companies do not tend to get rid of staff. They do not need to hire as many as they scale, or for the peak periods in the year, because the AI agent flexes with scale and demand. The composition changes too: fewer tier-1 hires, more senior people handling the exceptions, and one named person owning the agent.
Which tickets still need a human?
By definition, whatever the AI does not resolve, and you set that boundary yourself. In our rollouts, the escalation line holds the judgment calls, the exceptions to policy, the regulated advice, the angry customer and the ambiguous request. The split is a configuration you control: escalation guidance decides what hands over and when. Two teams on similar products can run very different rates on purpose.
How do I forecast support hiring when deflection keeps rising?
Treat the rate as a moving input, and re-read it quarterly (we re-read ours on a rolling 30-day basis). Forecast the escalation line, because that is the only line that hires, and it grows with complexity while complexity moves more slowly than volume. Hold the resolution rate constant in a twelve-month plan and you will over-hire, because the builder line pushes it up over the same period. The field median AI-handling rate is around 70%, though treat that as directional only: it is an aggregate, vendors count differently, and published rates are a self-selected ceiling.
Do I stop hiring tier 1 entirely, or just hire fewer?
Fewer, and the job changes. The people who remain handle only what the AI could not, which makes for a harder week. In our rollouts it has put more intensity into the work that is left, because only the difficult questions and problems remain to solve, the things the AI could not resolve itself. Offshore tier-1 teams tend to shrink for the same reason: in the rollouts we run offshore teams can be less necessary, because they are often doing exactly those roles, with escalations moving to tier 2 and tier 3 inside the company.
What is the ratio of AI-resolved to human-handled tickets I should plan for?
Plan on your own measured rate, and use a benchmark to check it against. The field median AI-handling rate is around 70%, our published resolution rate is 72% on a rolling 30-day basis, and the four rollouts in this post span 58% to 76%. Keep the caveats with the numbers: they are aggregates, nobody measured these vendors head to head, vendors count resolutions differently, and published rates (ours included) are a self-selected ceiling. Your integrations and escalation guidance decide your number, so the only way to know it is to run it.
Reference point | Rate | What it covers |
Field median | Around 70% | Median AI-handling rate across 195 rated deployments from 38 vendors |
Our published rate | 72% | Rolling 30-day resolution rate across our customer base |
The four rollouts in this post | 58% to 76% | 1,582 to 105,000 tickets a month |
How many customer service reps per customer?
The sources that come closest to a per-customer ratio give you a calculation to run. One customer success staffing guide sizes a team "based on customer segments, the effort each requires, and the hours CSMs actually have available." That is the right instinct and it transfers directly: segment your contacts by effort, work out how many hours each segment consumes, and divide by the hours one person really has. With an AI agent in place, apply it only to the conversations that reach a person.
