Ada Pricing Explained (2026): Plans, Costs & What to Watch For

Ada chatbot pricing isn't published on Ada's site. If you looked for a plans table on ada.cx and landed on a form to book a call, that is the pricing page. It has no tiers and no figures.

So this article does the sourcing for you. Below you'll find every public figure on Ada's cost, with its source and how much weight it deserves; how Ada bills; a worked model to run on your own volume; and the fees that land outside the quote.

That should be enough to size a five or six-figure contract before you commit 30 to 90 days to evaluating one. Pricing moves, and vendors package differently by region and billing term, so treat every figure here as a starting point for your own quote.

Key takeaways

• Ada publishes no pricing on its own site. ada.cx/pricing serves a demo-booking form. Every figure in circulation comes from a marketplace listing, procurement data, Ada's own blog, or a third party.

• Ada does publish its billing model. Its platform page states conversation-based pricing, where you pay for every conversation the AI agent has with an end user. A resolution-based model is available to enterprises that ask for one.

• Ada is built for high volume. Vendr's procurement data puts its smallest observed deployment band, up to roughly 25,000 conversations a month, at $30,000 to $70,000 a year in platform fees before usage or implementation.

• The lowest vendor-attached figure is $30,000 a year. It comes from Ada's own Salesforce AppExchange listing. Capterra's starting-price field says $60,000, and the two do not reconcile.

• The median Ada contract is $72,000 a year. Vendr records observed deals from $36,053 to $313,800, updated February 2026.

• Ada's own blog uses $0.35 per conversation and $1.50 per resolution. Both are illustrative figures in Ada's pricing-model post, and only one page in the current search results uses them.

• The quote is not the bill. Implementation, integrations, per-language fees, and a 3 to 7% annual uplift all sit outside it, on Vendr's contract data.

What is Ada CX, and who is it built for?

Ada is an enterprise customer-service AI agent that runs on top of an existing contact-center stack, sold to large support operations. The company is based in Toronto and is registered as Ada Support Inc., which is why directory listings still file it under Ada Support.

Scale explains the price bracket. Ada reported more than 550 enterprise AI agents deployed and 6.4 billion interactions in its March 2026 growth release, alongside 108% agentic AI ARR growth.

Its published customers are mostly high-volume consumer operations. Cebu Pacific, monday.com and Malaysia Airlines all run Ada agents. Ada builds for airlines and large marketplaces, which is why the numbers start in five figures.

How much does Ada's chatbot cost in 2026?

Most Ada customers pay between about $36,000 and $314,000 a year, with a median around $72,000. None of those numbers come from Ada.

Every public figure comes from one of four places: Ada's own published figures, a starting-price field on a software directory, aggregated procurement data, or an unsourced third party. Where a figure came from matters more than the figure.

Two contradictions are worth naming, because you will hit them yourself. Ada's own AppExchange listing says $30,000 a year and Capterra's starting-price field says $60,000, so ask which one your rep recognizes. Vendr's page also reports one purchase count in its body copy and a much smaller deal count in its stat block, without saying which population produced the $72,000 median.

Why the estimates spread so wide

The spread across those figures looks like disagreement. It is mostly three different things being quoted as if they were the same thing.

Some figures are a per-unit rate and some are a total annual contract. $1.50 and $72,000 are not competing answers. A $30,000 starting price and a $72,000 median can both be accurate, depending on which lines of the contract you count, which the next section breaks down. And the top of the range is one company running very high volume, so $300,000 describes one deployment and no list price at all.

Spendflo's $4,000 floor is the one figure that does not reconcile. It sits an order of magnitude below every other source's minimum, it is dated March 2025, and Spendflo labels it as an estimate. Treat it as an outlier.

How Ada's pricing model works

Ada bills on consumption, so a contract has a fixed part and a variable part. Ada's AppExchange listing calls the model consumption-based with economies of scale, which is the only place the company states the model in its own words on a marketplace, though it does not name the billing unit there.

Expect a quote to itemize three lines. Vendr's contract data separates recurring platform fees from one-time implementation in exactly this way, and Ada's own consumption language accounts for the usage piece.

• Platform fee. The recurring charge for access to the AI agent, sized to your volume.

• Usage commitment. A block of conversations bought in advance.

• Implementation and services. One-time setup, integration work, and any custom development.

Ada's own illustrative rate makes the shape concrete. At $0.35 per conversation, 10,000 conversations a month works out to roughly $42,000 a year in usage, before the platform fee or implementation. Run that on your own volume and hold it against the $72,000 median. If your usage number lands far above the median, Ada's own economies-of-scale language suggests the rate you get quoted will not be $0.35.

Buying usage up front has a consequence in both directions. A quiet year does not refund the unused block, and a busy year pushes you into overages. Ada does not publish its overage rates, so get them in writing before you sign anything.

Ada publishes no tier names at all, so there is no plans table to compare. Some pricing write-ups list tiers called "Starter/Growth" or "Professional/Business," which are third-party constructs built to organize the data. Those names will not appear on an Ada quote.

Discounts are available. G2's buyer data shows a 16% average discount on Ada contracts, and Vendr reports larger reductions on multi-year commitments and annual prepayment.

Does Ada charge per conversation or per resolution?

Ada charges per conversation. The Ada platform page carries a FAQ with this exact question, and the answer describes conversation-based pricing where you pay for every conversation your AI agent has with end users. Ada offers a resolution-based model to enterprises that ask for one, though it says most customers choose conversation-based. Some published comparisons still say Ada has never disclosed this, so check the date on anything claiming otherwise.

The model changes what you are buying. You pay when the AI agent handles a conversation, whether or not the customer leaves with a fix, so your cost tracks inbound volume more closely than it tracks outcomes.

Ada's case for it is reasonable. Resolution definitions are not standardized across vendors, so a resolution-priced contract prices something the buyer cannot audit. In Ada's words, "You pay for what your AI handles, not how it's labeled." Ada published the arithmetic too. On a hypothetical 500,000-conversation account, resolution-based cost more than triples by year three as the resolution rate climbs from 25% to 75%.

Two things temper Ada's argument. Its own Automated Resolution definition rests on four criteria, Relevant, Accurate, Safe and Contained, and Contained is the same no-handoff test Ada criticizes elsewhere, while its docs never tie resolutions to billing. A definition is also only unauditable if the vendor keeps it private. Model the cost curve whichever vendor you pick, but model it against your whole support cost, since rising automation moves work off headcount while it moves spend onto the meter.

So ask any vendor four questions. Which model is my quote on? What counts as a billable event? When does the clock stop on a conversation nobody resolved? And how do I audit the count against my own invoice? Ada answers the first on its platform page. The rest belong in the contract.

What Ada's features cost you

Ada chatbot features are also its pricing model, because almost everything you switch on either adds conversations to the meter or adds a line to the implementation quote. Four capability areas move the number most.

Channels and conversation volume

On conversation-based billing, every channel you enable feeds the meter, which makes channel scope the single biggest driver of your bill. Ada's platform page lists voice, email, chat, Messenger, WhatsApp, SMS, Instagram, in-app and custom channels.

There is a detail in the documentation worth checking. Ada's channel documentation gives Instagram its own setup page, then documents two other social paths, Sunshine Conversations and a Zendesk social integration. It names no setup procedure for WhatsApp, Messenger or SMS, so a channel you assumed was native may arrive through middleware you also pay for. Confirm the delivery path for each one you plan to run.

The Reasoning Engine and Playbooks

Playbook complexity is what drives professional-services cost, because every multi-step flow you need is configuration someone has to build and maintain. Ada launched its unified Reasoning Engine in February 2026, described as a patent-pending dual-reasoning architecture running one reasoning "brain" across every channel. Playbooks are the workflow layer on top, built from six step types (SEND, SET, ASK, RUN, IF/ELSE, GO TO). Ada's docs now name Playbooks the recommended path, and call the older block-based Processes "no longer actively developed."

Ada's own IPSY case study reports 90% of that customer's AI volume running through Playbooks, which shows how central the layer becomes once you are live.

Languages and voice

Each additional language is a negotiable line item in the implementation quote instead of a switch you flip, and the range sits in the cost table below. Ada's docs state support for 60 languages with native response generation and knowledge ingestion in each. Voice is a smaller set, and Ada's May 2026 voice update puts native voice support at 42 languages, with smart interruption handling and built-in noise cancellation. The 60-language figure covers response generation, while Ada's Knowledge API reference limits article content to nine languages.

Language capability itself is table stakes across this category, so the cost is the story.

Knowledge, integrations and security

Knowledge work is quoted as professional services, and it is one of the larger items in the cost table below. Ada documents four ways to get knowledge in: connect a knowledge base, import a website with daily syncs, write articles in Ada's dashboard, or push content through the Knowledge API. Content is capped at 50,000 articles by default, with higher limits on eligible plans.

Check your own knowledge stack against the documentation before you assume it is covered. Ada's integrations page names 25 integrations, 16 of them under content ingestion, while its knowledge integration docs carry setup procedures for eight of the 16. Ada documents no Confluence, Notion, Google Docs or SharePoint connector, and its docs say a knowledge base outside that list needs a custom integration built on the Knowledge API, arranged through your Ada team.

Ada's trust page lists SOC 2 Type II, PCI DSS, HIPAA, GDPR and AIUC-1, and its trust center adds a SOC 3 report, CCPA, CPRA, PIPEDA and a WCAG 2.1 AA VPAT. Certifications at that level are part of what an enterprise contract buys, and part of why Ada's floor sits in five figures.

What to watch for before you sign

The quote covers the platform and your usage commitment. Most of what surprises buyers sits outside it.

All five ranges come from Vendr's aggregated contract data, so treat them as what other buyers have paid. Ada publishes no fixed price for any of them. The annual uplift is one of the easier items to negotiate, and Vendr reports buyers capping it at 2 to 3%.

Check whether you are Ada's size. Ada publishes no minimum volume, and any figure presented as an official Ada threshold is worth checking, because the numbers circulating on comparison sites are uncited. Vendr's observed bands are more useful. Small deployments run up to roughly 25,000 conversations a month, at $30,000 to $70,000 in annual platform fees. Mid-sized deployments sit between 25,000 and 100,000 a month. Enterprise deployments run past 100,000. Find your own row before you book a call.

The free trial situation is unclear. Ada's own site and documentation do not mention a trial, a pilot or a sandbox anywhere we could find. Ada's AppExchange listing says a 14-day free trial is available, though that listing requires Salesforce Service Cloud, so its trial is scoped to the Salesforce package instead of Ada's platform. G2 and Capterra both say no trial is available, and TrustRadius says one is. Ask for a trial or a paid pilot explicitly, in writing.

Plan for a long payback. G2's buyer-reported figures put Ada at two months to implement and 13 months to return on investment. Some teams move faster. Two recent reviewers describe setup as easy, one of them an enterprise user reporting phase one live in about three weeks, so implementation effort with Ada is uneven instead of uniformly heavy.

Is Ada's chatbot worth the money? What buyers say

Ada's buyers rate the product highly and rate its price lowest. On G2 Ada holds 4.6 out of 5 across 173 reviews, and on Software Advice's breakdown, value for money is its joint-lowest sub-score at 4.3 against a 4.7 headline. Capterra, GetApp and Software Advice share one 15-review pool, so treat them as one sample.

The complaints are specific. An enterprise reviewer in February 2026 lists pricing first among their dislikes, and an April 2026 reviewer writes that "scaling this could become an issue because of the costs involved..." A mid-market head of customer service, writing on G2 in 2023, found after building out their instance that Ada did not support features it advertised, because their team runs Kustomer instead of Salesforce or Zendesk. Confirm which capabilities apply to your own helpdesk before you sign, since the answer changes what you are buying.

The praise comes from people running Ada at scale. A reviewer two years in reports ticket volume falling year over year while the business grew, and considers Ada worth the cost. One technical operations manager praised the drag-and-drop builder for making API calls that would take developer work elsewhere, then said Ada "upcharge ridiculous amounts for features" competitors include for free. That split verdict is a fair summary of the value question, though his review predates Ada's generative platform, so read the pricing half as history.

Ada vs the alternatives on price

Ada is the only tool in this comparison with no rate you can look up. The other three all have a per-unit figure in public, including Pluno, the AI support agent for Zendesk and Intercom that publishes this article.

Ada bills per conversation by default and offers a resolution-based model to enterprises that ask for one. Every rate above sits on top of a platform or seat cost, so a per-unit figure is a component of the bill instead of the bill.

Cheapest per unit is the wrong axis, because each vendor defines its unit differently. A resolution priced at one dollar and a resolution priced at two can describe very different amounts of work. What matters when you are budgeting is whether you can forecast the bill before you sign. Three of these four give you numbers you can model before you talk to anyone.

For the full comparisons, we broke down Intercom Fin AI pricing and Zendesk AI pricing separately, and put two of them head to head in Zendesk AI vs Ada. If you are building a shortlist instead of a budget, we also compared six Ada alternatives on resolution depth and cost.

If you're evaluating Ada, what to compare it against

If your support volume sits below the scale Ada is built for, the more useful comparison is between the AI layer options on the helpdesk you already run. One disclosure first: this article is published by Pluno, which sells an AI support agent, and most pages ranking for this query are written by Ada's competitors without saying so.

Vendr's smallest observed band still carries $30,000 to $70,000 a year in platform fees before implementation. If your volume puts you at the bottom of that band, the useful question is whether an enterprise contract fits your team at all. For a Zendesk or Intercom team, the live decision is which AI layer runs on the helpdesk you already pay for, the native AI or Pluno.

Pluno is an AI support agent for complex technical tickets that works inside Zendesk and Intercom. It ingests your resolved support tickets, which is what lets it handle issues your help center never documented, like a failed data import or an SSO configuration error. B2B SaaS products change faster than their documentation, so the answers to the hardest tickets usually live in ticket history and nowhere else.

Pluno's own economics are worth stating plainly. There is a flat monthly platform fee set by your ticket volume, a per-resolution charge on top of it, agent-assist and quality-scoring capabilities priced separately per seat, and a customer who stops replying counts as resolved once the published window closes. Ada bills per conversation, so the two are not the same model, and which unit costs less is not the useful question. Whether you can check the invoice is. Four things differ there.

• The rate is published. €0.90 per autonomous resolution (about $1.05), on Pluno's pricing page, alongside the platform fee. Which channels are in scope for autonomous resolution depends on your setup, so confirm yours before you model volume.

• The window is published. A ticket is marked resolved 72 hours after Pluno's last reply if the customer does not respond, which gives an unhelped customer time to come back before the charge lands.

• Escalations are never billed. A ticket that goes to a human is not a charge, so you do not pay for partial work.

• Every billed resolution is auditable. Each AI-resolved ticket is tagged in your helpdesk, so you can filter the tag there, and you can request an export of every AI-resolved ticket ID for any billing period.

Where Pluno falls short. It is built for complex technical support, so a team handling mostly straightforward FAQ traffic pays for capability it will not use. Learning from resolved support tickets depends on having ticket history, so a brand-new helpdesk takes longer to reach full value. A platform fee plus per-resolution pricing suits higher ticket volumes better than very small teams. And Pluno works inside Zendesk and Intercom, so a Salesforce, Freshdesk or HubSpot team is not the fit today.

The bottom line

• Get three numbers in writing before you negotiate: the platform fee, the size of the usage commitment, and the overage rate above it. Ada doesn't document any of the three publicly.

• Ask which model your quote is on. Ada bills per conversation by default and offers resolution-based to enterprises, and the two produce very different invoices at the same volume.

• Price the whole first year. Setup and integration work land in the same budget cycle as the platform fee, but they are quoted separately.

• Re-check every figure on the day you negotiate. Your own quote is the only figure that binds anyone.

• Run your shortlist against your own hardest resolved support tickets. Comparing real resolutions tells you more than comparing headline rates.

You can replace the range with a number. Book a Pluno walkthrough, and we'll model the cost against your own ticket volume. We can also run a free simulation on 50 of your resolved support tickets, so you can see the resolutions before you pay for anything.

Frequently asked questions

How much does Ada's chatbot cost per year? Most Ada contracts land between $36,053 and $313,800 a year, with a median around $72,000, according to Vendr's procurement data. Ada publishes no pricing on its own site. The lowest figure the company has attached to its own name is $30,000 a year, on its Salesforce AppExchange listing.

Does Ada charge per conversation or per resolution? Per conversation. Ada's platform page states that its conversation-based model charges for every conversation the AI agent has with an end user, and that a resolution-based model is available to enterprises with specific needs. Ada's own pricing blog uses $0.35 per conversation and $1.50 per resolution as illustrative figures, though neither is a quoted rate.

Does Ada have a free trial? Sources disagree, and Ada's own site and documentation do not mention a trial, pilot or sandbox. Its Salesforce AppExchange listing offers 14 days, but that listing requires Salesforce Service Cloud, so the trial is scoped to that package instead of Ada's platform. G2 and Capterra say no trial exists and TrustRadius says one does, so ask Ada directly and get the answer in writing.

What features does Ada's chatbot include? Ada runs across voice, email, chat, in-app and social channels, powered by a unified Reasoning Engine launched in February 2026 and a workflow layer called Playbooks. Its docs list 60 supported languages for response generation and 42 native voice languages. Ada's integrations page names 25 integrations across helpdesks, telephony and knowledge tools. On security its trust page lists SOC 2 Type II and AIUC-1 certification, along with PCI DSS, HIPAA and GDPR compliance.

Is Ada worth it for a mid-market support team? It depends on your volume. Ada's buyers rate it 4.6 out of 5 on G2 across 173 reviews, and score value for money lower than any other dimension. Vendr's smallest observed band still carries $30,000 to $70,000 a year in platform fees before implementation. At low volume, an enterprise contract with a 13-month reported payback is worth questioning before you start an evaluation. Our Ada alternatives comparison covers the options.