Two AI support tools can both start at the same monthly price and produce very different bills. One might charge for generated replies. Another might charge when a ticket is resolved. A third might add AI usage to a helpdesk subscription.
Before comparing chatbot pricing, count the work you expect the tool to do. Then ask each vendor how that work becomes billable usage. A message, a conversation, a ticket and a resolution are not interchangeable.
Pricing models below were checked against the linked vendor pages on November 4, 2026. Use the current plan terms for a purchase decision. The arithmetic examples are hypothetical and are not quotes from any vendor.
Find out what the unit means
A shopper might ask three questions in one conversation. The AI could draft a reply, revise it, look up an order and hand it to a person. Different products can count that activity differently.
- Per reply or action: Ask which generated replies, checks or account actions consume usage.
- Per conversation or ticket: Ask when a new unit starts and how reopened conversations are handled.
- Per resolution: Ask exactly what counts as resolved and what happens after a human handoff.
- Subscription plus usage: Check what is included and the price of going over it.
You cannot reliably turn a quote for 1,000 resolutions into a price for 1,000 messages without understanding the underlying workload.
How the models appear in real products
Yuma's pricing page defines a full resolution around a ticket completed without human involvement. Check the quoted volume, commitment and any additional products you need.
Gorgias's billing guide describes helpdesk ticket charges and automated interaction charges, which can apply to the same fully automated ticket. Review the terms for your account and plan.
Brandwise documents credits for work such as moderation checks and generated replies. The mix of enabled features matters when estimating usage.
SmartReply uses credits for automated comments, messages or actions, as described on our pricing page. Check the plan allowance against the workflows you intend to enable. We publish this guide, so we include our own model rather than treating it as the default for the whole market.
Build a normal month and a busy month
Take a recent period and count conversations by the work they need. Separate public comments, private support, order questions and requests requiring actions. Include the follow up messages that make up the rest of the conversation.
Next, estimate a busy period using your own history. A promotion can increase comment volume without increasing order support at the same rate. A shipping delay can do the opposite.
Do not assume every conversation will be automated. Include the staff review time for exceptions, corrections and policy changes. Ask how a vendor bills those cases.
Use simple arithmetic before choosing a plan
For an illustrative plan, suppose the subscription is $100, it includes 1,000 billable units and extra units cost $0.10 each. If you use 1,400 units, the usage beyond the allowance is 400. The estimated software bill is $140 before tax and other charges.
That calculation only helps after you know what a unit means. If one customer conversation uses four units, 1,400 conversations will not fit into the same estimate.
You can use our AI support cost worksheet to record your normal and busy month. It leaves rates blank so you can enter the terms from your actual quote.
Ask what happens at the limit
- Does the product stop automating, use an overage rate or change your plan?
- Do unused allowances carry over?
- Are tests, drafts and moderation checks included in usage?
- Are the helpdesk, implementation and required integrations separate?
- Can you inspect the events behind the usage total?
Get the answers in the plan terms or quote. A low starting price is less useful if nobody can explain your busy month.
Compare cost with the result
During a pilot, track correct resolutions, repeat contacts and staff time alongside the software bill. A cheap reply that sends the customer back into the queue can cost more overall than a more expensive action that resolves the request.
For the messages behind those workflows, browse our customer service response templates. Each example includes the facts to check and the action that needs to happen next.
Use the same workload to compare products. Our ecommerce software guide explains how to test the workflow. For SmartReply's current allowances and plans, see pricing or bring your volume to a demo.