Enterpret vs Chattermill vs SentiSum Pricing: What Support Ticket Analysis Software Costs

Read first-party on 10 September 2026, only one of the three leading support ticket analysis vendors publishes a price, and the price it publishes is a floor of $100,000 a year. SentiSum states "One annual partnership. From $100,000" on its pricing page. Chattermill's pricing page does not exist as a page at all: chattermill.com/pricing returns a permanent redirect to its demo booking form. Enterpret's is worse, in the sense that enterpret.com/pricing returns a 404 and no pricing page is linked anywhere on the site. That single published number is the most useful thing in the category, because it tells you what the two vendors who hide their pricing are hiding it against.

How much does support ticket analysis software cost?

Here is the complete picture across the three vendors that dominate this category, read directly from their own sites rather than from a review aggregator.

Two of the three do not merely decline to quote a rate. They have removed the concept of a pricing page. That is a different signal from a vendor who publishes tiers and marks them "contact us", because a tier list at least tells you how the product is packaged and roughly where you sit in it. Here you get nothing to anchor on before the first call.

What does SentiSum cost?

SentiSum sells one thing, called the CX Intelligence Layer, and it starts at $100,000 a year on an annual partnership. That price covers every conversation read across your channels, which SentiSum lists as tickets, calls, chat, surveys, reviews and bot transcripts, plus a custom taxonomy built on your own data, unlimited users, SSO, API access and all integrations set up by their team.

Two agents are included in the base number: the Insights Agent, which answers plain-English questions about your customers, and the Early Warning Agent, which does anomaly detection and alerting on conversation volume and themes. Three things are not included and are priced separately: the Quality Agent, which scores conversations against a rubric and produces coaching lists; the Automation Agent, which resolves and routes conversations; and MCP server access, which plugs the platform into your own AI stack.

SentiSum's own reasoning for splitting those out is worth quoting, because it is unusually direct: they carry their own model costs and deliver separately measurable returns, so the vendor prices them on their merits "rather than padding the core price for everyone". Whether you find that fair or find it unbundling depends on how many of the three you end up needing, and most buyers should assume the real first-year number sits above the headline.

The part of SentiSum's model that matters more than the price

SentiSum states plainly that it does not meter usage. Volume is agreed in annual bands, and if your operation outgrows the band you negotiate the next one at renewal or buy a volume pack mid-term. Their words: no per-ticket metering, no surprise invoice.

For a support organization that is the single most valuable term in the contract. Ticket volume is the one number you cannot forecast, because it spikes exactly when something goes wrong, which is exactly when you most need the analysis running. A per-ticket meter charges you most in your worst month. A volume band does not. If you are comparing quotes and one vendor meters per ticket, model your worst month rather than your average one before you compare the two figures.

The other unusual term is the risk structure. SentiSum offers a free scoped audit first, on a read-only slice of your own data with PII redacted, and then a walk-away right in the first 90 days of the paid partnership. A six-figure annual commitment with a 90-day exit is a materially different purchase from a six-figure annual commitment without one, and it is worth asking the other two vendors whether they will match it.

Why does Chattermill not publish pricing?

We cannot tell you Chattermill's reasoning, but we can tell you exactly what its site does. A request to chattermill.com/pricing returns an HTTP 301, which is a permanent redirect, pointing at /book-a-demo. The homepage links no pricing page. So the answer to "what does Chattermill cost" is structurally unavailable: the vendor has decided the only route to a number is a sales conversation.

Chattermill positions itself more broadly than pure ticket analysis, connecting support data to voice of customer programs and to metrics like NPS and CSAT. Broader scope usually means a larger and more variable deal, which is a common reason vendors stop publishing. It does not tell you whether the number is above or below SentiSum's floor.

Why does Enterpret not publish pricing?

Same outcome, blunter implementation. enterpret.com/pricing returns a 404. There is no pricing page to redirect from, and no pricing link in the site navigation. Enterpret is the largest of the three by brand search volume in the US, which makes the absence more conspicuous rather than less.

One practical consequence: when a vendor publishes nothing, the numbers that circulate about it come from review sites, procurement leaks and sales decks, and those figures are unverifiable. Treat any specific Enterpret or Chattermill annual figure you find online as a rumor until it appears on a document with the vendor's name on it. We are not going to repeat any here, because we could not confirm one.

Is $100,000 a year normal for support ticket analysis software?

It is normal for this specific tier of the category, and it is not the whole category. The three vendors above sell to enterprises with very large conversation volumes, typically tens of thousands of tickets a month across several channels and often several languages. At that scale a six-figure annual number is in line with what enterprise experience platforms cost, and SentiSum's floor is a reasonable proxy for where the others start.

What it does not represent is the price of analyzing support tickets in general. A team doing 2,000 tickets a month is not the buyer these three are built for, and a $100,000 floor prices that team out entirely. The honest read of the published number is that it draws a line: above roughly that volume the enterprise platforms make sense, and below it you are looking at a different class of product, or at the text analytics features already bundled into the help desk you own.

It is worth checking what you have already paid for before you shop. Zendesk, Intercom and Freshdesk all ship some degree of ticket classification and sentiment tagging in their higher tiers, and we broke down where those tiers actually sit in our Zendesk pricing breakdown. Buying a six-figure analysis layer on top of a feature you already own is a common and expensive mistake.

What actually drives the price in this category?

Since only one of the three publishes anything, the useful exercise is understanding the variables the quote is built from. Across all three the same factors recur.

• Conversation volume. The number of tickets, chats, calls, reviews and survey responses read per year. This is the primary axis everywhere, whether it is metered or banded.
• Channel count. Voice and call transcripts cost more to process than text tickets, and adding a channel usually reprices the deal rather than sliding it up a tier.
• Languages. Multi-language taxonomies are a genuine cost driver and a common source of quote variance between vendors.
• Taxonomy work. How much custom model building happens on your history. SentiSum says onboarding analyzes 6 to 12 months of history, which is real work and it is priced in.
• Add-on modules. Quality scoring, automated routing and API or MCP access are separately priced at SentiSum and are likely to be separately priced elsewhere.

Notice what is absent from that list: seats. All three sell unlimited or effectively unlimited users, which is now standard at the enterprise end of feedback analytics. If a vendor in this category quotes you per seat, that is the anomaly and it is worth asking why.

What to ask before you take a quote to finance

Because two of the three publish nothing, the comparison work falls entirely on you. Five questions make the quotes comparable.

• Is volume metered per conversation or agreed as an annual band, and what happens if we exceed it mid-year? This is the question with the largest financial spread in the whole contract.
• What exactly is in the base number, and which capabilities are separately priced modules? Use SentiSum's split as the checklist: quality scoring, automation and routing, and programmatic or MCP access.
• Does the price cover all channels we named, including voice, or only text?
• Is there a walk-away right or a success metric agreed at signature? One vendor publishes a 90-day exit. Ask the others to match it in writing.
• Does our data train models shared with other customers? SentiSum states in writing that it does not. Get the same sentence from anyone you are seriously considering.

One more scoping question, and it is the one buyers skip. Support tickets are only the customers who bothered to contact you. The angrier and more valuable signals are often public, sitting in app store reviews, marketplace listings and social posts that never touch your help desk, so it is worth tracking what people say about your brand outside your own channels in parallel rather than assuming the ticket queue is the whole voice of the customer. If public reviews are the bigger part of your problem, our review analysis software page covers that side specifically, and buying a ticket-only platform to solve it would be an expensive miss.

How we got these numbers

Every claim on this page was read directly from the vendors' own sites on 10 September 2026, using a US desktop browser profile so the figures are the ones a US buyer sees. The SentiSum figure and terms come from sentisum.com/pricing and its FAQ. The Chattermill and Enterpret findings are HTTP responses: chattermill.com/pricing returned a 301 redirect to /book-a-demo, and enterpret.com/pricing returned a 404, both verifiable in a browser in about ten seconds.

Vendors change pricing and packaging, and SentiSum's floor in particular is the kind of number that moves. Confirm on the vendor page before you sign anything. We re-read the pricing pages in this category every four to six weeks and date every figure for that reason.

Where UserInsight fits

All three of these platforms are built to read the support queue extremely well. The limitation they share is that a ticket tells you what a customer complained about, not what that customer was doing in the product immediately before they gave up, and the second half is usually where the fix lives.

That join is the job UserInsight does. It unifies product usage with support tickets, reviews and survey replies from the same users, clusters the recurring reasons, and ranks them by how many accounts and how much revenue they touch, with every finding traced back to the source evidence behind it. Our support ticket analysis page covers how the theming works, and text analytics tools covers the broader category these vendors sit in. In the interest of not wasting your time: UserInsight is pre-launch, with a waitlist rather than a checkout, so if you need a platform live this quarter, buy one of the three above.