White Paper

Choosing Between Per-Seat, Per-Conversation, and Per-Resolution Pricing

Published September 10, 2026 · Reviewed by the Fidiora team

Short answer

The right support pricing model depends on your ratio of agents to resolution volume, not on which vendor quotes the lowest number. Stable teams with steady volume tend to do best on seats. Lean teams with high repetitive volume tend to do best on outcome pricing. This guide walks through how to tell which you are.

Key takeaways

  • The unit each model charges for, capacity or outcome, matters more than the rate.
  • Seat pricing rewards stable headcount. Outcome pricing rewards automating repetitive volume.
  • Convert every option to cost per resolved issue at your real numbers before comparing.
  • Most teams have never actually run this comparison at their own volume.

What each model actually charges for

Per-seat pricing charges for capacity: the right for one person to log in, regardless of workload. Per-conversation pricing charges on contact, regardless of outcome. Per-resolution pricing charges only when an issue is genuinely solved.

None of these is universally better. Each rewards a different shape of business.

The decision framework

Stable team, steady volume, preference for predictability: seat pricing is a reasonable choice. Seasonal demand with a lean team: usage-based pricing tends to fit better. High repetitive volume relative to headcount: outcome pricing is usually the only model where automating work actually reduces the bill.

The deciding variable is your ratio of agents to resolution volume, which is specific to your business and not something a vendor comparison page can tell you.

Running the worked comparison

Take your monthly resolved issue count and your seat count. For a seat model, add every line: base licence, AI add-on, channel fees. For a usage model, apply the rate at your volume. Divide both by resolved issues. Now you have two versions of the same number.

This calculation frequently produces a surprise, because seat pricing hides its total across several add-on lines while usage pricing puts everything on one line.

Watch the overage terms

Committed-volume discounts become penalties during a spike unless there is a hard ceiling. Ask what happens at the cap: does it stop, throttle, or route to your team.

A spend cap is what converts a usage model from an unbounded liability into a budgeted line item most finance teams can approve.

See it in practice

Fidiora prices per genuine resolution, publishes the rate and the definition, and connects to your existing content in under an hour.

See Pricing
FAQ

Questions

Which pricing model is cheapest for a small team with high volume?
Usually per-resolution, because you stop paying for idle capacity and cost tracks the volume you actually resolve. A large team with modest volume is often the reverse case, where a few seats cover everything cheaply.
How do I compare these models fairly?
Convert each to cost per resolved issue at your real seat count and volume, including every add-on. List prices are not comparable across models because they charge for different things.
What is the biggest risk in usage-based pricing?
An uncapped bill during a spike. Ask specifically what happens when you exceed committed volume, and insist on a hard ceiling you control before signing.
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a 15-min Demo

No credit card · Live in under an hour