Choosing between per-ticket vs per-agent pricing shapes your entire outsourcing budget. Consequently, getting this decision wrong can cost tens of thousands of dollars a year in hidden fees or wasted agent capacity.
Industry benchmarks put fully-loaded in-house agent costs at roughly $73,590 per year in the US, compared to around $21,120 offshore. That gap is exactly why outsourcing vendors compete hard on pricing structure. However, the structure they choose changes what you actually pay.
What Is Per-Ticket Pricing?
Per-ticket pricing charges a flat or tiered rate for every resolved contact, regardless of how long it takes. Therefore, your monthly bill scales directly with ticket volume rather than headcount.
- Best for: predictable, high-volume, low-complexity tickets
- Typical range: $6–$13 per ticket for offshore Tier 1 support
- Risk: costs spike unexpectedly during volume surges
Additionally, per-ticket models can incentivize vendors to close tickets quickly rather than thoroughly, so quality clauses in the contract matter as much as the rate itself.
What Is Per-Agent Pricing?
Per-agent pricing means you pay a fixed monthly or hourly rate per dedicated seat, independent of ticket volume. As a result, costs stay predictable even when demand fluctuates.
- Best for: complex, high-touch, or specialized technical support
- Typical range: varies widely by region, skill tier, and shift coverage
- Risk: you pay for idle capacity during slow periods
Meanwhile, per-agent contracts generally give you more control over training, escalation paths, and dedicated IT helpdesk support workflows than transactional per-ticket arrangements.
Per-Ticket vs Per-Agent: Side-by-Side Comparison
| Factor | Per-Ticket | Per-Agent |
|---|---|---|
| Cost predictability | Low — scales with volume | High — fixed per seat |
| Best fit | High-volume, routine tickets | Complex, specialized issues |
| Vendor incentive | Speed of closure | Coverage and availability |
| Idle capacity risk | None | Yes, during low-demand periods |
| Typical use case | Tier 1 helpdesk, ecommerce support | Tier 2/3, SaaS, financial services |
Hidden Costs to Watch For
Regardless of the model you pick, setup and transition costs are rarely part of the headline rate. In fact, industry data shows setup fees ranging from $5,000 to $200,000 depending on vendor size and scope.
- Onboarding and knowledge-transfer fees
- Minimum seat or ticket-volume commitments
- Escalation surcharges when tickets move beyond Tier 1
- Contract minimums (some enterprise BPOs require 50+ seats)
For a deeper look at how these numbers translate to specific channels, our technical support team can walk through a cost model built around your actual ticket mix.
Which Model Should You Choose?
If your ticket volume is predictable and mostly Tier 1, per-ticket pricing typically costs less overall. Conversely, if your product requires deep technical knowledge or account context, per-agent pricing avoids the quality trade-offs that come with pure volume-based billing.
Many growing companies land on a hybrid: per-agent pricing for a dedicated core team handling escalations, layered with per-ticket overflow support for volume spikes. Similarly, managed IT services providers often blend both models within a single contract.
How to Evaluate a Vendor’s Pricing Proposal
- Ask for the fully-loaded cost per ticket or per seat, including setup fees
- Confirm what counts as a “resolved” ticket in per-ticket contracts
- Check minimum commitments and early-termination penalties
- Request CSAT and first-contact-resolution benchmarks tied to the pricing model
Ultimately, the cheapest rate on paper isn’t always the cheapest outcome. According to industry cost-per-ticket benchmarking data, outsourcing cuts costs by 41–73% versus fully in-house teams, but only when the pricing model matches the actual support workload.
SupportSave structures pricing around your ticket mix and complexity rather than a one-size-fits-all rate, so you’re not overpaying for idle seats or underpaying for the support quality your customers need.