'Contact sales' pricing across 41 support tools: who hides it

Published prices on one side, a contact-sales quote on the other.

So start with one question: which tier, and which team size, would a sales quote actually cover? Every help desk, live chat tool and shared inbox in our pricing record sits under a published model: per seat, per ticket (Gorgias), per conversation (Tidio, Botpress, Landbot), a flat monthly plan (Crisp, Smartsupp, Helpjuice) or free with paid add-ons (Tawk.to). The quote-only entries sit somewhere else entirely, among AI agent specialists and knowledge tools.

Even the AI layer is mostly public. Our AI billing record, checked in October 2026, lists Tidio's Lyro from $39 a month for 50 AI conversations on monthly billing, or $32.50 billed annually, and Smartsupp's Mira AI Agent at $20 per 100 conversations a month on monthly billing, or $16 on an annual plan. Those are usage-based prices, with one-time free allowances and billing-term discounts, and the vendors still print them. The research section below walks through these findings.

Consider what happens when a buyer asks an AI assistant instead. Ask it for the vendor's price at your team size, and note whether the answer points to the vendor's own pricing page.

Which support tools hide their price behind contact sales?

Seven of the 41 support tools compared across 8 ranking pages quote only through sales, and every one of them sells AI agents or knowledge tools, not help desks or live chat.

Before you book a demo, run three checks on any vendor:

1. Find which pricing model the vendor uses: per seat, per volume, flat, free or custom quote.
2. If a price is published, note the tier where it stops.
3. If nothing is published, check whether the product is an AI agent or knowledge tool, where quote-only pricing is the norm.

Our pricing record sorts all 41 tools into 7 pricing models, with every price copied from the vendor's own pricing page and the date it was checked. The custom-quote group is short and specific: Ada, Sierra, Decagon, Voiceflow and Forethought on the AI agent side, plus Document360 and Guru for knowledge. Everything else publishes a number.

The common assumption is that hidden pricing runs through all support software. It does not. Help desks, shared inboxes, live chat and chatbot builders publish, which is why a team can size a budget in the customer support pricing comparison without a single call.

Guru shows what full hiding looks like. Its pricing page, checked Oct 30, 2026, offers a custom package built around scale, knowledge complexity and AI maturity, with no list price and no AI price. AI search and Knowledge Agents sit inside that package.

Partial hiding is the other pattern, and it sits at the top tier. Confluence publishes a free plan for 10 users, Standard at $7.15 and Premium at $14.10 per user per month for 10 users billed monthly, then routes Enterprise to contact sales (checked Oct 30, 2026). Small teams see a number. Large ones get a conversation.

Vendor marketing shows the same split. In a 2026 Issuetrak-run Reddit post ranking 10 Zendesk alternatives, Issuetrak, ranked first, was the only tool listed as "Custom," while the post itself named pricing transparency as its first selection criterion.

Use the table as a first filter: a tool in the bottom row will need a sales call, while every other row can be priced today. To be clear, Zazachat is an independent guide on the buyer's side, so neither group in this list pays for its place in it. That distinction matters most once you reach the enterprise column of a price list.

Is "our pricing is too complex to publish" a genuine reason?

Mostly not. Help desks already publish AI rates per resolution, outcome, session and interaction, so vendors that still quote are protecting room to negotiate, not hiding hard arithmetic.

The complexity excuse is old. In 2012, a poster on r/sysadmin wrote that the rationale they normally heard was that "pricing is complex, and quotes must be generated on a per-client basis." In that 2012 thread, the same buyer answered it directly: anyone with the right analytical ability "can crunch through 95% of the pricing schemes I've seen." Fourteen years later, the support market has tested that claim at scale.

Conventional wisdom says usage-based AI billing is too variable to list. Our AI billing record shows otherwise. Each vendor bills its AI in a different unit, and we compare them only in the vendor's own words, never converted into one another. Here is what mainstream support tools publish for usage that changes month to month:

Look at the last row against the third. Fin and Forethought both bill by outcome. One prints the rate. The other sends you to sales. Same unit, same variability, opposite disclosure. That is the clearest single test of the complexity claim in our data, and it fails.

The models themselves are not exotic either. The billing platform Orb lists six standard B2B SaaS pricing models (flat-rate, usage-based, tiered, per-user, feature-based and freemium) and names large public examples of each, including AWS for usage-based billing "for its vast collection of cloud computing resources." Every one of them can be printed on a page.

So what is the real reason? Founder-facing pricing advice is unusually candid about it. Enterprise prices are kept behind a sales screen because a price only moves one way once negotiation starts, which is down, and a high published number may scare prospects off before the anchor is set. Competitors also read published prices: Reuters reported in September 2026 that McDonald's pricing engine pulls public prices from nearby Wendy's and Burger King online menus. So ask any quote-only vendor which billing unit its quote is built on.

For a buyer, the distinction changes the conversation. A vendor hiding complexity needs your data to quote. A vendor protecting its anchor needs your budget. If you are weighing quote-only agents against ones that publish, the AI support agent rankings with prices show which side of that line each tool sits on, before you hand over a single figure about your own spend.

How can a small business get a real price without sitting through sales calls?

Start with published prices for your exact team size, copied from vendor pricing pages with dates, and enter any quote-only conversation already holding a published floor.

If hidden prices protect the vendor's room to negotiate, the buyer's job is to take that leverage back before the first call. I recommend four steps, in this order:

1. Price the publishers first. Build your shortlist from tools that print a price, and price them at your team size rather than the "from" figure on the banner.
2. Keep one listed competitor on every shortlist. A published alternative is your reference point when a quote arrives.
3. Check security requirements before pricing the top tier. Certifications decide which plan you need, so confirm them on each vendor's trust page first.
4. Book a sales call only with a floor in hand. Walk in knowing what the published option costs your team.

The first step is where most of the work hides. Our matcher holds 25 tools, and every published price in it is copied from the vendor's own pricing page with the date it was checked. That date matters because a price without one is a rumor. You can run your own numbers in the support cost calculator with AI included, which prices seats and AI usage together.

The second step is what seasoned IT buyers already do. In a 2021 r/sysadmin thread, one buyer said they would go to a competitor that lists its price, "even if it is more expensive," rather than spend 30 minutes or more on a sales pitch. Another described sitting through about 20 minutes of a "loop in their architect" pitch from Elasticsearch before they could ask the license cost of a single server. In the same 2021 thread, a third endured a heavy enterprise pitch only to learn the product cost $100 a month for the whole organization.

That last story is worth holding onto. Hidden does not always mean expensive. It does always mean slow.

The third step protects you from a quieter trap. A requirement such as a HIPAA BAA or SOC 2 report can push you up a tier, and the top tier is where quotes replace prices. The security certifications table lists, tool by tool, whether each of the 25 matcher tools holds SOC 2 Type II, offers a GDPR DPA or makes a HIPAA BAA available, as each vendor's own trust page states. Knowing which of those you need tells you whether a published plan can work at all.

For the fourth step, the free tools carry most of the load: a six-question matcher, the cost calculator and a security certifications table for the same 25 tools. If you want a second opinion on a quote, I take a free 15-minute call about a software choice, with no product to sell you on the other end of it. Bring the quote, the published alternative and your team size, and the gap between them usually tells you how much room the vendor kept for itself.

Will contact sales pricing disappear from support software?

Not at the top of the price list. Buyer pressure may push more mid-market vendors to print starting prices, but AI agent specialists and enterprise tiers show no sign of following yet.

The pattern in our pricing record is already settled. Watch the AI agent specialists: if Ada, Sierra or Decagon start printing a rate per resolution or per conversation, the line will have moved. Until then, ask every quote-only vendor to put its price for your team size in writing. The research section above walks through these findings.

A 2016 r/sysadmin thread shows what the choice costs a small buyer. In that 2016 thread, a non-profit with 60 users told NetApp its hard budget was $15k, sat through a one-hour presentation, and was quoted $30k. Commenters in the same thread warned that a vendor's first question is usually your budget.

So keep the budget to yourself. I take free 15-minute calls about a software choice, and I would rather see the quote next to the published price for your team size before you sign anything.