Help Desk Cost per Agent vs Ticket: Calculate the Tradeoff
Compare seat and ticket billing with quotas, overage, seasonal demand and AI charges. Work out a break-even point using explicit assumptions.
Seat pricing follows the number of paid users; ticket pricing follows the vendor's definition of billable support activity. The cheaper model depends on staffing, contact volume and required features. Compare equivalent workflows over a normal month and a busy month before comparing annual totals.
Define the units before multiplying
Zendesk's public pricing uses per-agent subscription prices and distinguishes annual billing from monthly terms. Gorgias's billing documentation instead defines billable helpdesk tickets around an outgoing message, including messages from agents, AI Agent or rules. Multiple replies in that ticket are not automatically multiple billable tickets.
| Seat model inputs | Usage model inputs |
|---|---|
| Paid responder and administrator seats | Included ticket quota |
| Price for the required plan | Definition of a billable ticket |
| Seat minimum and billing commitment | Overage price and commitment |
| Collaborator roles and add-ons | Separate AI and channel usage charges |
Count internal specialists separately from customer responders. Help Scout's role documentation, for example, distinguishes Light Users who can collaborate internally from users who reply to customers. Price each colleague by role and plan access.
Work out an illustrative break-even point
Assume a seat-based option costs $50 per paid agent per month. Eight agents cost $400. Assume a usage-based option costs $250 monthly including 1,000 billable tickets, with $0.30 per extra ticket. These are invented calculation inputs, not quoted vendor prices.
- At 800 tickets, the usage option costs $250; the seat option costs $400.
- At 1,500 tickets, usage costs $250 + 500 × $0.30 = $400.
- At 2,000 tickets, usage costs $250 + 1,000 × $0.30 = $550.
Under those assumptions, 1,500 tickets is the monthly break-even point. It applies only above the included quota and only while the other costs remain equal. Adding four temporary agents raises the assumed seat bill to $600 if those seats can be bought for that month; the usage bill stays tied to tickets. Check minimum terms before using that staffing scenario.
Model the year and add the missing components
Use your monthly history rather than multiplying a quiet month by twelve. For an illustrative year with ten months at 800 tickets and two at 2,000, the assumed usage cost is 10 × $250 + 2 × $550 = $3,600. Eight constant seats at the assumed $50 cost $4,800. Neither number includes AI, channels, implementation or taxes.
Add required AI usage, telephony, messaging, integration fees and implementation separately. A ticket-based plan does not make all activity free, and AI automation does not necessarily eliminate the base ticket charge. Use the AI pricing guide for that second layer. Compare final scenarios on the relevant Zendesk and Gorgias pricing pages.
Frequently asked questions
Should we use all incoming messages as ticket volume?
Use the vendor's billable-event definition. Messages, conversations and chargeable tickets can produce different counts.
Which model should we choose?
Choose the lowest complete cost among products that meet the required workflow. Use a peak scenario to check budget exposure and your own history to estimate the likely annual bill.