Chatbot Pricing Models: Per-Resolution vs Flat-Rate (2026)

Chatbot pricing follows five models: per resolution or per conversation (you pay each time the bot closes a ticket, like Intercom Fin at $0.99), per seat or per agent (help desks), per active contact or subscriber (ManyChat), per session, and flat-rate subscription with message fees passed through at cost. Usage-metered plans get more expensive the more your bot succeeds; flat plans stay predictable. Most US teams end up choosing between a bill that scales with volume and one that stays the same every month.

Last updated July 2026.

Before you compare feature lists, understand how each vendor plans to bill you, because the pricing model matters more than the sticker price. Two products at "$29" can produce wildly different invoices once real traffic hits. Here are the five models on the US market in 2026, what triggers a charge in each, and where the hidden costs hide.

The five chatbot pricing models, side by side

Every chatbot vendor uses one of five billing structures (or a blend). The unit they meter is the thing that decides your bill. Pick the wrong one for your volume and you can pay several times more for identical work.

How much does a chatbot cost per month?

A chatbot costs anywhere from $0 on a starter tier to several thousand dollars a month at scale in 2026. Simple rule-based bots and free tiers run $0 to $50 per month. Mid-market AI support tools land around $100 to $500. Usage-metered platforms have no ceiling: your monthly fee is base plan plus per-resolution or per-contact charges.

The monthly number depends almost entirely on which model you are on. On a flat plan, the figure is the figure. On a metered plan, your "monthly fee" is really a base subscription plus a variable meter that only shows up on the invoice. Intercom is the clearest example: seats run $29, $85, or $132 per seat per month on annual billing, and then Fin adds $0.99 per resolution on top with a 50-outcome monthly minimum. A team deflecting 2,000 tickets a month pays roughly $1,980 in Fin fees alone, before a single human seat. For a fuller breakdown, see our guide on how much an AI chatbot costs.

What is the average chatbot pricing?

There is no single average, because the models are not comparable, but a useful benchmark: entry AI support plans cluster around $15 to $70 per month, mid-tier around $100 to $500, and per-resolution platforms average close to $1 per resolved ticket. "Average chatbot pricing" quoted as one number is usually blending flat plans and metered plans that bill on different units.

Treat any single "average" figure with suspicion. A $29 flat plan and a $29-per-seat plan with a per-resolution meter are not the same product at the same price. When you see an average, ask what unit it is measuring: monthly subscription, per seat, per resolution, or per contact. The unit is the whole story.

What is chatbot as a service pricing?

Chatbot as a service (CaaS) pricing means you rent a hosted AI chatbot on a recurring subscription instead of building and hosting one yourself. You pay monthly or annually for the platform, and the vendor runs the infrastructure, models, and integrations. Pricing is usually a base plan plus usage: either message volume, resolutions, contacts, or a flat allowance.

The CaaS label covers most of the market now, from ManyChat to Intercom to MessageAgent. What separates them is still the meter. ManyChat prices by active contact, so your cost tracks how many unique people you message, which means a successful campaign raises your bill. Help desks price by seat and stack AI fees on top. The flat chatbot pricing approach keeps the platform fee fixed and passes the underlying carrier and Meta message fees through at cost, so the only variable is the real network fee, not a vendor markup.

Which chatbot pricing model is cheapest?

The cheapest model depends on your volume. At very low volume, a free tier or a small per-contact plan wins. But as ticket or message volume grows, flat-rate subscriptions with fees passed at cost become the cheapest, because per-resolution and per-contact meters scale up with your own success. The more work the bot does well, the more metered models charge you.

This is the hidden-cost trap, and it deserves a hard look before you sign anything.

The trap in usage-metered pricing

Here is the uncomfortable part of per-resolution pricing: you are punished for the exact outcome you bought the tool to produce. Deflect 500 tickets, pay for 500. Deflect 5,000, pay for 5,000. The vendor's revenue is tied to your ticket volume, which means the better the bot performs, the bigger your invoice. Success and cost move in the same direction.

Per-contact pricing has the same shape. ManyChat bills on active contacts, so a post that takes off, a busy Black Friday, or a seasonal rush all push you into a higher tier with no extra value delivered. Per-session pricing is the least predictable of all: a single busy support day can burn through what you budgeted for the month, and you cannot see it coming.

None of this makes metered pricing a scam. For a business with genuinely low and flat volume, paying only for what you use can be the right call. The danger is signing a metered contract while planning to grow. You are effectively agreeing to a tax on your own scale. Run your real numbers: take your monthly conversation or resolution volume, multiply by the per-unit rate, and compare that against a flat plan at the same volume. Do it at today's volume and again at double. The crossover point is often lower than buyers expect.

How to read a chatbot pricing page without getting surprised

Vendors rarely lie on their pricing pages, but they do lead with the number that looks smallest. A few questions cut through it:

• What is the metered unit? Seat, resolution, conversation, session, or active contact. This determines whether your bill is stable or elastic.
• Is AI billed separately from seats? With help desks it usually is. Intercom's pricing shows this clearly: seats and Fin resolutions are two separate line items.
• Are message fees marked up? SMS carrier fees and WhatsApp or Messenger fees from Meta are real costs someone has to pay. The honest approach passes them through at cost. Some vendors bundle them into an opaque per-message rate with margin baked in.
• Is there a minimum? Fin, for example, has a 50-outcome monthly minimum, so the meter never reads zero.
• What happens at a spike? Ask what a viral moment or a bad support week does to the invoice. If the answer is "it depends on volume," you are on an elastic plan.

ManyChat's entry tiers start in the low double digits per month and scale by active contact from there (verify current pricing on the vendor's site, since its tiers were restructured in early 2026). Front's Autopilot is quoted from $0.05 per conversation but is sales-gated, so the rate you actually get is negotiated. The pattern holds across the metered vendors: the headline number is a floor, not a forecast.

What flat, predictable pricing changes

MessageAgent runs on a flat monthly subscription. One AI agent answers, qualifies, books, upsells, and escalates across SMS, WhatsApp, Instagram DM, Facebook Messenger, web chat, and email in a single inbox, and the platform fee does not move when the bot handles more work. The carrier and Meta message fees are passed through at cost, so you pay the real network price with no per-resolution surcharge on top.

The practical difference is forecasting. With predictable chatbot pricing, your finance team can put one number in the budget and know it holds whether you deflect 500 tickets or 5,000. With metered pricing, you are forecasting a variable that goes up precisely when your marketing works. For a growing US team, that predictability is often worth more than a lower entry price, because the entry price is not what you end up paying.

Pick the model before you pick the product. Estimate your volume, run it through each meter, and check where the lines cross. If you expect to grow, a flat plan with fees at cost usually wins on total cost, and it always wins on predictability.