Per-Ticket vs Per-Seat Pricing

The customer support software market is worth over $10 billion, yet almost every vendor prices the same way: per seat, per month. Zendesk, Freshdesk, Intercom, Help Scout—they all charge based on how many people you have answering tickets, not how many tickets you actually handle.

This pricing model made sense when support teams were cost centers staffed by dedicated agents. But the landscape has changed. Support is increasingly handled by product teams, engineers, founders, and AI. The line between “support agent” and “everyone else” has blurred.

So why hasn’t pricing evolved?

This guide breaks down the economics of both models, shows you how to calculate your true support costs, and helps you determine which pricing structure actually aligns with your business.

How Per-Seat Pricing Works

Per-seat (or per-agent) pricing charges a fixed monthly fee for each user who can access the support system. Prices typically range from $19 to $150+ per seat per month, depending on features.

The typical structure looks like this:

Tier	Price/Seat/Month	Features
Starter	$19-29	Basic ticketing, email
Professional	$49-79	Automation, reporting
Enterprise	$99-150+	Custom workflows, SLA, SSO

The appeal is predictable costs. If you have 5 support agents, you pay for 5 seats. Simple.

Who benefits from per-seat pricing:

• Large support teams with dedicated agents who handle high volumes
• Businesses with stable, predictable support demand
• Companies where support is a distinct department, not distributed across roles

The model assumes support is performed by a defined group of people whose primary job is handling tickets. For traditional helpdesks, this makes sense.

Where Per-Seat Pricing Breaks Down

The per-seat model has a fundamental flaw: it charges for capacity, not usage. This creates several problems for modern businesses.

Problem 1: The “Light User” Tax

Not everyone who needs support access is a full-time agent. Consider who might need to respond to tickets:

• Engineers triaging bug reports
• Product managers handling feature requests
• Founders responding to VIP customers
• Sales teams managing pre-sales questions
• Success managers handling account issues

Under per-seat pricing, each of these people needs a seat—even if they only handle a few tickets per month. A PM who responds to 10 tickets monthly costs the same as an agent handling 500.

At $79/seat, giving 10 people “occasional access” costs $790/month—regardless of actual usage.

Problem 2: Growth Penalty

Per-seat pricing scales with team size, not business growth. As your company grows, you need more people touching support:

• More engineers for technical escalations
• More product people for feedback loops
• More regional staff for timezone coverage

Each addition increases your support software bill, even if total ticket volume stays flat. You’re penalized for distributing support responsibility—the opposite of what modern companies should do.

Problem 3: Seat Gymnastics

When seats are expensive, teams develop workarounds:

• Shared logins (security risk, no accountability)
• Gatekeeper agents who relay information (slower resolution)
• External tools for collaboration (context fragmentation)
• Delayed responses waiting for the “right” person to be available

These workarounds degrade support quality while adding hidden operational costs that don’t show up on the software bill.

Problem 4: AI Disruption

AI is fundamentally changing support economics. When AI can handle 30-50% of tickets automatically, what happens to your per-seat costs?

You still need the same number of seats for human oversight and escalations, but your cost-per-resolution skyrockets because humans now handle only the hardest tickets. The efficiency gains from AI don’t translate to software savings.

Per-seat pricing was designed for a world where humans handled every ticket. That world is ending. For a deeper dive into this shift, see Why AI Makes Per-Seat Pricing Obsolete.

How Per-Ticket Pricing Works

Per-ticket pricing charges based on actual usage—the number of tickets created, not the number of people who might respond to them.

A typical structure looks like this:

Tier	Monthly Fee	Included Tickets	Overage
Free	$0	100	—
Starter	$29	1,000	$0.02/ticket
Pro	$99	10,000	$0.02/ticket
Enterprise	$499	100,000	Custom

The key difference: unlimited users are included. Your entire team can access the system without incremental cost. You pay for what you use.

Who benefits from per-ticket pricing:

• Distributed support models where many people handle tickets
• Businesses with variable or seasonal support volume
• Multi-brand operators managing several products or clients
• Companies investing in AI and automation

The Economics: A Side-by-Side Comparison

Let’s run real numbers across different scenarios.

Scenario 1: Small SaaS Startup

Profile: 500 tickets/month, 3 dedicated support people, 5 engineers/PMs who occasionally help

Per-Seat Model (Professional tier at $79/seat):

• 3 full-time agents: $237/month
• 5 occasional users: $395/month
• Total: $632/month
• Cost per ticket: $1.26

Per-Ticket Model (Starter tier at $29/month for 1,000 tickets):

• Base fee: $29/month
• All 8 users included
• Total: $29/month
• Cost per ticket: $0.06

Savings: $603/month (95%)

Scenario 2: Growing E-commerce Brand

Profile: 3,000 tickets/month, 5 support agents, 8 other team members needing access

Per-Seat Model (Professional tier at $79/seat):

• 13 seats: $1,027/month
• Cost per ticket: $0.34

Per-Ticket Model (Pro tier at $99/month for 10,000 tickets):

• Base fee: $99/month
• All 13 users included
• Total: $99/month
• Cost per ticket: $0.03

Savings: $928/month (90%)

Scenario 3: Agency Managing 20 Client Brands

Profile: 8,000 tickets/month total across clients, 4 support staff, 15 client contacts needing visibility

Per-Seat Model (Professional tier at $79/seat):

• 19 seats: $1,501/month
• Cost per ticket: $0.19

Per-Ticket Model (Pro tier at $99/month for 10,000 tickets):

• Base fee: $99/month
• All 19 users included
• Total: $99/month
• Cost per ticket: $0.01

Savings: $1,402/month (93%)

Scenario 4: High-Volume Enterprise

Profile: 50,000 tickets/month, 25 dedicated support agents, 10 managers/specialists

Per-Seat Model (Enterprise tier at $129/seat):

• 35 seats: $4,515/month
• Cost per ticket: $0.09

Per-Ticket Model (Enterprise tier at $499/month for 100,000 tickets):

• Base fee: $499/month
• All 35 users included
• Total: $499/month
• Cost per ticket: $0.01

Savings: $4,016/month (89%)

When Per-Seat Wins

Per-seat pricing can be more economical when:

• You have very few users (1-2 people)
• Ticket volume is extremely high relative to team size
• You need enterprise features only available in per-seat products

Break-even example: At $79/seat with 2 users ($158/month) vs. $99/month per-ticket, the per-seat model wins if you handle fewer than ~1,000 tickets and don’t need additional user access.

But this scenario is increasingly rare. Most businesses have more people who should have support access than currently do.

The Hidden Costs You’re Not Counting

Software pricing is only part of the equation. Per-seat models create hidden operational costs that don’t appear on any invoice.

Resolution Time Overhead

When support access is restricted, tickets take longer to resolve:

• Escalation delays: Waiting for the one person with access
• Context handoffs: Explaining the issue to someone who can respond
• Back-channel communication: Slack threads, emails, meetings about tickets

Studies show cross-functional tickets take 2-3x longer when access is gated. If your average ticket costs $15 in labor and you add 30 minutes of coordination overhead, that’s $7.50 per ticket in hidden costs.

Knowledge Fragmentation

When engineers can’t see support tickets directly:

• They miss patterns in bug reports
• Product decisions lack customer context
• The same questions get re-answered

This isn’t quantifiable on a spreadsheet, but it compounds. Teams with shared support visibility ship better products.

Customer Experience Degradation

Customers notice when they’re being bounced around:

• “Let me check with engineering and get back to you”
• “I’ll need to escalate this to someone with access”
• “Can you explain the issue again for my colleague?”

Each handoff erodes trust. In competitive markets, support experience is a retention factor that’s hard to measure but expensive to lose.

Calculating Your True Cost Per Ticket

To compare pricing models accurately, calculate your fully-loaded cost per ticket. For a detailed walkthrough, see How to Calculate Your True Cost Per Support Ticket.

True Cost = (Software + Labor + Overhead) / Tickets Resolved

Software costs:

• Monthly subscription
• Per-seat fees for all users
• Add-on costs (integrations, storage, etc.)

Labor costs:

• Agent time × hourly rate
• Specialist escalation time
• Manager review time

Overhead costs:

• Coordination time (meetings, handoffs)
• Tool switching (looking up info elsewhere)
• Duplicate work (re-explaining context)

Most companies only track software costs. When you add labor and overhead, the picture changes dramatically.

Example calculation:

Cost Component	Per-Seat Model	Per-Ticket Model
Software	$632/month	$29/month
Labor (same)	$8,000/month	$8,000/month
Overhead	$1,200/month*	$400/month*
Total	$9,832/month	$8,429/month
Tickets	500	500
Cost/ticket	$19.66	$16.86

Overhead estimated at 15% of labor for restricted access, 5% for open access

The software “savings” from a cheaper per-seat tier often disappear when you account for operational friction.

The Strategic Case for Per-Ticket Pricing

Beyond raw economics, pricing model choice signals how you think about support.

Support as a Product Feature

Per-ticket pricing treats support as a product capability, not a cost center. When everyone can participate without incremental cost, support becomes:

• A feedback loop that improves your product
• A competitive advantage that differentiates your offering
• A shared responsibility across the organization

Companies that embed support into their product DNA—Stripe, Linear, Notion—understand this. Support isn’t separate from the product; it’s part of what makes the product good.

Alignment with Modern Operations

Modern software companies don’t have rigid departmental boundaries:

• Engineers deploy and support their own services
• Product managers talk directly to users
• Founders stay close to customer pain

Per-ticket pricing aligns with this reality. Per-seat pricing fights against it.

Future-Proofing for AI

As AI handles more tickets, your economics should improve. Per-ticket pricing ensures they do:

• AI resolves 40% of tickets automatically
• Your ticket count (and costs) drop proportionally
• Human agents focus on complex issues

Per-seat pricing captures none of this efficiency. You pay the same whether AI handles 0% or 50% of volume.

Making the Switch: What to Consider

If you’re evaluating a move from per-seat to per-ticket pricing, consider:

Data Migration

• Can you export ticket history?
• Will integrations (email, Slack, CRM) transfer cleanly?
• What’s the learning curve for your team?

Feature Parity

Per-ticket vendors may be newer and have fewer features. Audit your requirements:

• Do you actually use the advanced features you’re paying for?
• Are “missing” features truly necessary or just familiar?
• What features matter for your specific workflow?

Stakeholder Buy-In

Switching tools requires change management:

• Train the team on new workflows
• Update documentation and processes
• Set expectations for the transition period

Trial Period

Run both systems in parallel if possible:

• Forward tickets to the new system
• Compare resolution times and team feedback
• Validate cost projections with real data

Conclusion: Pricing Should Match Value

Per-seat pricing made sense when support was a specialized function performed by dedicated agents using complex software. For that model, charging per user was logical.

But support has evolved:

• It’s distributed across roles, not siloed in a department
• It’s embedded in products, not handled through separate portals
• It’s increasingly automated, with humans handling exceptions

Pricing should evolve too.

Per-ticket pricing aligns costs with value. You pay for tickets resolved, not seats occupied. Your whole team can participate without penalty. Your costs scale with actual usage, not hypothetical capacity.

For startups, agencies, e-commerce brands, and multi-product companies, this model delivers dramatically better economics—often 80-95% lower software costs with improved operational efficiency.

The question isn’t whether per-seat pricing is “wrong.” It’s whether it’s right for your business, with your team structure, handling your support volume.

Run the numbers. You might be surprised.

---

Calculate Your Potential Savings

Ready to see how per-ticket pricing would work for your business?

Quick estimate: Take your current monthly support software spend, count everyone who should have access (not just who currently does), and multiply seats by $29-99 depending on your current tier. Compare that to a per-ticket model where all users are included.

For most businesses, the math speaks for itself.

Get started with Dispatch Tickets and see the difference per-ticket pricing makes.