unitcostai

AI + Human Ticket Cost

What happens to ticket cost when AI hands some cases to humans?

How this tool works

This cost model weights fully deflected tickets against tickets that still escalate after an AI first pass, then reports the blended cost per resolved ticket and monthly impact.

How It Works

  1. Set ticket volume, human baseline cost, and escalated-ticket handling cost.
  2. Set AI cost for deflected tickets and AI requests before handoff on escalations.
  3. Review blended ticket cost, monthly savings, and the cost share still driven by human escalation.

Formula

blended_cost = deflection_rate * ai_deflected_cost + (1 - deflection_rate) * (ai_before_handoff + human_escalation_cost)

Assumptions and Units

  • Currency: USD
  • Unit of analysis: resolved support ticket
  • Deflection rate is the share of tickets fully resolved without human handoff
  • Escalated tickets still include AI first-pass cost before the human handling term is added
  • Pricing source: daily pricing snapshot in repo, no runtime scraping

Related resources: AI Ticket Cost, AI Payoff Point, AI Support Deflection Rate, AI Support Agent Cost per Ticket, What Cache Hit Rate Means for RAG, How To Estimate Requests Per User/Month.

Pricing snapshot: 2026-05-03Provider: OpenAIModel: GPT-5.2

Step 1 Provider and Model

Switch model assumptions using prices from the selected snapshot.

Step 2 Support Scenario

Set ticket volume, human baseline, and escalation assumptions before tuning the AI workload.

Mid-volume SaaS support queue with moderate retrieval depth and tighter per-ticket savings headroom.

Step 3 AI Workload Assumptions

Set the support-turn assumptions first, then open advanced retrieval and infra fields if needed.
Show advanced inputs

Open these only when retrieval, reranking, vector, or infra detail changes the support decision.

Scenario actions

Copy scenario URL

Paste into ChatGPT or Claude, or share with a teammate.

Save and track this scenario

Track pricing drift on this scenario and get an email if the latest result changes.

How tracking works

After you click Save and track, we carry this exact calculator state into the tracked-scenarios page so you can sign in and confirm the save.

We save your assumptions and the pricing snapshot used for this result.

When a newer pricing snapshot lands, we recompute the same scenario, show what changed, and email you if the latest result moved.

1 tracked scenario free, then $12/mo or $120/yr for up to 25 tracked scenarios.

Decision Signal

Near human

At 54.0% deflection, blended support cost lands at $1.9843 per ticket versus $2.4 for the current human baseline.

That leaves $0.4157 of cost headroom per ticket, or $914.59 per month at the current ticket volume.

Blended cost / ticket

$1.9843

Cost gap / ticket

+$0.4157

Monthly blended cost

$4,365.41

Monthly savings vs human

+$914.59

Most Sensitive Inputs

Most sensitive blended-cost inputs when each is moved up by 10%.
Deflection rate-$0.2
Human cost / escalated ticket+$0.1794
AI requests / ticket+$0.0152

Totals

Summary metrics for the current support scenario.
Blended cost / ticket
$1.9843
Human cost / ticket
$2.4
Cost gap / ticket
+$0.4157
Monthly blended cost
$4,365.41
Monthly human cost
$5,280
Monthly savings vs human
+$914.59
Human share of blended cost
90.4%
Escalation rate
46.0%
Blended cost / ticket$1.9843
Human cost / ticket$2.4
Cost gap / ticket+$0.4157
Monthly blended cost$4,365.41
Monthly human cost$5,280
Monthly savings vs human+$914.59
Human share of blended cost90.4%
Escalation rate46.0%

Blended Cost Breakdown (USD/ticket)

Each cost component is computed independently, then summed.

Largest cost block: Human escalation.

CacheSavings from repeated support requests served by cache. Negative means lower total cost.
$-0.031
Embeddings IngestionAmortized per-ticket share of the fixed monthly support corpus embedding refresh.
$0
GenerationModel input/output token spend for support turns.
$0.0365
InfraNon-model infra overhead per support request.
$0.0057
RerankingReranker cost based on docs rescored per support request.
$0.1661
RetrievalExtra model input spend from retrieved support context.
$0.0128
Vector DbVector database query cost across support requests.
$0.0001
Human escalationHuman handling cost applied only to the escalated share of tickets.
$1.794
CacheSavings from repeated support requests served by cache. Negative means lower total cost.$-0.031
Embeddings IngestionAmortized per-ticket share of the fixed monthly support corpus embedding refresh.$0
GenerationModel input/output token spend for support turns.$0.0365
InfraNon-model infra overhead per support request.$0.0057
RerankingReranker cost based on docs rescored per support request.$0.1661
RetrievalExtra model input spend from retrieved support context.$0.0128
Vector DbVector database query cost across support requests.$0.0001
Human escalationHuman handling cost applied only to the escalated share of tickets.$1.794
Sensitivity RankingChange in ticket cost when one variable is increased by 10%.
VariableDelta blended cost / ticket
Deflection rateShare of tickets fully resolved without human handoff.-$0.2
Human cost / escalated ticketHuman handling cost on escalated tickets only.+$0.1794
AI requests / ticketAverage AI turns needed to fully resolve a ticket.+$0.0152
Rerank DocsDocs reranked per support request.+$0.0143
AI requests before handoffAI turns spent before a ticket escalates to a human.+$0.0039
Cache Hit RateFraction of support requests served from cache.-$0.0031
Output TokensGenerated tokens per support response.+$0.002
Input TokensBase prompt tokens per support request.+$0.0011
Retrieved ChunksRetrieved chunk count per support request.+$0.0011
Tokens Per ChunkAverage chunk size in retrieved support context.+$0.0011
Infra Cost Per Request+$0.0005
Vector Queries Per RequestVector lookup count per support request.+$0
Vector Cost Per Query+$0
Embedding Ingestion Tokens Monthly+$0
Monthly ticketsTicket volume used for monthly totals and fixed-term amortization.-$0
Human cost / ticketCurrent fully loaded human handling cost per resolved ticket.$0

Assumptions and Units

Explicit assumptions keep the support model reproducible and auditable.
  • CurrencyUSD
  • Unit of analysisResolved support ticket
  • Pricing snapshot2026-05-03
  • Selected model rowOpenAI/GPT-5.2
  • Deflection definitionShare of tickets fully resolved without human handoff
  • Blend ruleBlended cost weights deflected and escalated tickets by the current deflection rate
  • Escalated ticket costEscalated tickets include both AI first-pass cost and human handling cost

Recommended Next Step

Use these links to move from modeled support economics into the next pricing or implementation check.

Once the blended escalation path looks viable, open break-even pricing or the flagship workflow model to translate support savings into margin and required-price headroom.

Commercial next step

Break-even PriceAI Workflow Cost

Sources and Snapshot

Pricing comes from the current dated snapshot.

Active Pricing Row

Selected model

OpenAI / GPT-5.2

  • Input tokens$1.75 / 1M
  • Output tokens$14 / 1M

Shared retrieval defaults

  • Embedding input$0.02 / 1M
  • Rerank docs$1 / 1K

Continue Analysis

Switch tools

Read guides