Skip to content
← Back to Blog

Per Conversation, Per Resolution, Per Session. Your Three AI Quotes Are Not Comparable.

One member asks three questions and leaves. Per conversation that is one billable event. Per credit it is at least three. The spread between those two is your annual number.

Three vendors have quoted your association for an AI assistant on the website. One charges per conversation, one per resolution, one per session. The numbers are all between fifty cents and two dollars, which makes them look like competing bids on the same thing.

They are not. Those three words describe three different events, and which one you are buying decides whether the annual number is four figures or five.

Where this sits. This is a companion to the post on what your vendors do with member data when they turn on AI. That one was about the contract. This one is about the invoice. Every figure below is from the vendor's own published pricing page, checked the week this was written, with the date noted because these change.

Five Vendors, Five Units

These are mainstream support and service platforms rather than association-market products, and they publish their prices, which is the reason we can use them to illustrate the problem.

  • Intercom Fin. Priced from 99 cents per Fin outcome, with no seats required to use it. Seats, if you want them, run 29, 85 and 132 dollars per seat per month across the three plans.
  • Zendesk. Pays only for requests the AI resolved without escalating to a person, at 1.50 dollars per automated resolution on a commitment or 2.00 dollars pay as you go, with a small monthly allowance included per agent seat.
  • Salesforce Agentforce. Two dollars per conversation, or a credit model at 500 dollars per 100,000 credits where individual actions consume anywhere from 20 to 120 credits depending on what the agent does. A user license is 5 dollars per user per month and requires the credits.
  • Freshworks Freddy. First 500 sessions included on every plan, then 49 dollars per 100 sessions. The separate Copilot that helps your staff rather than your members is 29 dollars per agent per month.
  • Microsoft Copilot Studio. Priced in credits per message rather than per outcome, and the rate depends on what the message does: a classic answer is 1 credit, a generative answer is 2, an agent action is 5, and grounding a message in your tenant data is 10.

Why the Words Matter More Than the Numbers

Line those up and the per-unit prices cluster. The units do not.

Take one member interaction. A member opens the chat, asks three questions, gets three answers, and leaves. Per conversation that is one billable event. Per session it is one. Per resolution it may be one, or three, or zero if the thing escalated to a person. Per message or per credit it is at least three, and more if any of the answers needed to look something up.

Same interaction, four different bills. Nobody is being deceptive. Each unit is a reasonable way to price the service and each vendor built its billing around its own architecture. But an association comparing three quotes on price is comparing three different definitions of what it is buying, and the spread between them is not small.

The structural difference. A resolution model only charges when the AI actually finished the job. A message or credit model charges for every exchange including the ones that went nowhere. Those two are structurally opposed, and which one favors you depends entirely on how often your bot is going to succeed, which is the thing nobody knows before deployment.

The Number Nobody Puts in the Quote

Every one of these models needs the same input to produce an annual figure, and it is the one your vendor cannot supply: how many of these events you will have in a year.

And association volume is lumpy. Associations have a specific shape here that general business benchmarks do not capture. Volume is not level. It spikes around renewal season, around the week registration opens for the annual meeting, around dues notices, around any deadline you set. A quote built on an average month will understate the months that matter and the overage rate is where the surprise lives.

What to do instead of guessing. Count the support emails and calls your staff handled in the same months last year, and separate the ones a bot could plausibly have finished from the ones it could not. That is a rough number and it is far better than the vendor's benchmark, because it is yours. Run it through each quote's own unit and you will have three annual figures that are actually comparable.

Terms Worth Finding Before You Sign

These are the clauses that move the real cost, and they are rarely on the pricing page:

  • Whether unused capacity rolls over. Salesforce states plainly that unused credits do not roll over. If your volume is seasonal and you buy for the peak, you are buying capacity you will not use in the quiet months.
  • What the overage rate is. Often several times the committed rate. Zendesk publishes 1.50 on a commitment against 2.00 pay as you go, which is a modest gap and an honest one. Not every vendor publishes both numbers.
  • Which actions cost more than others. If one answer costs one credit and the same answer grounded in your member data costs ten, then the configuration that makes the bot useful is the configuration that makes it expensive. Ask what a realistic answer actually consumes.
  • Whether the two models can coexist. Salesforce notes that Flex Credits and per-conversation billing are not supported in the same org. Picking the wrong one is not a preference, it is a decision you may have to live with.
  • And whether seats are still required. Several of these price the agent separately from the seats, which is good, and several bundle a staff-facing assistant at a per-seat rate on top, which is a second line item that arrives later.

The Part Specific to Association Vendors

Everything above comes from companies that publish their pricing. Here is what we found when we looked at the association market.

Nobody in this sector publishes a number. We checked the published pricing of the association-market platforms that sell member-facing AI, and could not find a per-unit price published by any of them. Not the AMS vendors, not the community platform vendors, not the association-specific chatbot products. Every one is quote only.

To be fair about why. That is normal for enterprise software and it is not evidence of anything underhanded. It does mean you cannot do the comparison above using only your sector's vendors, and it means the first question in the sales conversation has to be what unit you are being charged in, because you will not find it on a page beforehand.

How to use them anyway. The mainstream numbers above are useful to an association precisely because they are published. They are the anchor you take into a quote-only conversation, and a vendor quoting several times the published rate for a comparable unit should be able to say what you are getting for the difference. Sometimes the answer is good: association-specific integration, dues logic, member entitlement handling. Sometimes there is no answer.

Ask Three Questions Before the Demo

These take a vendor thirty seconds to answer and they tell you more than the demo will:

  • What is the billable unit? Conversation, session, resolution, message or credit. Get the word, then get the definition of the word, because resolution in particular means different things to different vendors.
  • What does one typical member interaction cost? Walk them through a member asking three questions and getting three answers. Have them tell you the number of billable units. Vendors answer this honestly and the answers differ enormously.
  • What happens in our busiest month? Then ask what happens to unused capacity, and what the rate is above the commitment. Those two together are the real annual number.

Send Us the Quotes

If you have two or three of these in hand, send them over with roughly how many support requests your staff handled last year and in which months. What comes back is each quote converted into the same unit so the numbers mean the same thing, an annual figure for each at your actual volume rather than an average month, the overage and rollover terms pulled out of each contract, and which of the differences are real capability against which are packaging.

We have told associations to buy none of the three before now, usually when the honest answer was that reconciling the content the bot would answer from was the actual project. If that is where this lands for you, we will say so, and that conversation is a great deal cheaper than the one that follows a year of paying per credit for answers drawn from a dues page that contradicts itself.

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article Your School District Is Not a Special District. Here Is Your Title II Date.