report.object
AI customer-service pricing and ticket economics
Expert-reviewed from public records, platform data, primary sources, and private research beyond AI search. Use /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/sample before purchase, then download PDF, JSON, or Markdown after checkout.
page.markdown
AI customer-service pricing and ticket economics.md
# AI customer-service pricing and ticket economics
Compare support automation by accepted resolution: repeat contacts, handoffs, retained human work and invoice definitions decide the cost behind each outcome, tier, ticket, session, credit or platform charge.
## Object
| field | value |
| ---------------- | -------------------------------------------------------- |
| report_id | rpt_ai_customer_service_pricing_ticket_economics_2026_05 |
| schema_version | 2026-05-28 |
| last_updated_at | 2026-06-16 |
| category | AGENTS |
| sector | Customer experience |
| region | GLOBAL |
| confidence_score | 0.88 |
| source_count | 48 |
| evidence_count | 53 |
## Endpoints
| action | endpoint |
| ------------ | ----------------------------------------------------------------------------------- |
| summary | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05 |
| sample | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/sample |
| schema | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/schema |
| quote | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/quote |
| purchase | /checkout/rpt_ai_customer_service_pricing_ticket_economics_2026_05?view=agent |
| versions | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/versions |
| changelog | /api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/changelog |
| monitor | /api/v1/monitors?report_id=rpt_ai_customer_service_pricing_ticket_economics_2026_05 |
| mcp_resource | colophon://reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/sample |
## Coverage
| field | value |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| category | AGENTS |
| sector | Customer experience |
| region | GLOBAL |
| topics | customer-service AI pricing, ticket economics, outcome pricing, automated resolutions, helpdesk AI agents, AI support agents, Fin, Zendesk AI Agents, Gorgias AI Agent, Freshworks Freddy AI Agent, HubSpot Breeze Customer Agent, Help Scout AI Answers, Sierra Agent OS, Decagon AI Agents, Siena AI, Zowie AI Agents, Yuma AI, Kodif, Front AI, Kustomer AI, DevRev CX Agent, billing audit, repeat contacts, human handoff, cost per accepted resolution, support automation ROI |
| source_classes | pricing_page, pricing_documentation, product_documentation, company_announcement, company_pricing_position, terms, marketplace_pricing, integration_documentation, customer_case_study, regulator, standard, customer_primary_evidence, filing, market_survey |
| update_cadence | Weekly |
## Sample JSON
```json
{
"report_id": "rpt_ai_customer_service_pricing_ticket_economics_2026_05",
"slug": "ai-customer-service-pricing-ticket-economics",
"schema_version": "2026-05-28",
"title": "AI customer-service pricing and ticket economics",
"abstract": "Compare support automation by accepted resolution: repeat contacts, handoffs, retained human work and invoice definitions decide the cost behind each outcome, tier, ticket, session, credit or platform charge.",
"category": "AGENTS",
"sector": "Customer experience",
"region": "GLOBAL",
"topics": [
"customer-service AI pricing",
"ticket economics",
"outcome pricing",
"automated resolutions",
"helpdesk AI agents",
"AI support agents",
"Fin",
"Zendesk AI Agents",
"Gorgias AI Agent",
"Freshworks Freddy AI Agent",
"HubSpot Breeze Customer Agent",
"Help Scout AI Answers",
"Sierra Agent OS",
"Decagon AI Agents",
"Siena AI",
"Zowie AI Agents",
"Yuma AI",
"Kodif",
"Front AI",
"Kustomer AI",
"DevRev CX Agent",
"billing audit",
"repeat contacts",
"human handoff",
"cost per accepted resolution",
"support automation ROI"
],
"last_updated_at": "2026-06-16T00:00:00Z",
"source_count": 48,
"evidence_count": 53,
"confidence_score": 0.88,
"web_url": "/r/ai-customer-service-pricing-ticket-economics/rpt_ai_customer_service_pricing_ticket_economics_2026_05",
"sample_endpoint": "/api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/sample",
"inventory_endpoint": "/api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/inventory",
"full_endpoint": "/api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/full",
"schema_endpoint": "/api/v1/reports/rpt_ai_customer_service_pricing_ticket_economics_2026_05/schema",
"redaction": {
"status": "sample",
"paid_sections_redacted": true,
"preview_limits": [
"summary",
"table_of_contents",
"evidence_profile"
]
},
"coverage": {
"category": "AGENTS",
"sector": "Customer experience",
"region": "GLOBAL",
"topics": [
"customer-service AI pricing",
"ticket economics",
"outcome pricing",
"automated resolutions",
"helpdesk AI agents",
"AI support agents",
"Fin",
"Zendesk AI Agents",
"Gorgias AI Agent",
"Freshworks Freddy AI Agent",
"HubSpot Breeze Customer Agent",
"Help Scout AI Answers",
"Sierra Agent OS",
"Decagon AI Agents",
"Siena AI",
"Zowie AI Agents",
"Yuma AI",
"Kodif",
"Front AI",
"Kustomer AI",
"DevRev CX Agent",
"billing audit",
"repeat contacts",
"human handoff",
"cost per accepted resolution",
"support automation ROI"
],
"source_classes": [
"pricing_page",
"pricing_documentation",
"product_documentation",
"company_announcement",
"company_pricing_position",
"terms",
"marketplace_pricing",
"integration_documentation",
"customer_case_study",
"regulator",
"standard",
"customer_primary_evidence",
"filing",
"market_survey"
]
},
"confidence": {
"overall_confidence": 0.88,
"source_quality": 0.9,
"source_recency": 0.94,
"source_density": 0.9,
"claim_verifiability": 0.86,
"geographic_coverage": 0.78,
"known_gaps": [
"No public dataset links AI-agent billing events to accepted customer-service resolution after repeat contacts, reversals, human corrections and customer harm.",
"Several sales-led enterprise vendors do not publish rate cards, overage terms, minimums, implementation fees or partial-success treatment.",
"Vendor case studies rarely disclose measurement windows, denominators, audit design, invoice treatment, retained human work or cross-channel repeat-contact rates.",
"Billing dashboards may expose resolution states, but buyer-side invoice-to-log export quality usually requires contract review or pilot proof."
]
},
"document": {
"object": "report_document",
"schemaVersion": "2026-05-28",
"title": "AI customer-service pricing and ticket economics",
"subtitle": "Use accepted resolution as the pricing unit before comparing vendor billable events.",
"abstract": "Compare support automation by accepted resolution: repeat contacts, handoffs, retained human work and invoice definitions decide the cost behind each outcome, tier, ticket, session, credit or platform charge.",
"category": "AGENTS",
"sector": "Customer experience",
"region": "GLOBAL",
"topics": [
"customer-service AI pricing",
"ticket economics",
"outcome pricing",
"automated resolutions",
"helpdesk AI agents",
"AI support agents",
"Fin",
"Zendesk AI Agents",
"Gorgias AI Agent",
"Freshworks Freddy AI Agent",
"HubSpot Breeze Customer Agent",
"Help Scout AI Answers",
"Sierra Agent OS",
"Decagon AI Agents",
"Siena AI",
"Zowie AI Agents",
"Yuma AI",
"Kodif",
"Front AI",
"Kustomer AI",
"DevRev CX Agent",
"billing audit",
"repeat contacts",
"human handoff",
"cost per accepted resolution",
"support automation ROI"
],
"sources": [
{
"id": "S1",
"label": "Intercom - Fin AI Agent outcomes",
"publisher": "Intercom",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes"
},
{
"id": "S3",
"label": "Zendesk - automated resolutions for AI agents",
"publisher": "Zendesk",
"sourceClass": "pricing_documentation",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official billing documentation; buyer should still test export fields, invoice samples and contract-specific exceptions.",
"transformChain": [],
"url": "https://support.zendesk.com/hc/en-us/articles/5352026794010-About-automated-resolutions-for-AI-agents"
},
{
"id": "S6",
"label": "Gorgias - pricing",
"publisher": "Gorgias",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://www.gorgias.com/pricing"
},
{
"id": "S7",
"label": "Gorgias - billing documentation",
"publisher": "Gorgias",
"sourceClass": "pricing_documentation",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official billing documentation; buyer should still test export fields, invoice samples and contract-specific exceptions.",
"transformChain": [],
"url": "https://docs.gorgias.com/en-US/how-youre-billed-for-using-gorgias-199385"
},
{
"id": "S9",
"label": "Freshworks - Freshdesk pricing",
"publisher": "Freshworks",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://www.freshworks.com/freshdesk/pricing/"
},
{
"id": "S11",
"label": "HubSpot - Customer Agent outcome pricing update",
"publisher": "HubSpot",
"sourceClass": "company_announcement",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Company announcement; useful dated pricing signal, not independent outcome validation.",
"transformChain": [],
"url": "https://www.hubspot.com/company-news/hubspots-customer-agent-and-prospecting-agent-now-you-pay-when-the-task-is-complete"
},
{
"id": "S12",
"label": "HubSpot - product and services catalog",
"publisher": "HubSpot",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://legal.hubspot.com/hubspot-product-and-services-catalog"
},
{
"id": "S14",
"label": "Help Scout - AI resolutions pricing",
"publisher": "Help Scout",
"sourceClass": "pricing_documentation",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official billing documentation; buyer should still test export fields, invoice samples and contract-specific exceptions.",
"transformChain": [],
"url": "https://docs.helpscout.com/article/1746-ai-resolutions-pricing"
},
{
"id": "S17",
"label": "Sierra - outcome-based pricing for AI agents",
"publisher": "Sierra",
"sourceClass": "company_pricing_position",
"accessedAt": "2026-06-16",
"status": "partial",
"access": "sample",
"caveat": "Vendor-authored pricing position; use for commercial logic, not independent rate-card verification.",
"transformChain": [],
"url": "https://sierra.ai/blog/outcome-based-pricing-for-ai-agents"
},
{
"id": "S19",
"label": "Siena AI - pricing",
"publisher": "Siena AI",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://www.siena.cx/pricing"
},
{
"id": "S21",
"label": "Zowie AI Agent Platform - AWS Marketplace",
"publisher": "AWS Marketplace",
"sourceClass": "marketplace_pricing",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Marketplace listing; package, utilisation, infrastructure and implementation terms need contract reconciliation.",
"transformChain": [],
"url": "https://aws.amazon.com/marketplace/pp/prodview-fs73j5j7ik4tk"
},
{
"id": "S23",
"label": "Yuma AI - FAQ and pricing scope",
"publisher": "Yuma AI",
"sourceClass": "pricing_documentation",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official billing documentation; buyer should still test export fields, invoice samples and contract-specific exceptions.",
"transformChain": [],
"url": "https://yuma.ai/faq"
},
{
"id": "S35",
"label": "Intercom - Lightspeed Fin customer story",
"publisher": "Intercom",
"sourceClass": "customer_case_study",
"accessedAt": "2026-06-16",
"status": "partial",
"access": "sample",
"caveat": "Vendor-published customer story; useful for workflow shape, weak as independent ROI or accepted-resolution proof.",
"transformChain": [],
"url": "https://fin.ai/customers/lightspeed-transformation"
},
{
"id": "S45",
"label": "Yuma AI - pricing and demo",
"publisher": "Yuma AI",
"sourceClass": "pricing_page",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Official public pricing snapshot; order-form terms, allowances, taxes, implementation and overages can still change the buyer's bill.",
"transformChain": [],
"url": "https://yuma.ai/pricing"
},
{
"id": "S48",
"label": "Silicon Valley Bank - State of Enterprise Software Report 2026",
"publisher": "Silicon Valley Bank",
"sourceClass": "market_survey",
"accessedAt": "2026-06-16",
"status": "verified",
"access": "sample",
"caveat": "Public source; verify current contract, product and pricing treatment before procurement.",
"transformChain": [],
"url": "https://www.svb.com/trends-insights/reports/state-of-enterprise-software/"
}
],
"evidence": [
{
"id": "E1",
"sourceId": "S1",
"claimIds": [
"C1",
"C4"
],
"summary": "Fin charges one outcome per conversation for chat and email when used with Intercom: $0.99 for a resolution, Procedure handoff, or disqualification, and $9.99 for a sales qualification.",
"status": "verified",
"confidence": 0.94,
"access": "sample"
},
{
"id": "E2",
"sourceId": "S1",
"claimIds": [
"C2",
"C4",
"C6"
],
"summary": "Fin defines a resolution as confirmed or assumed after Fin's last answer; default escalation and failed procedures are not billed, while a configured Procedure handoff can be billable.",
"status": "verified",
"confidence": 0.93,
"access": "sample"
},
{
"id": "E4",
"sourceId": "S3",
"claimIds": [
"C1",
"C2",
"C4",
"C6"
],
"summary": "Zendesk automated resolutions for AI agents rely on handled or answered conversations, LLM verification, channel-specific session timing and 72-hour email/no-follow-up logic; escalated conversations do not consume an automated resolution.",
"status": "verified",
"confidence": 0.92,
"access": "sample"
},
{
"id": "E7",
"sourceId": "S6",
"claimIds": [
"C1",
"C3",
"C4",
"C5"
],
"summary": "Gorgias publishes helpdesk ticket plans and AI Agent automated-interaction tiers; public monthly AI tiers show $1.00 per automated interaction with $1.50 overages, and annual tiers show $0.90 per automated interaction with $1.50 overages.",
"status": "verified",
"confidence": 0.94,
"access": "sample"
},
{
"id": "E8",
"sourceId": "S7",
"claimIds": [
"C3",
"C4",
"C5",
"C6"
],
"summary": "Gorgias billing documentation says a helpdesk ticket fee and an AI Agent automation fee can both apply to the same ticket when AI Agent resolves without human intervention, while automated interactions require no human-agent involvement within 72 hours.",
"status": "verified",
"confidence": 0.95,
"access": "sample"
},
{
"id": "E10",
"sourceId": "S9",
"claimIds": [
"C1",
"C3",
"C4"
],
"summary": "Freshdesk public pricing lists Growth, Pro and Enterprise agent seats and says Email AI Agent sessions are priced at $49 per 100 sessions, with 500 sessions offered on Pro and Enterprise plans.",
"status": "verified",
"confidence": 0.93,
"access": "sample"
},
{
"id": "E11",
"sourceId": "S9",
"claimIds": [
"C4"
],
"summary": "Freshworks defines an Email AI Agent session as a 72-hour window starting from the customer's first email; all AI responses inside that window count as one session regardless of reply count.",
"status": "verified",
"confidence": 0.91,
"access": "sample"
},
{
"id": "E13",
"sourceId": "S11",
"claimIds": [
"C1",
"C2",
"C4"
],
"summary": "HubSpot announced Breeze Customer Agent outcome pricing at $0.50 per resolved conversation, paid as 50 HubSpot Credits per resolution, and said it moved from $1.00 per conversation to resolved-conversation pricing on 14 April 2026.",
"status": "verified",
"confidence": 0.93,
"access": "sample"
},
{
"id": "E15",
"sourceId": "S12",
"claimIds": [
"C1",
"C3",
"C4"
],
"summary": "HubSpot product catalog lists included monthly credits by product tier and sells additional HubSpot Credits at $0.010 per credit through capacity packs or pay-as-you-go.",
"status": "verified",
"confidence": 0.93,
"access": "sample"
},
{
"id": "E17",
"sourceId": "S14",
"claimIds": [
"C1",
"C2",
"C4",
"C6"
],
"summary": "Help Scout AI Answers charges $0.75 per AI resolution, where one AI chat session is resolved without human help; monthly spending limits can disable AI Answers once the limit is reached.",
"status": "verified",
"confidence": 0.92,
"access": "sample"
},
{
"id": "E20",
"sourceId": "S17",
"claimIds": [
"C1",
"C2",
"C4",
"C6"
],
"summary": "Sierra describes outcome pricing tied to business outcomes such as resolved support conversations, saved cancellations, purchases, upsells or cross-sells, and says unresolved conversations are not charged in most cases.",
"status": "verified",
"confidence": 0.9,
"access": "sample"
},
{
"id": "E23",
"sourceId": "S19",
"claimIds": [
"C1",
"C3",
"C4"
],
"summary": "Siena's pricing page says pricing is based on ticket volume and team structure and describes a $750/month platform fee plus automated tickets at $0.90 each.",
"status": "verified",
"confidence": 0.92,
"access": "sample"
},
{
"id": "E25",
"sourceId": "S21",
"claimIds": [
"C1",
"C3",
"C4"
],
"summary": "AWS Marketplace lists Zowie AI Agent Platform as SaaS with a 12-month contract package of 25,000 automated conversations for $34,500, with AWS infrastructure costs potentially separate.",
"status": "verified",
"confidence": 0.92,
"access": "sample"
},
{
"id": "E27",
"sourceId": "S23",
"claimIds": [
"C1",
"C2",
"C4"
],
"summary": "Yuma's FAQ says pricing is scoped around ticket volume, workflows, channel mix and implementation depth rather than generic seat counts, and deployment starts gradually so teams can review quality before scaling.",
"status": "verified",
"confidence": 0.88,
"access": "sample"
},
{
"id": "E39",
"sourceId": "S35",
"claimIds": [],
"summary": "Lightspeed's Fin story reports more than 43,000 Fin resolutions per month, 88% Fin involvement, 72% resolution, support in 12-plus languages and 100-plus countries, but the metrics remain vendor-published and do not expose a buyer-side billing audit.",
"status": "verified",
"confidence": 0.84,
"access": "sample"
},
{
"id": "E49",
"sourceId": "S45",
"claimIds": [
"C1",
"C4"
],
"summary": "Yuma-owned pricing material describes performance-based billing, a 30-day trial and sales-led pricing details, while the Shopify listing supplies public package anchors that need contract reconciliation.",
"status": "verified",
"confidence": 0.87,
"access": "sample"
},
{
"id": "E52",
"sourceId": "S48",
"claimIds": [
"C1",
"C3",
"C4"
],
"summary": "Silicon Valley Bank reports that nearly 40% of surveyed enterprise-software companies are primarily seat-based today, but only 26% expect to remain primarily seat-based as AI labour augmentation and compute economics change pricing.",
"status": "verified",
"confidence": 0.87,
"access": "sample"
}
],
"claims": [
{
"id": "C1",
"statement": "Customer-service AI pricing is no longer one SaaS metric; vendors charge by outcome, automated resolution, ticket, session, credit, conversation, seat, platform package or enterprise contract.",
"confidence": 0.94,
"evidenceIds": [
"E1",
"E4",
"E7",
"E10",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25",
"E27",
"E49",
"E52"
],
"access": "sample"
},
{
"id": "C2",
"statement": "The economic denominator should be accepted resolution: a customer issue resolved correctly after repeat-contact, reversal, escalation and human-rework checks.",
"confidence": 0.92,
"evidenceIds": [
"E2",
"E4",
"E13",
"E17",
"E20",
"E27"
],
"access": "sample"
},
{
"id": "C3",
"statement": "Base helpdesk, CRM or platform cost often remains even when AI resolves the ticket, so AI unit prices should not be read as total support cost.",
"confidence": 0.91,
"evidenceIds": [
"E7",
"E8",
"E10",
"E15",
"E23",
"E25",
"E52"
],
"access": "sample"
},
{
"id": "C4",
"statement": "Chargeable events vary enough that buyers need an event dictionary before comparing vendors.",
"confidence": 0.94,
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E11",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25",
"E27",
"E49",
"E52"
],
"access": "sample"
},
{
"id": "C5",
"statement": "Ticket-fee and AI-fee stacking is an explicit risk in helpdesk-native models and a hidden risk in sales-led enterprise packages.",
"confidence": 0.9,
"evidenceIds": [
"E7",
"E8"
],
"access": "sample"
},
{
"id": "C6",
"statement": "Assisted handoffs can be non-billable, billable, or treated as AI contribution rather than completion depending on the vendor definition.",
"confidence": 0.91,
"evidenceIds": [
"E2",
"E4",
"E8",
"E17",
"E20"
],
"access": "sample"
}
],
"colophon": {
"checkedAt": "2026-06-16",
"latestRevisionAt": "2026-06-16T00:00:00Z",
"reviewStandard": "expert_human_reviewed",
"kinetics": {
"speed": "fast",
"impact": 0.9,
"momentum": 0.89,
"businessImpact": "Customer-service AI buying is shifting from per-event sticker prices to accepted-resolution economics: repeat contacts, handoffs, retained work and invoice audit now decide the payable outcome.",
"rateOfChange": "Pricing-page changes, outcome definitions, credit/session allowances and billing-export fields can change the approved cost model before renewal.",
"from": "seat, ticket and deflection comparisons by vendor event",
"toward": "accepted-resolution pricing with issue-level invoice audit, repeat-contact checks and retained-work accounting"
},
"watch": [
"CFPB complaint bulletin, circular or enforcement action naming AI false resolution, refund error, complaint routing or disclosure harm; regulated-service outcome pricing may need human approval and harm-credit terms.",
"Intercom Fin outcome-pricing documentation changes support-outcome, Procedure handoff, disqualification or sales-qualification billing rules; outcome routes may need a new event dictionary before renewal.",
"Zendesk automated-resolution or AI-agent reporting documentation adds export fields for conversation ID, ticket ID, repeat-contact state or reversal; invoice-audit recommendations could move from sampling to export reconciliation.",
"Gorgias AI Agent pricing changes automated-interaction overage, included AI Agent ticket treatment or the 72-hour human-involvement rule; ecommerce ticket-plus-automation stacking assumptions need renewal repricing.",
"Freshdesk pricing or Email AI Agent documentation changes the 72-hour session window, $49 pack size, included sessions or cap behaviour; session economics need a new pack-utilisation model.",
"Yuma pricing page or Shopify App Store package terms change trial length, package minimums or automated-ticket treatment; ecommerce shortlist economics could reopen."
],
"gapAnalysis": "Independent, invoice-level CX-agent economics evidence linking chargeable event IDs, issue identity, false resolution, repeat contacts, handoff reason, tool-call failure, credit/reversal state, reviewer minutes, rework, CSAT, customer harm and cost per accepted resolution."
},
"body": {
"sections": [
{
"id": "executive-summary",
"title": "Executive summary",
"access": "sample",
"dek": "The AI bill is easy to price and hard to compare.",
"claimIds": [
"C1",
"C2",
"C3",
"C4"
],
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25"
],
"blocks": [
{
"id": "executive-summary-narrative",
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25"
],
"type": "section_narrative",
"lead": "The useful benchmark is the cost of a correct, final, non-reopened customer resolution.",
"body": [
"The market now sells support automation through outcomes, automated resolutions, resolved conversations, automated interactions, sessions, credits, ticket packages, seats, platform fees and sales-led enterprise contracts. Those units sound similar enough to confuse a budget review and different enough to distort one.",
"A buyer should normalize every proposal to cost per accepted resolution. Accepted means the customer issue was solved correctly, the action was completed, the customer did not return through another channel, no human had to fix the result, and the invoice row can be tied to the conversation and ticket logs. [E2, E16]"
],
"detail": [
"The trap is treating a vendor's billable event as the support outcome. Fin can bill a Procedure handoff [E2]; Zendesk verifies automated resolutions after channel-specific handling rules [E4]; Gorgias can charge both ticket and automation fees on the same AI-resolved ticket [E8]; Freshworks sessions [E10] and HubSpot credits [E15] introduce different consumption logic.",
"The right procurement artefact is a pricing ledger, not a price comparison table. It should join invoice events to conversation IDs, ticket IDs, handoff reasons, tool calls, repeat contacts, human review and final customer state."
]
},
{
"id": "buyer-decision-packet",
"title": "Renewal approval is the buyer moment",
"evidenceIds": [
"E1",
"E2",
"E4",
"E8",
"E10",
"E17"
],
"type": "table",
"columns": [
{
"key": "field",
"label": "Field",
"align": "left"
},
{
"key": "decision",
"label": "Decision implication",
"align": "left"
}
],
"rows": [
{
"field": "Decision owner",
"decision": "CX finance, procurement and support operations deciding whether to approve, reprice or renegotiate a high-volume support-agent contract."
},
{
"field": "Buying trigger",
"decision": "Outcome-priced vendor proposal, renewal, overage surprise or first production AI-agent rollout."
},
{
"field": "Approval evidence",
"decision": "Accepted-resolution cost, event dictionary, invoice-to-log export, mock invoice and retained-work accounting."
},
{
"field": "Economic boundary",
"decision": "Pricing, billing mechanics and ticket economics; full voice, workflow and governance lanes belong in related CX reports."
},
{
"field": "Renewal question",
"decision": "Can finance audit cost per accepted resolution after launch, including repeat contacts, handoffs, reversals and retained work?"
}
]
},
{
"id": "executive-price-rules",
"title": "Four rules prevent a false saving",
"evidenceIds": [
"E2",
"E4",
"E8",
"E17"
],
"type": "table",
"columns": [
{
"key": "rule",
"label": "Rule",
"align": "left"
},
{
"key": "why",
"label": "Why it matters",
"align": "left"
},
{
"key": "buyerMove",
"label": "Buyer move",
"align": "left"
}
],
"rows": [
{
"rule": "Use accepted resolution, not automation rate.",
"why": "Automation can include no-follow-up outcomes, vendor-verified resolutions, ticket automation, session usage or unverified internal outcomes.",
"buyerMove": "Apply a repeat-contact and QA window before counting a resolution as accepted."
},
{
"rule": "Separate base platform from AI usage.",
"why": "Seats, tickets, platform fees, credits, channel usage, implementation and overages can remain after AI deflects work.",
"buyerMove": "Budget the whole route, not the AI line item."
},
{
"rule": "Price the handoff.",
"why": "Human assistance may be non-billable, billable as a Procedure handoff, or counted as AI contribution rather than completion.",
"buyerMove": "Demand handoff reason codes and invoice treatment in the order form."
},
{
"rule": "Audit the invoice.",
"why": "Outcome pricing pays for classification. Classification should be testable.",
"buyerMove": "Require raw logs, billing exports and dispute rights."
}
]
},
{
"id": "customer-experience-report-link",
"evidenceIds": [],
"type": "report_link",
"reportId": "rpt_ai_customer_experience_workflows_2026_05",
"slug": "ai-customer-service-workflows",
"label": "AI for customer-service workflows",
"dek": "Use the broader CX report for market structure, vendor lanes, voice, vertical workflow and governance routing.",
"relation": "Related report"
},
{
"id": "route-definition-callout",
"title": "Route definition",
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25"
],
"type": "callout",
"tone": "neutral",
"body": "Route means the approved path from work to accepted output: the source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger that make an AI result usable."
}
]
},
{
"id": "decision-frame",
"title": "Decision frame",
"access": "sample",
"dek": "Buy the denominator before buying the agent.",
"claimIds": [
"C1",
"C2",
"C3",
"C4"
],
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25",
"E52"
],
"blocks": [
{
"id": "decision-frame-narrative",
"evidenceIds": [
"E2",
"E4",
"E8",
"E17",
"E52"
],
"type": "section_narrative",
"lead": "A customer-service agent can be cheap per event and expensive per solved issue.",
"body": [
"The buyer's first decision is the economic unit. Outcome pricing works when the outcome is real, discrete and reversible. Session pricing works when interaction length is predictable. Seat-plus-add-on pricing works when the helpdesk remains the operating system. Enterprise packages work when integration, governance and deployment services are the actual product. Silicon Valley Bank's State of Enterprise Software report shows this is a market move, not a support-vendor quirk: nearly 40% of enterprise-software respondents remain primarily seat-based today, but only 26% expect to stay there as AI labour augmentation and compute economics change pricing [E52].",
"The second decision is the proof window. A 72-hour no-follow-up rule, an assumed resolution, a resolved AI chat, a verified automated resolution and a fully automated ticket are different commercial states. They should all be translated into one buyer-owned state: accepted resolution. [E4, E16]"
],
"detail": [
"The third decision is how to handle retained work. AI may reduce frontline handling and increase supervision, knowledge maintenance, billing audit, exception review, connector upkeep and policy release work. Those minutes belong in the denominator.",
"A buyer can approve more than one pricing route. The mistake is comparing them without a common ledger."
]
},
{
"id": "pricing-route-table",
"title": "Each route hides a different cost",
"evidenceIds": [
"E7",
"E10",
"E15",
"E20",
"E23",
"E25"
],
"type": "table",
"columns": [
{
"key": "route",
"label": "Pricing route",
"align": "left"
},
{
"key": "bestWhen",
"label": "Best when",
"align": "left"
},
{
"key": "hiddenCost",
"label": "Hidden cost to model",
"align": "left"
},
{
"key": "contractQuestion",
"label": "Contract question",
"align": "left"
}
],
"rows": [
{
"route": "Outcome or resolved conversation",
"bestWhen": "The customer issue has a clean finish and low ambiguity.",
"hiddenCost": "Assumed success, repeated issues, configured handoffs and sales qualification.",
"contractQuestion": "What reverses or credits an outcome?"
},
{
"route": "Automated-resolution verification",
"bestWhen": "The platform can classify AI contribution and resolution quality.",
"hiddenCost": "Verification method, follow-up window, trigger setup and assisted escalations.",
"contractQuestion": "Can the buyer audit the resolution state assigned to each conversation?"
},
{
"route": "Ticket or automated interaction",
"bestWhen": "The helpdesk already prices support work by ticket volume.",
"hiddenCost": "Ticket fee plus automation fee, overages and seasonal spikes.",
"contractQuestion": "Can one customer issue create several billable events?"
},
{
"route": "Session or credit",
"bestWhen": "The buyer wants predictable consumption controls for a narrow channel.",
"hiddenCost": "Long threads, repeated responses, expired packs and credit exhaustion.",
"contractQuestion": "What happens when the cap is reached mid-cycle?"
},
{
"route": "Seat plus AI add-on",
"bestWhen": "The platform remains the support system of record.",
"hiddenCost": "Seats retained for escalations, supervisors, QA and operations.",
"contractQuestion": "Does AI success reduce, freeze or increase seat commitments?"
},
{
"route": "Enterprise outcome package",
"bestWhen": "Workflows need deep integrations, governance and services.",
"hiddenCost": "Minimums, implementation, success services, simulations and contract change work.",
"contractQuestion": "Which work is included before the first billable outcome?"
}
]
}
]
},
{
"id": "pricing-units",
"title": "Pricing units",
"access": "sample",
"dek": "The labels rhyme. The invoices do not.",
"claimIds": [
"C1",
"C3",
"C4",
"C5",
"C6"
],
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E11",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25",
"E52"
],
"blocks": [
{
"id": "pricing-units-narrative",
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E11",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25",
"E52"
],
"type": "section_narrative",
"lead": "Outcome, resolution, ticket, session, credit and conversation are not interchangeable words.",
"body": [
"A vendor can advertise performance pricing while billing a very different event from the one finance assumes. Fin's support outcome [E1], Zendesk's automated resolution [E4], Gorgias's automated interaction [E7], Freshworks's session [E10], HubSpot's credit [E13] and Help Scout's AI resolution [E17] all need their own entry in the pricing model.",
"The market-level reason is visible in Silicon Valley Bank's State of Enterprise Software survey: software companies are moving away from seat primacy because labour augmentation and variable AI costs break the old seat proxy [E52].",
"The chargeable-event dictionary decides whether an AI-handled return counts once, twice, not at all, or only after a no-follow-up window. It also decides whether an assisted handoff is a cost saver, a billable outcome or AI contribution without completion."
],
"detail": [
"The buyer should ask every vendor to provide a written chargeable-event dictionary before the pilot starts. If the dictionary cannot be exported against real conversation logs, the buyer is piloting a demo, not a bill."
]
},
{
"id": "pricing-unit-table",
"title": "The billable event changes the answer",
"evidenceIds": [
"E1",
"E2",
"E4",
"E7",
"E8",
"E10",
"E11",
"E13",
"E15",
"E17",
"E20",
"E23",
"E25"
],
"type": "table",
"columns": [
{
"key": "unit",
"label": "Billable unit",
"align": "left"
},
{
"key": "where",
"label": "Where it appears",
"align": "left"
},
{
"key": "chargedWhen",
"label": "Charge trigger",
"align": "left"
},
{
"key": "costTrap",
"label": "Cost trap",
"align": "left"
},
{
"key": "buyerMetric",
"label": "Buyer metric",
"align": "left"
}
],
"rows": [
{
"unit": "Outcome",
"where": "Fin, Sierra and other outcome-led agent routes.",
"chargedWhen": "Defined business result occurs, such as resolution, procedure handoff, saved cancellation, purchase or other agreed outcome.",
"costTrap": "Assumed success, billable handoff, repeat-contact rules and sales qualification can change the invoice.",
"buyerMetric": "Accepted resolutions after repeat and rework window."
},
{
"unit": "Automated resolution",
"where": "Zendesk AI Agents.",
"chargedWhen": "AI resolves without human escalation after handled or answered status, session timing and LLM verification.",
"costTrap": "Vendor verification can diverge from internal QA because no-follow-up windows, channel rules and trigger setup also matter.",
"buyerMetric": "Verified internal resolution with topic-level QA."
},
{
"unit": "Automated interaction or ticket",
"where": "Gorgias, Siena and commerce-specialist agents.",
"chargedWhen": "AI handles an interaction or automates a ticket under vendor-specific rules.",
"costTrap": "Helpdesk ticket fees, AI fees and overage fees can stack on the same customer issue.",
"buyerMetric": "Completed ecommerce case after returns, refunds, order edits and follow-up."
},
{
"unit": "Session or credit",
"where": "Freshworks sessions and HubSpot Credits.",
"chargedWhen": "A session, response or credit-consuming action occurs, depending on product and channel.",
"costTrap": "Session windows, pack expiry and credit exhaustion can change whether the buyer pays for difficult threads or stalled mid-cycle automation.",
"buyerMetric": "Accepted case per credit or session pack."
},
{
"unit": "Conversation package",
"where": "Zowie AWS Marketplace-style committed packages.",
"chargedWhen": "A package of automated conversations is bought for a contract period.",
"costTrap": "Low utilisation and separate infrastructure, implementation or success costs can dominate the per-conversation math.",
"buyerMetric": "Utilized accepted conversations per contract period."
},
{
"unit": "Seat plus AI add-on",
"where": "Front, Help Scout, Kustomer, Freshworks and helpdesk-native suites.",
"chargedWhen": "Base users or platform tiers are purchased, then AI add-ons or usage are layered on top.",
"costTrap": "Seat spend may not shrink just because AI handles work; retained agents and supervisor seats remain.",
"buyerMetric": "Total support cost per accepted resolution."
}
]
}
]
},
{
"id": "accepted-resolution-economics",
"title": "Accepted-resolution economics",
"access": "locked",
"dek": "The correct denominator arrives after the customer has had a chance to come back.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "accepted-resolution-economics-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "chargeable-events",
"title": "Chargeable events",
"access": "locked",
"dek": "The public price pages are useful. The edge cases are where the money moves.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "chargeable-events-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "scenario-model",
"title": "Scenario model",
"access": "locked",
"dek": "The model should be built from buyer facts, not vendor averages.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "scenario-model-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "billing-audit",
"title": "Billing audit",
"access": "locked",
"dek": "Outcome pricing needs an audit trail.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "billing-audit-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "retained-human-work",
"title": "Retained human work",
"access": "locked",
"dek": "The work shifts before it disappears.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "retained-human-work-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "contract-controls",
"title": "Contract controls",
"access": "locked",
"dek": "The order form should describe failure as carefully as success.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "contract-controls-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "deployment-evidence",
"title": "Deployment evidence",
"access": "locked",
"dek": "Case studies show where to test, not what to pay.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "deployment-evidence-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "known-unknowns",
"title": "Known unknowns",
"access": "locked",
"dek": "The missing data is exactly what finance needs.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "known-unknowns-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "recommended-next-steps",
"title": "Recommended next steps",
"access": "locked",
"dek": "Procure the ledger before the licence.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "recommended-next-steps-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "vendor-directory",
"title": "Vendor directory",
"access": "locked",
"dek": "Use vendors after the unit economics are defined.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "vendor-directory-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "source-ledger",
"title": "Source ledger",
"access": "locked",
"dek": "Primary pricing, product, case-study and governance sources behind the economics.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "source-ledger-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "glossary",
"title": "Glossary",
"access": "sample",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "glossary-table",
"title": "Terms used in this report",
"caption": "Definitions are reader aids, not separate evidence claims.",
"evidenceIds": [],
"type": "table",
"columns": [
{
"key": "term",
"label": "Term",
"align": "left"
},
{
"key": "meaning",
"label": "Plain meaning",
"align": "left"
}
],
"rows": [
{
"term": "Route",
"meaning": "The approved path from work to accepted output: source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger."
},
{
"term": "API",
"meaning": "Application programming interface: a governed software connection used by an app or workflow to call a model or service."
},
{
"term": "LLM",
"meaning": "Large language model: a model trained to read and generate text-like tokens."
},
{
"term": "PayGo",
"meaning": "Pay as you go: shared cloud capacity billed by usage rather than pre-reserved throughput."
},
{
"term": "SLA",
"meaning": "Service-level agreement: a contractual availability or support commitment, not observed uptime history."
}
]
}
]
}
]
}
},
"gap_analysis": "Independent, invoice-level CX-agent economics evidence linking chargeable event IDs, issue identity, false resolution, repeat contacts, handoff reason, tool-call failure, credit/reversal state, reviewer minutes, rework, CSAT, customer harm and cost per accepted resolution.",
"kinetics": {
"speed": "fast",
"impact": 0.9,
"momentum": 0.89,
"businessImpact": "Customer-service AI buying is shifting from per-event sticker prices to accepted-resolution economics: repeat contacts, handoffs, retained work and invoice audit now decide the payable outcome.",
"rateOfChange": "Pricing-page changes, outcome definitions, credit/session allowances and billing-export fields can change the approved cost model before renewal.",
"from": "seat, ticket and deflection comparisons by vendor event",
"toward": "accepted-resolution pricing with issue-level invoice audit, repeat-contact checks and retained-work accounting"
},
"watch_signals": [
"CFPB complaint bulletin, circular or enforcement action naming AI false resolution, refund error, complaint routing or disclosure harm; regulated-service outcome pricing may need human approval and harm-credit terms.",
"Intercom Fin outcome-pricing documentation changes support-outcome, Procedure handoff, disqualification or sales-qualification billing rules; outcome routes may need a new event dictionary before renewal.",
"Zendesk automated-resolution or AI-agent reporting documentation adds export fields for conversation ID, ticket ID, repeat-contact state or reversal; invoice-audit recommendations could move from sampling to export reconciliation.",
"Gorgias AI Agent pricing changes automated-interaction overage, included AI Agent ticket treatment or the 72-hour human-involvement rule; ecommerce ticket-plus-automation stacking assumptions need renewal repricing.",
"Freshdesk pricing or Email AI Agent documentation changes the 72-hour session window, $49 pack size, included sessions or cap behaviour; session economics need a new pack-utilisation model.",
"Yuma pricing page or Shopify App Store package terms change trial length, package minimums or automated-ticket treatment; ecommerce shortlist economics could reopen."
],
"sample_findings": [
"Customer-service AI pricing now spans outcomes, automated resolutions, tickets, automated interactions, sessions, credits, conversations, seats, platform fees and enterprise contracts."
]
}
```