Zendesk Cost per Ticket: How to Calculate and Reduce Support Costs
Knowing your cost per ticket turns support from a cost center into a measurable operation. It helps you justify headcount, evaluate tool investments, and spot inefficiencies. But calculating it accurately — especially for Zendesk-based teams — requires the right inputs and a consistent formula. This guide walks through how to calculate cost per ticket, what benchmarks to expect, and the most effective levers for reducing it.
What cost per ticket means
Cost per ticket is the total cost of your support operation divided by the number of tickets resolved in that period. It’s a blended metric that captures agent time, tooling, overhead, and infrastructure — everything it takes to close a ticket.
For the full definition and formula, see cost per ticket in the glossary.
The key nuance: cost per ticket is not the same as cost per contact. A single issue often generates multiple contacts (replies, follow-ups, reopens). Industry data suggests an average of 2.3 contacts per issue, meaning your true cost per resolution is roughly 2× your cost per individual reply.
How to calculate cost per ticket for your team
Step 1: Total your support costs
Add up everything your support function spends in a month:
| Cost category | What to include | Typical share |
|---|---|---|
| Labor | Salaries, benefits, payroll taxes, bonuses | 60–80% |
| Technology | Zendesk licenses, add-ons (Explore, AI), telephony, other tools | 10–20% |
| Overhead | Office space, equipment, management allocation | 5–15% |
| Training | Onboarding, ongoing training, QA programs | 2–5% |
Don’t forget Zendesk-specific costs: Suite licenses run $55–$169/agent/month depending on plan, plus add-ons like Advanced AI ($50/agent/month) and usage-based telephony charges.
Step 2: Count resolved tickets
Pull your monthly solved ticket count from Zendesk Explore. Use solved tickets (not created tickets) so you’re matching cost to output.
Filter out: - Auto-closed spam tickets - Merged duplicates (count as one resolution) - Internal/test tickets
Step 3: Divide
Cost per Ticket = Total Monthly Support Costs ÷ Tickets Resolved That Month
Example: A team of 5 agents with $45,000/month in total costs resolving 1,800 tickets = $25 per ticket.
Step 4: Track monthly
Add cost per ticket to your monthly support metrics dashboard or support metrics for executive reporting. The trend matters more than any single month — seasonal volume swings and one-time costs can make individual months misleading.
Cost per ticket benchmarks
Benchmarks vary significantly by industry, channel mix, and product complexity:
| Segment | Typical cost per ticket |
|---|---|
| E-commerce (simple) | $3–$8 |
| SaaS (standard) | $15–$30 |
| B2B SaaS (complex) | $25–$50 |
| Enterprise / high-touch | $40–$80+ |
By channel:
| Channel | Typical cost |
|---|---|
| Self-service / help center | $0.10–$0.50 |
| Chat / messaging | $3–$8 |
| $5–$15 | |
| Phone | $12–$25 |
If your cost per ticket is well above your segment benchmark, focus on the drivers below. If it’s below benchmark, verify you’re not underinvesting in quality — check CSAT and reopen rate alongside cost.
What drives cost per ticket up
Understanding the drivers helps you target the right levers:
- High average handle time — More agent minutes per ticket = higher labor cost per ticket. See how to measure and optimize AHT.
- High escalation rate — Escalated tickets involve multiple agents, each adding time and cost. See escalation rate report.
- Low first contact resolution — Multiple contacts per issue multiply the cost. Each reopen or follow-up adds agent time.
- Expensive tooling — Zendesk add-ons, telephony, and AI features add per-agent or per-resolution costs that directly increase cost per ticket.
- High turnover — Recruiting and training new agents is expensive, and new agents have higher AHT during ramp-up.
How to reduce cost per ticket
1. Increase self-service deflection
Every ticket deflected to self-service costs a fraction of an agent-handled ticket. Focus on: - Writing help articles for your top 10 ticket categories - Enabling Zendesk’s article suggestions on the ticket form - Using chatbots for FAQ-level questions
See self-service rate and ticket deflection in the glossary for measurement approaches.
2. Improve first contact resolution
Solving the issue on the first reply eliminates follow-up costs. Key tactics: - Ask for all relevant info upfront (ticket forms with required fields) - Give agents decision authority for common requests (refunds, extensions) - Build macros for the top 20 ticket types
3. Optimize handle time
Reduce the active time per ticket without rushing agents: - Internal knowledge base for fast lookups - Canned responses and templates - Skill-based routing so the right agent gets the ticket first
See how to measure and optimize AHT.
4. Reduce escalations
Each unnecessary escalation adds cost. Track escalation reasons and build tier-1 capability for the most common ones. See escalation rate report.
5. Right-size your tool stack
Audit your Zendesk add-ons and third-party tools quarterly. Are you paying for features no one uses? Could a simpler tool do the job? For small teams, a focused analytics tool like TicketBoard can replace expensive Explore Professional or Enterprise plans.
Common mistakes
- Not including all costs — If you only count salaries, your cost per ticket looks artificially low. Include tooling, overhead, and training for an honest number.
- Using created tickets instead of solved — Created ticket count doesn’t match the work done in that period. Some created tickets are still open; some solved tickets were created last month. Use solved tickets for the denominator.
- Comparing across different team structures — A team with dedicated QA, training, and management has higher cost per ticket than a team where agents do everything. That’s not inefficiency; it’s a different operating model. Compare like with like.
- Optimizing cost at the expense of quality — Cost per ticket is a ratio. You can lower it by cutting quality (shorter replies, faster closes), but that shows up in higher reopen rate, lower CSAT, and eventually customer churn. Always track cost alongside quality metrics.
FAQ
How often should I calculate cost per ticket? Monthly is standard. Quarterly for executive reporting, with monthly tracking for operational decisions. Weekly is overkill unless you’re in a cost-reduction initiative.
Should I calculate cost per ticket by channel? Yes, if you have the data. Channel-level cost per ticket reveals where automation and self-service have the highest ROI. Phone and email are typically the most expensive; chat and self-service the cheapest.
How does automation affect cost per ticket? Automation can dramatically lower cost per ticket — AI resolutions in Zendesk cost $1–$2 per resolution vs $15–$30 for agent-handled tickets. But watch for deflection quality: if automated responses cause more reopens or frustrate customers, the net savings shrink.
What’s the relationship between cost per ticket and team size? More agents increase total cost but also increase capacity. Cost per ticket stays flat if you scale proportionally. It decreases when you add automation or self-service, because you handle more tickets without proportional cost increases.