LayBuild vs Intercom Fin: helpdesk suite or flat-priced bot

Intercom and LayBuild are different kinds of product, and most of the decision follows from that. Intercom is a complete helpdesk (inbox, tickets, help center, outbound messaging) with an AI agent, Fin, billed per outcome. LayBuild is an AI agent that answers from your documents on a web widget, WhatsApp and a REST API, for a flat monthly price, and it has no ticketing system or email channel.

If you need a helpdesk, LayBuild does not replace one. If you already have a helpdesk, or your team is small enough that a shared inbox is overkill, the comparison gets more interesting. Every Intercom fact below comes from Intercom's pricing page (checked September 2026).

Who each product fits

Intercom fits a support team that wants one vendor for everything: conversations across chat, email, SMS, WhatsApp and phone, a ticketing system with SLAs and round-robin assignment, a public help center, and an AI agent inside the same inbox. Its pricing page also offers Fin on its own for teams that keep another helpdesk, naming Salesforce as one example.

LayBuild fits a team that wants an AI agent grounded in its own content, with a predictable monthly bill, and is fine handling escalations through our dashboard or its own tooling. It also fits teams that want to run the whole stack themselves: the source is on GitHub and ships with a docker-compose file (Postgres, Redis, Qdrant, API, web, nginx).

How the pricing models differ

Intercom charges two things. Seats: Essential is $29, Advanced $85 and Expert $132 per seat per month billed annually, and the page's structured data lists $39, $99 and $139 for monthly billing. Usage: Fin costs $0.99 per outcome, and WhatsApp, SMS, phone and email campaigns are pay-as-you-go on top.

The definition of an outcome matters more than the price. Intercom counts one when the customer confirms the issue is resolved, when the customer does not ask for more help after Fin responds, or when Fin completes a workflow (a Procedure), including handoffs. It charges once per conversation even if Fin answers several questions. The second condition means a customer who reads Fin's answer and closes the tab can count as an outcome.

LayBuild charges a flat monthly fee in INR with a conversation cap. There is no per-resolution charge, and nothing extra per seat inside the plan's seat count.

A worked illustration, with numbers you should replace with your own. Suppose three agents on Intercom Essential billed annually, and 2,000 conversations a month reach Fin, of which 1,000 count as outcomes. That is 3 × $29 = $87 in seats plus 1,000 × $0.99 = $990 in outcomes, so $1,077 a month before channel fees. On LayBuild Pro, the same 2,000 conversations fall inside the 8,000 cap for ₹3,999 a month plus your LLM provider's token charges. The gap widens as volume grows, because Intercom's bill scales with outcomes and ours only moves when you change plan.

The flat price has its own risk. You pay the same whether the bot resolves half your volume or almost none of it. Per-outcome pricing puts some of that risk on the vendor.

Where Intercom is stronger

Be clear-eyed about this list, because for many teams it decides the question on its own.

• Intercom is a helpdesk. It has a shared inbox, a ticketing system, multiple team inboxes, round-robin assignment and SLAs. LayBuild has a conversation list with human takeover, not tickets.
• Intercom answers email. Its page says Fin answers email, live chat and phone. LayBuild has no email, SMS, Slack or phone channel.
• Intercom has a help center product, including private and multilingual help centers on Advanced. LayBuild has no public help center.
• Fin can take actions on external systems, according to Intercom's page. LayBuild's "API tools" are simpler: after the answer is generated, attached HTTP tools are called with their configured defaults and the first successful result is returned. The model does not pick tools or extract arguments.
• Intercom's Expert plan lists SSO and HIPAA support. LayBuild has no SSO or SAML, and holds no SOC 2, HIPAA, ISO 27001 or GDPR certification.
• Intercom names Salesforce among the helpdesks Fin works with and has an integrations catalogue. LayBuild has no native Zendesk, HubSpot or Salesforce integration; you connect systems through four outbound webhooks and the REST API.

Where LayBuild is different

These are differences, not trump cards. Whether they matter depends on your constraints.

The bill is predictable. Your cost per month is the plan price plus model tokens, and neither depends on how a vendor defines an outcome.

You choose the model. LayBuild runs on Hugging Face by default (meta-llama/Llama-3.1-8B-Instruct) and supports OpenAI, Google Gemini, DeepSeek, Qwen, Cloudflare Workers AI, OpenRouter, NVIDIA and any OpenAI-compatible endpoint, chained with a circuit breaker so one provider failing does not take the bot down.

Answers are restricted to your content. Strict knowledge-base mode is always on. If retrieval finds nothing, we skip the LLM and send a fixed reply. After generation, if fewer than 25% of the answer's stemmed words appear in the retrieved sources, we replace the answer with the same fixed reply: "I do not have specific information about that in the knowledge base." That check is lexical, so it can block a correct paraphrase and can pass a wrong answer that reuses source vocabulary. It reduces invented answers; it does not eliminate them.

You can self-host. If your security review rules out sending conversations to a SaaS helpdesk, running LayBuild on your own infrastructure is an option. Intercom's pricing page lists only its hosted plans.

What LayBuild does not do

Read this before you buy, not after.

• No ticketing, SLAs, macros or help center.
• No email, Slack, SMS, Telegram, Messenger or voice channel. WhatsApp voice notes, images and video are rejected as unsupported.
• No knowledge sync from Notion, Confluence, Google Docs, GitHub or Zendesk. You upload files (PDF, DOCX, PPTX, XLSX, CSV, TXT, Markdown and others, 10 MB default max) or list URLs one by one. We fetch only the URLs you list, with no crawling and no scheduled re-sync. Plans cap documents at 10, 25 or 50 and URLs at 5, 25 or 50.
• Retrieval is English-first. The default embedding model and the full-text search are English. The bot replies in the customer's language, but retrieval for a non-English question against English docs is weaker.
• Handoff on request is off by default (the ALLOW_HUMAN_HANDOFF org setting). When it triggers, either because the customer asks for a human or because the conversation passes 25 AI turns, the status flips to HANDOFF, agents get a real-time alert and a webhook fires. There is no AI summary on handoff and no sentiment detection.
• The learning loop publishes without review. After each qualifying AI reply, we save the exchange as a knowledge doc and Q&A pair with no human approval, and retract it only if the customer rates the conversation 2 stars or lower. A wrong answer that nobody downrates can end up in your knowledge base, so review what it has learned regularly.
• Outbound webhooks have no retries or dead-letter queue. Deliveries are logged, so you can see failures, but you have to replay them yourself.

How to choose

Pick Intercom if you need the helpdesk as much as the AI: email support, tickets with SLAs, a help center, or compliance features like SSO and HIPAA support. You will pay per seat and per outcome, and in exchange you get one system for the whole support operation.

Pick LayBuild if the job is answering repetitive questions on your website or WhatsApp from documentation you control, you want a fixed monthly cost in INR, and you either have no helpdesk yet or are happy to keep one alongside us. Keep your existing helpdesk for email and tickets and route escalations to it through the handoff webhook.

Before you decide, measure one number: over a month, how many of your conversations are answerable from your docs alone? That share tells you what Fin's outcome bill would look like and how much a flat-priced bot can cover.

Next steps

Compare the plan limits on pricing, then read how the grounding check behaves in preventing hallucinations in customer support. If per-resolution billing is the reason you are shopping, deflection vs resolution pricing walks through the maths, and top Intercom alternatives lists other options with verified prices.