The short answer
Zendesk and Intercom are built for support organisations with headcount, process and someone who owns the tool. A five-person business uses a fraction of that surface area and pays per seat and per resolution for the rest. The realistic requirement is answering the repetitive share, triaging the remainder with context, and cancelling next month if it does not work.
Zendesk and Intercom are not bad products. They are extremely good products, built with care for a specific buyer: an organisation with a support department, a person who owns the tooling, and enough volume that routing rules and SLA policies earn their configuration. If that describes you, buy one of them and stop reading.
This is about the much larger group of businesses who evaluate those tools because they are the ones everybody has heard of, and who then discover they have bought a control panel for an aircraft they do not fly.
What you use, and what you pay for
Run the exercise honestly. Of everything in an enterprise helpdesk, what would a five-person business genuinely touch in a month?
You would use the inbox. You would use a knowledge base of some kind. You would probably use the AI answering, because that is the part that removes work. Everything else - SLA policies, skills-based routing, macros, triggers and automations, satisfaction surveys, workforce management, custom objects, sandbox environments, the reporting suite - is either configured once and forgotten or never configured at all.
That is not waste in the vendor's design. It is the correct feature set for a support department. It is simply not the feature set you are buying it for, and you are paying for it per seat, every month.
| Capability | Enterprise helpdesk | What a five-person team needs |
|---|---|---|
| Answering repetitive questions | Yes, often priced separately | Yes - this is the whole job |
| Triage with full context | Yes, via queues and views | Yes, but without configuring queues |
| Knowledge base | Yes, full CMS | Yes - five documents, not a CMS |
| SLA policies and escalation matrices | Yes | No - there is one escalation path: you |
| Skills-based routing | Yes | No - there are three people |
| Workforce management, shift planning | Yes | No |
| Reporting suite | Extensive | Four numbers, monthly |
| Implementation effort | Weeks, often with a partner | An afternoon, or it does not happen |
The two pricing models underneath
Per-seat pricing is the one that catches small teams first, and it catches them in a specific way: it prices access. The cost of letting a second person see the support inbox is another monthly line, which quietly encourages the worst possible arrangement - one person holding all the context and nobody able to cover when they are away. For a five-person company that is not a support process, it is a single point of failure with a subscription attached.
Per-resolution pricing is subtler and reads better on the page. You only pay when the AI actually solves something, which sounds like the fairest deal in software. Read it from the other side: a good month costs the most. Every gap you close in your knowledge base raises the share of questions resolved, and therefore your invoice. You are paying a fee that rises in proportion to how well the product works, and 'resolution' is defined by the vendor's billing logic rather than by you. The full cost arithmetic is here.
Per-seat pricing charges you for having a team. Per-resolution pricing charges you for the product working. Neither is a scam - both are just built for someone with a bigger budget than yours.
The implementation cost nobody quotes
The line item you can see is the subscription. The one you cannot is the fortnight.
Enterprise helpdesks assume an owner - somebody whose job includes configuring views, writing macros, mapping business hours and SLA targets, connecting the CRM, and then maintaining all of it as the business changes. In a large company that is a role. In a five-person company it is the founder's evenings, and it competes directly with the work that makes money.
The practical consequence is not that the configuration is done badly. It is that it is done once, at signup, and never revisited - so the routing rules describe a business that stopped existing eight months ago, and everyone works around them.
What the smaller requirement actually looks like
Strip it back to what has to be true for support to stop hurting, and the list is short.
- The repetitive questions get answered instantly, at any hour, correctly, from documents you control.
- Answers are checkable - each one names the document it came from, so a wrong answer is a document you edit.
- Anything the agent cannot answer reaches a person with the full transcript, so nobody repeats themselves.
- You can see what customers asked and what you could not answer, which tells you what to write next.
- The whole thing installs in an afternoon and cancels next month if it does not work.
That list is small enough to deliver without an implementation project, which is the entire argument. Everything an enterprise platform adds beyond it is real value for a support organisation and overhead for a business of five.
Where the honest line sits
There is a point where the bigger platform is right, and pretending otherwise would be selling badly. When you have a dedicated support function with more than a handful of agents, when SLA enforcement is contractual rather than aspirational, when you need shift planning and quality scoring, when support reporting goes to a board - at that point the surface area stops being overhead and starts being the point. Migrating up is a good problem and a normal one.
Below that line, the question is not which platform is best. It is which parts of a platform you would actually use, and whether you want to pay per seat and per resolution for the rest while you find out. The pricing page is a flat monthly plan you can cancel, and if you have a help centre already, its articles are the fastest knowledge base you will ever build.
Frequently asked questions
Is VaaniAPI a full helpdesk?
No, and deliberately. It covers AI answering from your documents, the escalation inbox, conversation analytics and knowledge management. There are no SLA policies, routing matrices, CSAT surveys or marketing tours - that focus is why setup takes minutes rather than a quarter.
What does per-resolution pricing actually cost?
It costs most in your best month. Every improvement to your knowledge base raises the share of questions resolved, and therefore the bill. Flat pricing means a customer who asks eight questions costs the same as one who asks none.
Can I migrate my existing help centre content?
Yes. Export the articles and upload them as documents; the knowledge base is rebuilt in minutes. Structure matters more than volume - short single-topic documents retrieve better than one long export.
When should a small team actually buy Zendesk or Intercom?
When you have a dedicated support function, need SLA enforcement and workforce management, or run support as a department with reporting lines. At that point the platform surface stops being overhead and starts being the point.
