Key Takeaways
- Global customer support ticket volumes grew 16% year-over-year in 2025, with no slowdown projected for 2026
- Small businesses (under 50 employees) average 150-300 support tickets per month; enterprise organizations handle 10,000 or more
- AI chatbots and virtual agents now deflect 25-40% of tickets that would otherwise reach human agents
- Self-service knowledge bases deflect an additional 15-25% of potential contacts when well-maintained
- Average cost per ticket ranges from $6 for outsourced Tier 1 to $25-$35 for complex in-house escalations
Meta description: Real data on customer support ticket volume trends for 2026: average volumes by company size, year-over-year growth, channel distribution, AI deflection rates, cost-per-ticket benchmarks, and staffing ratios from Zendesk, Gartner, Salesforce, and Forrester research.
Customer support ticket volumes are climbing and the teams handling them are not always growing at the same rate. In 2026, the gap between inbound contact volume and available capacity is one of the more consistent pressure points for businesses at every size.
The numbers below come from Zendesk, Freshworks, Salesforce, ICMI, Gartner, and a handful of sector-specific research sources. They cover how many tickets businesses are actually handling, how that has changed year over year, how contacts are distributed across channels, and what deflection, automation, and staffing data can tell you about where the strain is showing up.
How fast are customer support ticket volumes growing?
Zendesk's 2025 Customer Experience Trends Report found that customer support ticket volumes grew 16% year over year across the businesses it surveyed. That figure aligns with Salesforce's State of Service (Seventh Edition, 2025), which found 79% of service leaders report their team is handling a higher volume of interactions than they did two years ago.
The Freshworks Customer Service Benchmark 2025, drawing on data from 37 million conversations across 17,170 businesses, found that inbound contact volume increased at an average rate of 14-18% annually for the preceding three years. The range reflects sector differences, but the directional consistency is strong.
Several factors are behind the increase:
- More digital touchpoints creating more contact opportunities
- Higher customer expectations following pandemic-era service investments
- E-commerce order volume growth continuing to generate fulfillment-related contacts
- Ticket complexity rising as simpler queries shift to self-service, leaving harder problems for human agents
- Businesses going global or into new channels expanding their addressable customer base
Zendesk's data found 53% of support teams received more tickets in 2024 than in 2023, while only 28% saw volume stay flat or decline. The gap between teams adding headcount and teams absorbing that volume growth with existing staff is widening.
Average ticket volumes by company size
Size-based volume patterns are consistent across multiple data sources, even though absolute numbers vary by industry.
| Company size | Average monthly ticket volume | Range |
|---|---|---|
| Very small (under 10 employees) | 50-150 | 10-300 |
| Small (10-49 employees) | 150-600 | 50-1,500 |
| Mid-market (50-499 employees) | 600-5,000 | 200-15,000 |
| Enterprise (500+ employees) | 5,000-50,000+ | 1,000-200,000+ |
Sources: Zendesk Benchmark Report 2025; Freshworks 2025; Help Scout State of Customer Support 2024
Zendesk's annual benchmark report segments by company tier. Small businesses (under 100 employees) averaged 22.6 tickets per agent per day, while enterprise organizations averaged 17.3 tickets per agent per day. The lower per-agent volume at enterprise scale reflects deeper specialization and tiered routing, not less total demand.
Help Scout's 2024 State of Customer Support survey, covering 1,000 or more support professionals, found that the median customer support team handles 1,200-2,400 tickets per month, which works out to roughly 40-80 tickets per business day. Industry differences explain the range more than company size does.
SaaS companies have the highest ticket density per customer, averaging 3-5 support interactions per customer per year at growth-stage companies with rapid product change (CustomerGauge 2024). E-commerce businesses trend lower at 1.5-2.5 contacts per order, but generate higher absolute volumes because of transaction frequency.
Ticket volume by channel: where contacts actually come from
Channel distribution has shifted over the past three years, driven by mobile adoption, messaging platform growth, and AI-assisted routing.
| Channel | Share of total contact volume (2025) | YoY change |
|---|---|---|
| 38% | Down 4 pts | |
| Live chat / messaging | 27% | Up 6 pts |
| Phone | 21% | Down 3 pts |
| Self-service / knowledge base | 8% | Up 2 pts |
| Social media | 4% | Up 1 pt |
| Other (SMS, video) | 2% | Flat |
Sources: Zendesk CX Trends 2025; Salesforce State of Service 2025; Freshworks Benchmark 2025
Email is still the dominant channel by raw volume, but its share is declining as messaging and chat grow. Zendesk data shows live chat and messaging now account for the fastest-growing share of first contact, particularly on mobile devices. Among businesses with customers under 40, chat and messaging now exceed email as the preferred first-contact channel.
Phone volume has declined as a share of total contacts but remains significant for complex issues. ICMI's 2024 State of Contact Center report found phone handles a disproportionate share of escalated and unresolved issues, with agents spending an average of 32% more time per phone contact than per chat or email.
Social media volumes are small in percentage terms but carry outsized visibility and response-time pressure. Sprout Social's 2025 data found 37% of consumers now use social media for customer service at least occasionally, though most still prefer direct channels for anything requiring account access or sensitive information.
How AI chatbots are affecting ticket volume
AI chatbots and virtual agents are not just changing how tickets get handled. They are reducing the number of tickets that reach human agents at all.
Gartner (2026) estimates AI chatbots and virtual agents now deflect 25-40% of tickets that would otherwise be handled by a person. Freshworks (2025) found businesses with AI in their support stack report AI handles 74% of initial live chat contacts before human handoff is needed. Salesforce (2025) found 34% of service interactions are now handled end-to-end by AI or automation, up from 17% in 2022. Zendesk (2025) found companies using AI report 35% fewer tickets reaching human agents in the categories where AI was deployed.
Worth reading that Zendesk figure carefully. The 35% reduction applies to deployed categories, not total ticket volume. Most businesses have not rolled out AI across every contact type, so the system-wide impact is lower. For businesses with well-configured AI handling their most common ticket types, though, the reduction in human-handled volume is real and measurable.
Gartner projects that by 2029, AI agents will resolve 80% of common support issues end-to-end, compared to roughly 34% today. Human agents will increasingly handle escalations, sensitive situations, and relationship management rather than high-volume routine contacts.
| AI deployment level | Ticket deflection rate | Human-handled volume reduction |
|---|---|---|
| No AI (manual only) | 0% | Baseline |
| Basic FAQ chatbot | 10-18% | Low |
| AI with NLP and knowledge base | 25-35% | Moderate |
| Full agentic AI (top-tier) | 40-60% | High |
| Projected 2029 | Up to 80% | Structural |
Sources: Gartner Customer Service AI Forecast 2026; Freshworks 2025; Zendesk 2025; Salesforce State of Service 2025
For more on how chatbot adoption is reshaping support operations, the AI chatbot adoption rate in customer service research covers the satisfaction and efficiency data in detail.
Self-service deflection: the volume reduction that often goes unmeasured
Before a ticket gets submitted, there is a chance to resolve the issue without any human or AI involvement. Well-maintained self-service resources cut inbound contact volume without the cost of an automated interaction, and most businesses are not measuring how much volume they are actually deflecting this way.
Gartner estimates self-service now handles 15-25% of potential contacts that would otherwise generate tickets. Forrester's 2024 Customer Experience Index found companies with high-quality self-service resources saw 20% lower contact rates per customer than comparable businesses without them. ICMI (2024) found 67% of customers prefer self-service over contacting a live agent for straightforward issues, but only 9% describe their experiences with self-service as excellent.
That 9% number explains a lot. Most FAQ pages and knowledge bases fail on findability and completeness. When self-service fails, the contact volume impact reverses: customers who attempt it and come up empty are more likely to call than email, generating higher-cost contacts in place of the ones they were trying to avoid.
Zendesk's Guide product data found companies with actively maintained knowledge bases (updated at least monthly with new articles based on top ticket types) deflect 22% more potential contacts than companies with static knowledge bases. The maintenance investment pays back directly in reduced inbound volume.
| Self-service maturity | Deflection rate | Notes |
|---|---|---|
| No self-service | 0% | All contacts need handling |
| Basic FAQ (static) | 5-10% | High failure rate for edge cases |
| Maintained knowledge base | 15-20% | Regularly updated, searchable |
| AI-enhanced search + content | 20-30% | Suggests articles during ticket creation |
| Full self-service portal | 25-35% | Account management + knowledge base |
Sources: Gartner 2025; Forrester CX Index 2024; ICMI State of Contact Center 2024; Zendesk Guide data 2025
Cost-per-ticket benchmarks for 2026
As ticket volumes rise and AI investment increases, cost per ticket is diverging across organizations. The gap between businesses with mature deflection strategies and those running all-human queues is growing.
The most widely cited baseline is $22 per ticket for fully loaded in-house Tier 1 support in the United States, incorporating agent salary, benefits, management overhead, office or remote infrastructure, and tooling (Unthread.io 2026; GigaBPO 2026 benchmarks).
That figure varies by tier and complexity:
| Ticket type | In-house cost per ticket | Outsourced cost per ticket |
|---|---|---|
| Tier 1 (FAQ, order status, basic troubleshooting) | $12-$18 | $6-$10 |
| Tier 2 (technical, account, billing) | $22-$35 | $10-$18 |
| Tier 3 (escalated, complex) | $35-$80+ | $20-$40 |
| AI-resolved (no human agent) | $0.25-$2.00 | N/A |
| Blended average (all tiers, in-house) | ~$22 | $6-$13 |
Sources: Unthread.io 2026; GigaBPO 2026; Gartner; TSIA State of Support Services 2024; Freshworks 2025
The TSIA State of Support Services 2024 report, which surveys technology companies specifically, found the median fully burdened cost per ticket was $24.40 for in-house Tier 1 at companies between 500 and 2,000 employees, rising to $31.70 at enterprise scale where agent seniority and specialization drive cost.
The $0.25-$2.00 range for AI-resolved tickets is worth sitting with. Gartner's estimate accounts for API costs, platform licensing, and implementation overhead amortized over volume. At scale, the cost difference between human-handled and AI-resolved tickets is roughly an order of magnitude.
For businesses evaluating the cost case for outsourcing versus in-house handling, the customer support outsourcing ROI data provides a detailed breakdown across quality, resolution, and per-ticket economics.
Staffing ratios: agents per ticket volume
How many support agents a business needs relative to its ticket volume depends on channel mix, average handle time, and how much of the load AI or self-service is absorbing.
Industry baseline figures from ICMI, Zendesk, and Help Scout 2024-2025:
- Standard email/ticket: 1 agent per 40-60 tickets per day (800-1,200 per month)
- Live chat (concurrent): 1 agent handling 2-4 simultaneous chats
- Phone: 1 agent per 40-60 inbound calls per day
- Blended (multi-channel): 1 agent per 30-50 contacts per day
The ICMI 2024 report found that the average agent handles 50 interactions per day across all channels, down from 55 in 2022. The decline reflects increasing complexity per ticket, not reduced demand. Simpler queries are moving to self-service and AI, leaving agents with more time-intensive contacts per shift.
Three adjustments matter for workforce planning. First, best-practice contact centers target 80-85% agent utilization, leaving 15-20% of time for training, quality review, and administration. Pushing past 85% correlates directly with increased agent burnout and attrition. Second, full-time equivalent agents needed per scheduled hour of coverage typically runs 1.15-1.25x the raw FTE calculation when accounting for breaks, training time, and attrition buffer. Third, for SLA-driven operations targeting 80% of tickets answered within 4 hours, Erlang C modeling typically requires 15-20% more agents than a simple tickets-per-agent calculation suggests.
| Monthly ticket volume | Estimated agents needed (email/async) | With AI deflection (30%) |
|---|---|---|
| 500 tickets | 1-2 agents | 1 agent |
| 2,000 tickets | 3-4 agents | 2-3 agents |
| 5,000 tickets | 6-8 agents | 4-6 agents |
| 10,000 tickets | 12-16 agents | 8-12 agents |
| 25,000 tickets | 28-35 agents | 20-25 agents |
Estimates assume 1 agent per 700-900 monthly tickets (email/async), 8-hour shifts, 80-85% utilization, with AI deflection applied to the reduced figures.
Year-over-year trends: what is changing in 2026
A few shifts in the data distinguish 2026 from prior years.
Average handle time across all channels increased 8% from 2023 to 2025 even as total contact volume rose (ICMI). AI and self-service are absorbing simple queries, leaving agents with a higher proportion of complex, multi-step issues. Headcount math based on historical AHT will underestimate actual capacity needs going forward.
Messaging volume is pulling away from email. Zendesk data shows live chat and messaging apps grew at 3x the rate of email volume from 2023 to 2025. WhatsApp Business, Apple Business Chat, and similar platforms are becoming primary channels for certain customer segments. Support operations not staffed for asynchronous messaging at volume are generating backlogs they cannot see in their traditional dashboards.
First contact resolution is also slipping. The SQM Group FCR Benchmark 2024 found industry average FCR at 69%, down from 72% in 2022. The decline tracks with complexity growth: agents are handling harder issues per contact, and resolution often requires cross-team coordination that stretches timelines.
Agent attrition is compounding all of this. ICMI reported average front-line agent attrition at 38% annually in 2025, meaning roughly one in three agents turns over each year. High attrition keeps teams in a perpetual onboarding cycle, which suppresses FCR and AHT performance and creates constant training overhead.
For context on how response time benchmarks and capacity planning fit into the full customer support picture, see our average customer support response times research.
Industry variation in ticket volume benchmarks
Not all sectors move at the same rate. Sector-specific data from TSIA, Salesforce, and Zendesk shows real variation.
| Industry | Avg tickets per customer/year | Cost per ticket (in-house) | AI deflection rate |
|---|---|---|---|
| SaaS / technology | 3-5 | $25-$35 | 30-45% |
| E-commerce / retail | 1.5-2.5 | $14-$20 | 25-40% |
| Financial services | 2-4 | $28-$45 | 20-30% |
| Healthcare | 1.5-3 | $30-$55 | 15-25% |
| Telecommunications | 4-7 | $18-$25 | 30-45% |
| Travel / hospitality | 2-4 | $16-$24 | 25-35% |
Sources: TSIA State of Support Services 2024; Salesforce State of Service 2025; Zendesk Benchmark 2025; CustomerGauge 2024
Financial services and healthcare have the lowest AI deflection rates despite the highest costs per ticket. Regulatory requirements and the sensitivity of account information limit how much can be handled without a human involved, which is why per-ticket costs are highest there.
Telecommunications logs some of the highest raw ticket volume per customer (4-7 contacts per year) from billing cycles, service interruptions, and device issues, but also one of the highest AI deflection rates because many contact reasons are well-structured and repeatable.
What rising ticket volumes mean for staffing decisions
Ticket volume is growing faster than most support teams are hiring. Companies are responding differently depending on their situation.
Some are scaling through outsourcing. The customer support outsourcing market grew to an estimated $132 billion in 2026 (Fortune Business Insights). Outsourced capacity adds Tier 1 handling at $6-$13 per ticket without the fixed cost of in-house headcount or the ramp time of direct hires. For a detailed look at the economics, see the customer support outsourcing ROI data.
Others are investing in AI and self-service deflection. Businesses with mature deflection strategies are handling more contacts per agent than businesses running all-human queues, and the gap is getting wider. Gartner's projection that AI-assisted operations will handle 80% of common issues by 2029 means the organizations making that investment now are building capacity advantages that will be difficult to close later.
A third group is absorbing rising volume into longer response times, which is not really a strategy so much as a default. Zendesk's 2025 data found 35% of small businesses surveyed had response times above 24 hours for email tickets. The churn risk is documented: 67% of customers cited poor service as a reason for switching vendors in 2024 (Zendesk CX Trends 2025).
For businesses evaluating staffing capacity against current volume, the benchmarks above provide a starting point. A team handling 2,000 monthly tickets with two agents is running above safe utilization if any meaningful share involves live chat or phone. A team at 5,000 tickets with six agents, without AI deflection, is likely seeing queues build.
For support on scaling customer support operations without proportional headcount increases, see what Stealth Agents offers for customer support virtual assistants.
Conclusion
Ticket volumes are up 16% year over year and the tickets themselves are getting harder. That combination squeezes capacity for teams that have not added deflection or flexible headcount to keep pace. The Zendesk growth figure is consistent with Freshworks, Salesforce, and ICMI data across thousands of companies, so it is not a platform-specific reading.
The businesses managing the pressure well tend to have multiple things working together: AI deflection keeping a significant share of tickets from reaching human agents, maintained self-service handling contacts before they are even submitted, and outsourced or scalable capacity covering the rest. That is not a checklist, it is just what the data shows for teams that are not falling behind.
The businesses absorbing volume into longer queues are building churn risk that tends to show up in retention numbers before it shows up on any support dashboard. Running these benchmarks against current staffing is usually where that gap becomes visible.
Sources: Zendesk Customer Experience Trends Report 2025; Salesforce State of Service Seventh Edition 2025; Freshworks Customer Service Benchmark Report 2025; Gartner Customer Service AI Forecast 2026; ICMI State of Contact Center 2024; SQM Group Call Center FCR Benchmark 2024; TSIA State of Support Services 2024; Forrester Customer Experience Index 2024; Help Scout State of Customer Support 2024; Unthread.io Contact Center Cost Analysis 2026; GigaBPO Industry Benchmarks 2026; Fortune Business Insights CX Outsourcing Market Report 2026; CustomerGauge B2B Support Benchmarks 2024; Sprout Social Index 2025; Gartner Agentic AI Forecast 2025; McKinsey Customer Experience Research 2024; Zendesk Guide Deflection Data 2025; LiveChatAI Cost Per Contact Study 2025.