Customer Service Pricing Models Compared
Published September 10, 2026 · Reviewed by the Fidiora team
Support software is sold on four main models: per-seat, per-conversation, per-resolution, and flat pricing. Each charges for something different, so list prices are not comparable. Convert every option to cost per resolved issue at your real volume, then compare.
Key takeaways
- Four models, four different units, and no comparable list prices.
- Seats reward stable teams, usage models reward seasonal demand.
- Flat pricing is the easiest to forecast and the quickest to outgrow.
- The unit matters more than the rate in every usage-based model.
Per-seat pricing
A fixed fee per agent licence, regardless of workload. Predictable and simple, which is why finance teams like it. Its weakness is that it disconnects cost from value entirely: a quiet month costs the same as a brutal one, and automation produces no saving until you actually reduce headcount.
Per-conversation pricing
A fee for each conversation handled. Tracks demand rather than headcount, which suits seasonal businesses. Its weakness is that outcome is not part of the unit, so an abandoned chat and a perfect answer cost the same, and session definitions vary enough between vendors to change your bill substantially.
Per-resolution pricing
A fee only when an issue is genuinely solved. Aligns vendor revenue with customer outcome, which makes the definition of a resolution the most important term in the contract. It needs a spend cap to be safe, and with one it is the most forecastable usage model.
Flat pricing
A single price for a workspace or a small team, common at the low end. Nothing to forecast and nothing to model, which is genuinely valuable for a small company. Its weakness is a hard ceiling on capability, and outgrowing it means a migration rather than an upgrade.
How to choose
Start from your shape. Stable team, steady volume, and a preference for predictability points at seats. Seasonal demand with a lean team points at usage. High repetitive volume points at outcome pricing, because that is the only model where automating work reduces the bill.
Side by side
| Criterion | Model | Best and worst fit |
|---|---|---|
| Per-seat | Charges per agent licence, regardless of workload | Best for stable teams with steady volume. Worst for seasonal demand and for automation savings. |
| Per-conversation | Charges per conversation handled, regardless of outcome | Best for seasonal businesses. Worst during incidents, and where session definitions are loose. |
| Per-resolution | Charges only when an issue is genuinely solved | Best for high repetitive volume with a lean team. Worst without a spend cap or a published definition. |
| Flat | One price for a workspace or small team | Best for very small teams. Worst once you need segmentation, routing, or reporting. |
Fidiora charges $0.59 per genuine resolution. No seat fees, no add-on modules, no channel surcharges, and nothing billed for abandoned chats, timeouts, or handoffs to a human. Set a monthly spend cap and the bill cannot exceed it.
Questions
Which support pricing model is cheapest?
Why can I not just compare list prices?
What is the most important question to ask?
Related reading
See Fidiora resolve a ticket in 60 seconds.
No credit card, no sales call required. Connect your docs and watch it work.
No credit card · Live in under an hour