Per Seat vs Per Ticket Pricing Explained
Choosing between per-seat and per-ticket pricing can change your support budget dramatically. This guide breaks down how each model works and when each makes sense.
On this page
Support teams often face a choice between two common billing models: per‑seat (also called per‑agent) and per‑ticket. The model you pick determines how costs scale as your volume or headcount changes. This article defines each approach, explains how the math works for typical small teams, and highlights situations where one model fits better than the other.
What Is Per‑Seat Pricing
Per‑seat pricing charges a fixed amount for each active support agent, regardless of how many tickets that agent handles. Most vendors set a monthly or annual rate per seat, and the total bill grows linearly with the number of agents you add.
Typical characteristics:
- Predictable monthly cost if headcount stays stable.
- Cost rises when you hire, even if ticket volume stays flat.
- Often includes a base feature set; advanced features may require higher‑priced tiers.
For example, several per‑seat plans start at $15 per agent per month (Freshdesk, HubSpot Service Hub, LiveAgent). A five‑person team on such a plan would pay a multiple of the per‑agent price, and adding a sixth agent adds another $15 regardless of workload.
What Is Per‑Ticket Pricing
Per‑ticket pricing bills you for each incoming support request, usually on a monthly basis. The per‑ticket rate may decrease at higher volumes, but the core idea is that cost tracks ticket count, not headcount.
Typical characteristics:
- Costs align with actual support demand.
- No penalty for adding agents, but spikes in tickets raise the bill.
- May include a base fee plus a per‑ticket charge.
Gorgias uses a per‑ticket model, though exact rates vary by plan.
When Each Model Makes Sense
Per‑seat works well when:
- Your team size is stable and you want predictable budgeting.
- Agents handle a high volume of tickets each, so a per‑ticket cost would be high.
- You prefer a simple invoice that does not fluctuate month to month.
Per‑ticket works well when:
- Ticket volume is low or highly seasonal, so you pay less during quiet periods.
- You rely on a small core team but occasionally bring in contractors; you avoid extra seat fees.
- You want costs to reflect actual support load rather than headcount.
Flat‑Rate Alternatives
Some vendors offer flat‑rate pricing, where a single monthly fee covers the team without per‑agent charges. Flat rates can simplify budgeting for growing teams that expect both headcount and volume to increase. NeuraDesk uses a flat‑rate model with no per‑agent fees and no surprise bills.
Quick Decision Checklist
- Estimate your average monthly ticket volume.
- Count current and planned support agents.
- Calculate monthly cost under each model using vendor starting prices.
- Consider seasonality: will volume swing widely?
- Factor in feature needs: some advanced features are locked to higher tiers in per‑seat plans.
- Check contract flexibility: can you switch models without penalty?
If you want a simple flat‑rate help desk you can try NeuraDesk free.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free