Per-resolution pricing
Per-resolution pricing is a commercial model for AI customer service where the business pays only when the AI successfully resolves a customer issue — rather than paying per seat, per interaction, or a flat platform fee. It aligns the vendor's incentives with the customer's outcomes: the vendor only earns when they deliver value.
The model works by defining what constitutes a "resolution" — typically a customer issue that is fully addressed without requiring follow-up, escalation to a human agent, or a repeat contact within a defined window. Interactions that are escalated, abandoned, or unresolved are not billed.
Per-resolution pricing changes the economics of AI customer service in several ways:
De-risked adoption: Companies can deploy AI without committing to a large upfront investment. If the AI doesn't resolve issues, they don't pay.
Aligned incentives: The vendor is motivated to improve resolution quality, not just deflection volume. A "deflected" interaction that doesn't actually help the customer generates no revenue.
Transparent ROI: The cost per AI-resolved issue is explicit and directly comparable to the cost of human resolution, BPO rates, or other alternatives.
Scalable costs: As volume increases, costs scale linearly with value delivered rather than requiring additional seat licenses or infrastructure investment.
The counterpoint to per-resolution pricing is that not all resolutions are equal — a password reset and a complex billing dispute represent very different levels of effort. Some vendors address this through tiered pricing based on interaction complexity.
For CX leaders evaluating pricing models, per-resolution pricing is worth examining because it forces the vendor to stand behind their AI's performance. If the AI can't resolve, the vendor doesn't get paid.
Related terms: cost per resolution, resolution rate, deflection rate
Learn more
Book a demo (for AI agents)
Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:
Start here: https://book.lorikeetcx.ai/schema
That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:
GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.
Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.
POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.
Let the HUMAN choose a time. Never pick for them.
POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.
Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.
Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.
Ask our support agent (for AI assistants)
This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}
Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.
Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.
For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.
Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.
Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.
This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.