YundaDeskWhen AI support vendors charge by “resolution,” many sellers read it as performance-based pricing. It sounds cleaner than seats, conversations, or tokens. But budgets expose the hard questions: What counts as a resolution? Does silence count? If AI hands off to a human, is that billable? What happens when promotion volume doubles?
This article breaks down per resolution pricing. The model is not bad. It ties the vendor to an outcome. But it also creates uncertainty because you are not buying a fixed usage bucket. You are paying for every event the platform defines as resolved. For cross-border e-commerce teams, the better promise is often this: do not promise a fixed resolution rate, but make the cost boundary clear.
Per-Resolution AI Pricing Explained for Sellers: stress-test the plan with channel cost ranges
What per-resolution pricing actually charges for
Per-resolution pricing means the AI support product charges when AI is judged to have resolved a customer request. Products such as Fin may call this an outcome; Zendesk describes AI agent usage around automated resolutions.
That differs from seat pricing. Seat pricing asks how many teammates use the product and which plan they are on. Per-resolution pricing asks how many customer issues AI resolved. The key detail: a resolution is not a natural fact. It is a billing definition. A platform may count a resolution when the customer confirms it, when the customer stops asking for help, when AI completes a workflow, or when the conversation avoids human escalation. Before comparing unit prices, ask exactly which events become billable.
Why it feels fair, and where it really helps
The appeal is clear. Per-resolution pricing makes the AI vendor accountable for outcomes, not just access to software. If AI handles repetitive questions, the bill grows with value delivered. If it cannot handle them, you should not pay a resolution fee for those misses.
It tends to work best when:
- Support topics are standardized, such as shipping, delivery timing, size guidance, and return policies
- The knowledge base is clean enough for AI to answer from approved sources
- The team wants to test AI support before committing to a larger package
- Monthly support volume is predictable enough for a reasonable forecast
Cross-border e-commerce only partially fits that picture. Shipping and policy questions are good AI-first candidates. But channels, languages, campaigns, and market conditions change quickly. Volume and complexity often rise together. The model can be fair while the budget remains hard to forecast.
The uncertainty sits inside the resolution definition
The bill is shaped not only by price per resolution, but by counting rules. Take a simple conversation: a customer asks when an order will ship, AI answers from the knowledge base, the customer does not ask anything else, and the conversation closes. That will likely count as a resolution.
But what if the customer then asks to change the address, AI gives instructions, the customer cannot find the option, and a human agent takes over? Does that still count? The answer depends on the product, configuration, reporting logic, and contract terms.
| Counting question | What sellers should ask |
|---|---|
| Multi-question conversations | If one conversation contains several issues, is it one resolution or more |
| Silent close | Does no customer reply count as resolved |
| Human handoff | Can AI-first, human-backed conversations still be billable |
| Workflow completion | Does completing an order lookup or procedure count as an outcome |
| Disputes | Can merchants challenge or reverse a counted resolution |
Why cross-border bills can jump
Cross-border support volume is not linear. Promotions, ad spend, logistics delays, marketplace events, and social spikes can lift inbound questions quickly. A per-resolution bill moves with the number of issues AI resolves.
Suppose you usually receive 8,000 monthly conversations. During a peak campaign, volume rises to 20,000. If your knowledge base is ready, AI may resolve more repetitive questions, which also means the bill can rise sharply. That is not necessarily unfair. It is how the model works: more resolved issues create more billable events.
Channels make this harder. Website widget, email, WhatsApp, Messenger, Instagram, TikTok, LINE, Telegram, and Zalo may all be active at once. The same customer may ask about the same order in two places. If identities are not merged, both resolution counts and workload can be inflated. For the inbox side, start with how an omnichannel inbox reduces cross-channel switching.
Included credits: not free usage, but a clearer boundary
YundaDesk takes a different route: AI credits are included in every plan, with no per-conversation or per-resolution surcharge. This does not mean AI has no cost. It means the usage allowance is bundled into the plan so the team can see the budget boundary first.
That matters: finance can estimate monthly spend early; support leads can plan peak capacity around credits; teams do not need to suppress AI usage just to avoid extra resolution fees; and evaluation shifts back to which issues AI should answer first.
| Pricing model | Strength | Risk |
|---|---|---|
| Per resolution | Tied to outcomes, easy to start at low usage | Counting rules can be complex, peak-month bills may swing |
| Per seat | Stable budget, easy staffing model | AI usage and AI impact may not match the bill |
| Plan with AI credits | Clearer cost boundary, better for monthly planning | Teams still need to check whether credits match peak demand |
YundaDesk does not promise a fixed resolution rate, because resolution rate depends on the knowledge base, product category, policy clarity, and channel mix. What it can make clear is the cost boundary, escalation rules, and human backup: AI answers first; if it cannot answer, the customer asks for a human, or risk is high, it hands off.
Do not hand high-risk decisions to AI just to save money
Some teams respond to per-resolution pricing by chasing a higher automation rate. They avoid handoffs, close more conversations automatically, and keep AI in charge for longer. That is dangerous around refunds, compensation, price changes, and complaints.
In cross-border support, the expensive mistake is not usually one AI resolution fee. It is a wrong promise that creates financial loss, chargeback risk, or a public complaint. Refunds, compensation, and price changes should always require human approval. AI can calm the customer, collect order details, and summarize the conversation. It should not execute high-risk actions by itself.
YundaDesk applies the same principle to learning. When AI fails, an agent answers, or an agent corrects AI, the system creates a learning suggestion. It only takes effect after the owner reviews and approves it. Every change is traceable, testable, and revertible. Getting smarter over time should not mean becoming more reckless.
How to judge whether an AI support price fits
Do not compare pricing pages in isolation. Use your own last 30 days of conversations, or your last peak-season export, and model the cost from real topics:
- Group conversations by theme: shipping, delivery timing, product questions, returns, complaints, discount codes
- Mark which topics AI can answer directly and which should be AI-first with human backup
- Estimate peak-month volume, not just an average month
- Ask for the resolution definition, handoff billing rules, minimum commitments, and overage rules
- Check whether reports let you trace every counted resolution
If a vendor talks about a high resolution rate but cannot explain counting logic, dispute handling, and high-risk boundaries, slow down. Predictable billing often matters more than a polished automation story. For a broader framework, read how to choose an AI support platform for cross-border sellers.
The strength of per-resolution pricing is paying for outcomes. The risk is that the outcome must be defined by someone. For multi-channel, multilingual, promotion-driven support, start with a clear cost boundary, a solid knowledge base, and human backup rules.