# LayBuild AI > LayBuild AI is a hosted AI customer support agent that answers from the documents, page URLs and Q&A pairs you give it, on a website chat widget, WhatsApp and a REST API. When it can't find an answer in your content it says so, and your team can take over the conversation in the LayBuild dashboard. Plans are flat monthly prices in INR (Starter ₹1,499, Pro ₹3,999, Premium ₹9,999) with no per-resolution fee. ## Facts for citation - **Name**: LayBuild AI (or LayBuild). Website: https://laybuild.com - **Category**: AI customer support agent with human handoff. It is not a ticketing helpdesk. - **Channels**: web chat widget, WhatsApp (Meta Cloud API, text messages only) and REST API. No email, Slack, SMS or voice channel. - **Grounding**: answers come from your uploaded files, listed URLs, manual Q&A pairs and pinned documents. If retrieval finds nothing relevant, or the answer fails a word-overlap check against the sources, the customer gets a fixed "I do not have specific information" reply. This reduces made-up answers; it does not eliminate them. - **Human handoff**: agents claim conversations in the dashboard. Handoff on customer request is on by default and an admin can switch it off in settings. A conversation is handed off after 25 AI replies either way. - **Pricing**: Starter ₹1,499/month (1,500 conversations, 5 seats), Pro ₹3,999/month (8,000 conversations, 15 seats), Premium ₹9,999/month (20,000 conversations, up to 100 seats). Annual billing is ₹1,199, ₹3,199 and ₹7,999 a month. No per-resolution fee and no free plan. - **Models**: choosing your own model and provider key (for example OpenAI, Anthropic, Gemini, DeepSeek, Azure OpenAI or any OpenAI-compatible endpoint) is on Premium only. - **Not offered**: SSO or SAML, ticketing, helpdesk sync (Zendesk, HubSpot, Salesforce), self-hosting, SOC 2, HIPAA, ISO 27001 or GDPR certification. ## Product pages - [Home](https://laybuild.com/): What LayBuild does, the channels, and how a conversation moves from the AI to your team. - [Features](https://laybuild.com/features): Answers from your documents, guardrails, human handoff and the agent dashboard. - [AI agents](https://laybuild.com/agents): Running separate AI agents for support, technical and sales questions, each with its own knowledge. - [Pricing](https://laybuild.com/pricing): The three plans, their limits, and monthly versus annual prices. - [Compare](https://laybuild.com/compare): What LayBuild does and the questions to ask Intercom, Zendesk, Freshdesk and Chatbase about pricing, accuracy, handoff, channels and data. - [WhatsApp AI chatbot](https://laybuild.com/whatsapp-ai-chatbot): Answering WhatsApp Business messages from your documents, with team takeover. Text only. - [Intercom alternative](https://laybuild.com/compare/intercom-alternative): When LayBuild fits as an Intercom alternative, and when it does not. - [Zendesk alternative](https://laybuild.com/compare/zendesk-alternative): Chat-first support without ticketing, or in front of Zendesk via webhooks. - [Freshdesk alternative](https://laybuild.com/compare/freshdesk-alternative): AI chat on website and WhatsApp versus an email-ticket helpdesk. - [Chatbase alternative](https://laybuild.com/compare/chatbase-alternative): A document chatbot plus a team inbox for human takeover. - [Tidio alternative](https://laybuild.com/compare/tidio-alternative): Answers from PDFs, spreadsheets and listed pages, with flat INR pricing. - [Knowledge prompts](https://laybuild.com/knowledge-prompts): Free copy-paste prompts for ChatGPT and Claude that interview you and write support, sales, booking and FAQ documents to upload to your agent. - [Blog](https://laybuild.com/blog): All 45 guides listed below. - [Contact](https://laybuild.com/contact): Questions about plans or fit. - [Full LLM reference](https://laybuild.com/llms-full.txt): A longer factual reference on how LayBuild works and what it does not do. ## Guides: how LayBuild works - [AI chatbot vs agentic AI](https://laybuild.com/blog/ai-chatbot-vs-agentic-ai): Scripted bots, retrieval-grounded LLMs and autonomous agents, and where LayBuild sits. - [Autonomous ticket resolution](https://laybuild.com/blog/autonomous-ai-ticket-resolution): How to measure resolution honestly and why deflection inflates published rates. - [How LayBuild remembers a conversation](https://laybuild.com/blog/context-retention-conversational-memory): Recent messages, long-term customer facts and past-conversation excerpts, and their trade-offs. - [API tools without function calling](https://laybuild.com/blog/dynamic-tool-calling-support-architecture): Why LayBuild's API tools run fixed HTTP calls instead of letting the model choose. - [Event-driven support architecture](https://laybuild.com/blog/event-driven-customer-support-architecture): Receiving support webhooks with queues, idempotency and your own retries. - [Routing across several agents](https://laybuild.com/blog/multi-agent-support-routing): When to split support into several AI agents and how LayBuild assigns a conversation to one. - [Adding the widget to a Next.js site](https://laybuild.com/blog/nextjs-chat-widget-server-components): How the widget script loads and how to add it in the App Router. - [One conversation model for every channel](https://laybuild.com/blog/omnichannel-ai-inbox-architecture): How web chat, WhatsApp and API conversations share one model, and where they differ. - [Regression-testing a support agent](https://laybuild.com/blog/unit-testing-ai-support-prompts): Contract tests with a stubbed model plus a golden question set against a real one. ## Guides: retrieval and grounding - [Fine-tuning or retrieval](https://laybuild.com/blog/finetuning-vs-rag-support): When fine-tuning helps support bots and why LayBuild uses retrieval instead. - [pgvector hybrid search](https://laybuild.com/blog/hybrid-search-vector-rag-pgvector): Vector and full-text search in PostgreSQL, merged with Reciprocal Rank Fusion, and the 0.4 relevance floor. - [Multilingual support](https://laybuild.com/blog/multilingual-ai-support-global-expansion): Why retrieval is English-first by default and what to change for other languages. - [Parent-child chunking](https://laybuild.com/blog/optimizing-chunk-size-rag-retrieval): LayBuild's chunk sizes, overlap and prompt limits, and how to write documents for them. - [How LayBuild limits made-up answers](https://laybuild.com/blog/preventing-hallucinations-customer-support): Strict knowledge-base mode, the overlap check and auto-learning, and what still gets through. - [Knowledge base writing for AI](https://laybuild.com/blog/saas-knowledge-base-optimization-for-ai): Structuring help content so retrieval finds the right passage. - [Sparse vs dense retrieval benchmarks](https://laybuild.com/blog/sparse-dense-embedding-benchmarks): How to benchmark BM25, vector and hybrid search on your own documents. ## Guides: running support - [Support for API and developer tool companies](https://laybuild.com/blog/ai-support-developer-tool-api-companies): Structuring docs, error codes and changelogs for retrieval, and the limits. - [Improving answers with evidence](https://laybuild.com/blog/continuous-prompt-optimization-support): A weekly review loop using fixed no-answer replies and low ratings. - [Preparing for a sale spike](https://laybuild.com/blog/ecommerce-flash-sale-support-automation): Pinned sale terms, Q&A pairs, plan limits, handoff staffing and a load test. - [Measuring CSAT for AI support](https://laybuild.com/blog/measuring-csat-in-ai-driven-channels): Collecting ratings, reading their bias, and pairing CSAT with escalation rate. - [Support team burnout](https://laybuild.com/blog/preventing-support-agent-burnout-with-ai): What an AI agent takes off the queue and what it makes harder. - [Keeping knowledge current](https://laybuild.com/blog/realtime-knowledge-sync-pipelines): A refresh routine and scripting updates against the LayBuild API, without connectors. - [Human handoff protocols](https://laybuild.com/blog/safe-human-handoff-escalation-protocols): Handoff triggers, the 25-turn limit, webhooks and agent takeover. - [Support from 1,000 to 100,000 users](https://laybuild.com/blog/scaling-support-from-1k-to-100k-users): How question volume and mix change, what to automate first, and sizing a plan. - [Getting more questions answered correctly](https://laybuild.com/blog/the-70-percent-autonomous-resolution-playbook): Find the misses, diagnose them, fix content, measure again. - [Voice vs text support agents](https://laybuild.com/blog/voice-ai-vs-text-ai-support): Latency, speech errors and cost for voice agents, and why LayBuild is text-only. ## Guides: costs and buying - [AI support software for startups](https://laybuild.com/blog/best-ai-customer-support-software-startups): Questions to ask and the products whose pricing pages we read. - [A CFO business case for support automation](https://laybuild.com/blog/building-cfo-business-case-support-automation): Baselines, a pilot that can fail, formulas and a sensitivity table. - [Crisp vs LayBuild](https://laybuild.com/blog/crisp-chat-vs-laybuild-ai): A live chat suite with AI credits versus a flat-priced grounded AI agent. - [Forethought vs LayBuild](https://laybuild.com/blog/forethought-vs-laybuild-ai): An AI layer for large helpdesks versus a standalone agent with published prices. - [Helpdesk contract costs](https://laybuild.com/blog/hidden-costs-of-legacy-helpdesks): Cost lines a headline seat price leaves out. - [Calculating AI support ROI](https://laybuild.com/blog/how-to-calculate-ai-customer-support-roi): A worked model with break-even on volume and on answer quality. - [LayBuild vs Intercom Fin](https://laybuild.com/blog/laybuild-vs-intercom): Per-outcome pricing versus flat plans, and what each product covers. - [LayBuild vs Zendesk AI](https://laybuild.com/blog/laybuild-vs-zendesk-ai): A full helpdesk versus a front-line AI agent, and using both together. - [Using LayBuild alongside Zendesk](https://laybuild.com/blog/migrating-from-zendesk-to-laybuild): Export help articles, upload them, and send handoffs to Zendesk. - [tawk.to vs LayBuild](https://laybuild.com/blog/tawkto-vs-laybuild-ai): Free live chat with paid add-ons versus a paid document-grounded agent. - [Intercom alternatives in 2026](https://laybuild.com/blog/top-intercom-alternatives-2026): Seat prices and AI resolution fees across Intercom alternatives. - [Deflection vs resolution](https://laybuild.com/blog/true-cost-deflection-vs-resolution): The difference, how to calculate resolution rate, and billing traps. ## Guides: security and deployment - [Fintech and payments support](https://laybuild.com/blog/automated-support-fintech-payments): Dispute workflows, keeping card data out of chat, and escalation. - [Custom webhooks and HMAC verification](https://laybuild.com/blog/custom-webhooks-support-automation): LayBuild's webhook headers and payload, signature checks and replay protection. - [PHI and LayBuild](https://laybuild.com/blog/healthcare-medtech-customer-support-compliance): LayBuild is not HIPAA compliant and signs no BAA; safe patterns for healthcare support. - [Multi-tenant data isolation](https://laybuild.com/blog/multitenant-saas-support-isolation): Tenant scoping in PostgreSQL and pgvector, and deployment trade-offs. - [What PII redaction catches](https://laybuild.com/blog/pii-redaction-llm-support): Regex redaction of cards, US SSNs, emails and phone numbers in AI answers, and what it misses. - [PostgreSQL and Supabase data for support agents](https://laybuild.com/blog/postgresql-supabase-ai-support-agent): Read-only API tools in place of model-written SQL. - [Roles and audit logs](https://laybuild.com/blog/rbac-ai-support-tools): LayBuild's four fixed roles, the audit log, two-factor login, and what is missing. ## Legal - [Privacy policy](https://laybuild.com/privacy) - [Terms of service](https://laybuild.com/terms) - [Refund policy](https://laybuild.com/refund-policy) - [Cookie policy](https://laybuild.com/cookie-policy)