STKD.DIGITAL · BUSINESS IN MOTION
STKD.digital
Menu
All service and administration insights

Service and administration · 4 MIN READ

AI support pricing: why cost per resolution is not the whole bill

Compare the definition of a billable outcome, the human work that remains and the quality of the customer’s actual result.

THE SHORT ANSWER

Compare the total operating bill, not just the advertised price per resolution. That means the vendor's exact billing definition, seats or minimum commitments, usage, setup, knowledge upkeep and the human work that remains. Check customer outcomes separately: a billable event is not by itself proof that the customer's problem was solved.

Start with the billing definition

Do not assume two suppliers use the same unit. One may charge for seats and usage, another for specific outcomes, and a custom system may combine software, model usage and an ongoing service fee. Build your comparison around the same representative workload and the same definition of an acceptable customer result.

Guide map: Start with the billing definition; A current example of why the details matter; Model the work that remains with people

A current example of why the details matter

As checked on October 28, 2026, Intercom's Fin outcome documentation lists $0.99 for a resolution and $0.99 for certain configured procedure handoffs, while a sales qualification is listed at $9.99. The stated rates apply to chat and email when used with Intercom; voice and specialized needs have separate considerations. This is a dated vendor example, not a STKD price or a market-wide benchmark. Fin outcome definitions and pricing.

That documentation distinguishes confirmed resolutions from assumed resolutions when a customer leaves without requesting more help. It also describes what happens when a customer returns seeking further assistance. Read those rules alongside your own service measures rather than treating the billing event as the entire definition of success. Fin outcome documentation.

Intercom's pricing FAQ separately explains seat-based helpdesk plans, usage charges and a different arrangement for Fin on an existing helpdesk, where minimum commitments can apply. A unit price alone is therefore not a complete budget. Intercom pricing FAQ.

Model the work that remains with people

Take a representative month of requests and group them by type. Which can be answered from a maintained policy? Which need account verification? Which require a change in another system? Which need judgment, investigation or a commercial exception? Do not assume your current volume is uniformly automatable.

Illustrative example: a business receives 1,000 requests, but only 350 are straightforward policy or status questions. A proposal based on automating all 1,000 will overstate the immediately addressable opportunity. Even among the 350, some may need clarification, escalation or correction. Model a range of outcomes rather than one attractive rate.

Include the cost of preparing knowledge, reviewing conversations, investigating errors and handling escalations. If the remaining human cases become more complex, the average time per human case may rise. That does not automatically mean the project failed, but it changes the staffing calculation.

Compare cost per useful outcome, not just cost per event

Define a useful outcome in terms the customer and business recognize. For an order question, it may be accurate status with the correct next step. For an account change, it may be the authorized change confirmed in the system of record. For a complaint, it may be a well-prepared handoff to someone who can act.

Review a sample of conversations, including cases counted as successful. Look for invented policy, repeated questions, unsupported promises and customers who return through another channel. A dashboard can tell you where to look; it cannot replace reading enough real examples to understand the experience.

Calculate the monthly total using software, usage, setup spread over your chosen evaluation period, human handling and ongoing ownership. Keep that calculation separate from cash savings. Avoid assuming released capacity equals reduced payroll, or that every resolved question would otherwise have required the same amount of human time.

When custom work is worth comparing

A native support product may be the best fit when your needs align with its supported channels, knowledge sources and actions. Custom work becomes worth evaluating when the valuable task crosses your CRM, order system, scheduling platform or internal approval process in a way the existing product cannot handle appropriately.

The right comparison is not “custom versus cheap software.” It is the total cost and usefulness of each complete operating model. Ask who updates policies, how action permissions are controlled and how the team works if the integration stops. The lowest subscription price can still leave expensive manual gaps.

  • Get the exact definition of every billable outcome and any minimum commitment.
  • Build the estimate from your request mix, not a generic automation percentage.
  • Include review, knowledge maintenance and escalated work.
  • Inspect customer outcomes separately from billing outcomes.
  • Confirm usage caps, renewal terms and a practical fallback before committing.

Sources and further reading

Find my biggest bottleneck