Pay Per Ticket Outsourcing
Definition
Pay Per Ticket Outsourcing
Pay per ticket outsourcing charges an agreed amount for every support ticket a provider handles, so the invoice tracks demand rather than headcount. Whoever controls the ticket count controls the bill, which is the tension the contract has to manage.
It is the default commercial model for outsourced service desks, because ticket systems already count everything and both sides can read the same report.
The arithmetic is simple — the counting rules are not. Reopens, splits, merges, duplicates and auto-generated alerts all change the number without changing the work.
Then there is the deflection paradox. The buyer wants fewer tickets and the provider is paid for more, and no amount of goodwill resolves that on its own.
Key takeaways
- Counting rules matter more than the unit price in almost every contract.
- Reopens, merges, splits and machine-generated tickets need explicit treatment.
- A deflection incentive is required, or the provider is paid to leave demand in place.
- Complexity banding prevents a password reset carrying the same price as an outage.
How it works
The model needs a counting convention before it needs a rate. Every contract should state what creates a billable ticket, what merges into an existing one, how a reopen is treated, and whether automated alerts count at all.
Complexity banding comes next. Most service desks band tickets into two or three tiers, so investigation-heavy work is not priced identically to a routine request.
Volume bands then handle scale. Unit rates usually step down as monthly volume rises, which protects the provider’s fixed cost at low volume and rewards the buyer at high volume.
Public procurement solved the commitment half of this long ago. Indefinite-quantity contracts must state a minimum, and “the minimum quantity must be more than a nominal quantity, but it should not exceed the amount that the Government is fairly certain to order”.
| Counting question | Common default | Better treatment |
|---|---|---|
| Reopened ticket | Billed again | Free inside the reopen window |
| Merged duplicates | Billed separately | One billable ticket |
| Monitoring alerts | Billed as tickets | Excluded unless actioned |
| Split escalation | Two tickets | One ticket, higher band |
| Cancelled request | Billed | Not billable |
Deflection needs its own clause. The UK Sourcing Playbook’s instruction that contracts should “minimise perverse or unintended incentives” applies squarely here — volume-based payment rewards the wrong direction of travel.
The usual fix pays the provider a share of the reduction, or holds the monthly fee flat while volume falls. Either way the saving has to be shared — or it will not happen.
Examples
Ticket pricing behaves well in mature service desks with clean data and badly wherever the ticketing system is an afterthought. These four cases show both, plus one contract that fixed the deflection problem properly.
A manufacturer outsources its IT service desk at a banded rate across three tiers. Volumes are audited monthly against the provider’s export, and disputes are rare because the counting rules are written.
A logistics firm counts every monitoring alert as a billable ticket. The provider’s invoice doubles in a month when a flapping sensor generates several thousand alerts nobody reads.
A retailer signs a flat per-ticket rate with no bands. Complex point-of-sale failures and password resets are priced identically, and the provider quietly prioritises the easy queue.
An insurer adds a deflection share to its contract: the provider keeps 40% of the saving from any validated reduction in ticket volume. Self-service adoption rises in two quarters.
Related terms
Service-desk pricing sits alongside several measures and delivery terms that use the same vocabulary. The entries below separate the billing unit from the things people count with it.
- Support ticket: the record that becomes the billing unit here.
- Ticketing outsourcing: the service being bought, whatever the pricing model.
- Ticket deflection rate: the measure a deflection clause is written against.
- Open ticket: the unresolved backlog this model does not price.
- Service desk outsourcing: the broader function, including problem and change work.
- Helpdesk outsourcing: the narrower first-line service.
- Cost per resolution: what the buyer should measure alongside the per-ticket price.
FAQ
What creates a billable ticket?
Only what the counting convention says. A good contract names the creating events, excludes duplicates and unactioned alerts, and states how reopens and merges are treated.
Should reopened tickets be charged again?
Not inside the reopen window. Charging for a reopen pays the provider twice for one piece of work and removes the incentive to fix it properly first time.
How do you stop volume being inflated?
Audit the export, exclude machine-generated records, and put a deflection share in the contract. Counting rules on their own do not change behaviour.
Is banding really necessary?
Yes, wherever the ticket mix is varied. A single rate across resets and outages guarantees that one of the two is mispriced, usually the complex one.
What happens when volume falls?
Rates should step up as volume drops through the bands, or the provider loses its fixed-cost recovery. Buyers who ignore this find the provider renegotiating mid-term.
How does this differ from pay per resolution?
Per-ticket pays on arrival, per-resolution pays on closure. A single issue that spans several tickets costs more here and less under resolution pricing.
Shortlist service desk partners who publish their counting rules in the Outsource Accelerator directory.
Independent
