The price on a helpdesk's pricing page is rarely what you end up paying. The gap usually comes from a handful of predictable lines: who counts as a seat, which features sit on a higher tier or in a paid add-on, how AI usage is billed, what happens when you go over a limit, and what it costs to leave. None of these are hidden in a sinister sense. They are in the order form. They are just easy to skip when you are comparing headline prices.

This is the checklist we would use for any helpdesk contract, including ours.

Seats: who counts, and when you pay for them

Per-seat pricing is simple until you ask who needs a seat. Check these before you count heads:

  • Does everyone who replies to a customer need a full seat, or is there a cheaper light or collaborator role for people who only add internal notes or read conversations?
  • Do admins who configure the system but never answer customers need a seat?
  • Can you reassign a seat when someone leaves, and how quickly? Some contracts bill for the peak number of seats in the term, not the current number.
  • If you add seats mid-term, are they prorated, and do they renew at the same price?
  • Is the seat price tied to the plan tier, so that moving up a tier for one feature raises the price of every seat?

The last one is where costs jump. A single feature you need (SSO, a sandbox, an audit log, a higher API limit) can move the whole team to a higher tier.

Add-ons and tier-gated features

List every feature you need and find the cheapest plan that includes all of them, with any required add-ons. Common candidates for tier gating or separate add-ons include SSO, advanced reporting, custom roles, sandboxes, data residency, extra API capacity, and workforce management. The specific list differs by vendor, so read the vendor's current plan comparison page rather than relying on a comparison written by a competitor (ours included).

Ask whether add-ons are priced per seat, per account, or by usage. A per-seat add-on on a large team can cost more than the base plan.

AI add-ons: a second pricing model inside the first

Many helpdesks now sell AI features on top of seats, and they often use a different unit. Customer-facing AI agents are commonly billed per resolution or per outcome, and agent-assist features (drafting replies, summarising tickets) are often billed per seat. So you may be paying seats for your team plus a usage charge for automated conversations.

For usage-based AI billing, get the definition of the billable unit in writing, ask for an export of billed events, and ask what happens when you exceed any included allowance. We cover how to audit resolution definitions in deflection vs resolution.

Also check whether you can bring your own LLM provider or model, or whether the model is fixed by the vendor. That affects both cost and where your customers' messages are processed.

Overage and usage limits

Look for every limit in the contract that is measured by usage: conversations, resolutions, API calls, storage, attachments, automation runs, contacts. For each one, find out what happens at the limit. The answers range from a hard stop, to automatic overage billing at a stated rate, to a sales conversation at renewal. A hard stop on conversations in the middle of a busy month is an operational risk, not only a cost.

Channel costs that come from someone else

Some channels carry third-party charges no helpdesk can remove. WhatsApp Business messaging is billed by Meta according to its own pricing, on top of whatever your support platform charges; check Meta's current WhatsApp Business pricing for your countries. SMS and voice usually carry carrier or provider charges. When you compare platforms, put these on a separate line so they are not mistaken for a platform saving.

Migration and exit costs

The cost of leaving is part of the cost of staying. Check:

  • Can you export conversations, customer records, macros and knowledge-base articles in a documented format, on demand, without a support ticket?
  • Is there a charge for exports or for API access used during a migration?
  • How long after cancellation is your data kept, and can you request deletion?
  • How much of your setup (automations, routing rules, bot flows) is in a format that only works inside that product?

Migration effort is mostly your team's time: mapping fields, rebuilding automations, retraining agents, and running two systems in parallel for a while. Estimate it in hours, not in vendor promises.

Renewal terms

Read the renewal clause before the first signature. Check whether the contract auto-renews, how much notice you must give to cancel, whether prices can change at renewal and by how much, and whether annual discounts disappear if you drop seats. Put the notice deadline in a calendar.

Where LayBuild fits, and where it does not

LayBuild charges a flat monthly price per plan, with seats included: Starter is ₹1,499 a month with 5 seats and 1,500 conversations, Pro is ₹3,999 with 15 seats and 8,000 conversations, and Premium is ₹9,999 with 100 seats and 20,000 conversations. Annual billing lowers each price. There is no per-resolution fee and no per-seat add-on price. There is also no free plan and no discount for fewer seats. Current limits are on the pricing page.

The costs you would still carry are Meta's charges if you use the WhatsApp channel, and your own time for setup and review. If you self-host from our open-source repository, add your own infrastructure and the LLM provider bill for the key you bring.

It is also not a full helpdesk replacement for every team. LayBuild handles web chat, WhatsApp and a REST API, with human takeover in the dashboard. It has no email, SMS, voice, Slack or social channels, and no scheduled sync from tools like Zendesk or Confluence. If most of your volume is email tickets, you would run LayBuild alongside a helpdesk, not instead of one, and the contract checklist above still applies to the helpdesk.

Next steps

  • Take your current contract and fill in each section above with the real figure or "unknown". Every "unknown" is a question for your account manager before renewal.
  • Work out whether automation pays for itself with the ROI method.
  • If you are moving off Zendesk, read migrating from Zendesk to LayBuild.