{"id":59,"date":"2026-08-22T20:27:38","date_gmt":"2026-08-22T20:27:38","guid":{"rendered":"https:\/\/intellowork.com\/blog\/ai-chatbot-for-website\/"},"modified":"2026-08-31T05:36:22","modified_gmt":"2026-08-31T05:36:22","slug":"ai-chatbot-for-website","status":"publish","type":"post","link":"https:\/\/intellowork.com\/blog\/ai-chatbot-for-website\/","title":{"rendered":"AI Chatbot for Your Website: The Complete 2026 Guide"},"content":{"rendered":"\n\n

An AI chatbot for your website<\/strong> should answer questions from your actual content – documentation, pricing pages, policies, help centre – with a citation and an honest refusal when the answer is not there. That is a different product from the pop-up widget that asks for your email and offers three canned buttons. The distinction is not cosmetic: one reduces the work your team does, and the other adds a step in front of a contact form.<\/p>\n\n\n\n

This guide covers what a website assistant should do, the mistake that limits most deployments, how setup actually goes, and what to measure.<\/p>\n\n\n\n

What a website chatbot should actually do<\/h2>\n\n\n\n

Four jobs, in descending order of how often they justify the project.<\/p>\n\n\n\n

Answer product and policy questions accurately.<\/strong> Shipping timelines, integration support, pricing tiers, refund terms, technical requirements. These are the questions that decide whether a visitor buys, and they are already answered somewhere on your site in a place nobody can find.<\/p>\n\n\n\n

Qualify without interrogating.<\/strong> A visitor asking about SSO and data residency has told you something about themselves. Capture that signal from the conversation rather than putting a five-field form in front of the answer.<\/p>\n\n\n\n

Hand over cleanly.<\/strong> When the question needs a human, the human should receive the full conversation, the pages the visitor read and what was already answered. A handover that starts with “how can I help you today?” wastes the whole interaction.<\/p>\n\n\n\n

Tell you what your site is missing.<\/strong> Every question your content cannot answer is a content gap, ranked by frequency. This is the most undervalued output of a website assistant and the one that compounds over years.<\/p>\n\n\n\n

The mistake: treating the website bot as an island<\/h2>\n\n\n\n

Most website chatbots are configured with their own separate content, their own separate answers and their own separate admin screen. Then the same organisation deploys a WhatsApp bot with different content, and a support assistant with a third set, and within a year the three give three different answers to the same question about refunds.<\/p>\n\n\n\n

The correct architecture is one retrieval layer with per-channel behaviour on top: the same indexed content and the same grounding rules, with tone, length and available actions varying by surface. The website assistant can be chattier and link out; the WhatsApp assistant must be terse; the internal one can see more content. One brain, several faces – the pattern described in one chatbot, every channel<\/a>.<\/p>\n\n\n\n

Setup, realistically<\/h2>\n\n\n\n
\n
Stage<\/th>What happens<\/th>Typical effort<\/th><\/tr><\/thead>
Content ingestion<\/td>Crawl the site, plus docs, help centre and PDFs<\/td>Hours to a day<\/td><\/tr>\n
Content triage<\/td>Exclude outdated pages, old blog posts, staging URLs<\/td>The part people skip, and should not<\/td><\/tr>\n
Grounding and refusal setup<\/td>Define what it answers and how it declines<\/td>Half a day, high leverage<\/td><\/tr>\n
Evaluation<\/td>30 to 50 real questions with correct answers<\/td>A day, and it pays for itself<\/td><\/tr>\n
Handover wiring<\/td>Route to email, chat or CRM with full context<\/td>Half a day<\/td><\/tr>\n
Placement and launch<\/td>Where it appears, and on which pages<\/td>An afternoon<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

Content triage is where quality is won or lost. A three-year-old blog post describing a pricing model you abandoned will be retrieved and quoted confidently. Crawling everything is easy; deciding what should be authoritative is the actual work.<\/p>\n\n\n\n

Placement matters more than design<\/h2>\n\n\n\n

A bubble in the bottom-right corner of every page is the default and the weakest option. Higher-intent placements consistently outperform it: alongside pricing tables, at the point where a documentation page ends, and – the strongest of all – inside the contact form, offering a cited answer before the visitor submits. That is the moment of maximum intent, and it is where deflection actually happens.<\/p>\n\n\n\n

Two accessibility points that are routinely missed: the assistant must be keyboard navigable and screen-reader friendly, and it must not trap focus. And if you operate in the EU, note that transparency obligations under Article 50 of the EU AI Act have applied since 2 August 2026 – people must be told they are interacting with an AI system where that is not obvious. A visible label is cheap; forgetting it is not. More on that in our compliance checklist<\/a>.<\/p>\n\n\n\n

Choosing the platform<\/h2>\n\n\n\n

Five questions separate a real answer engine from a form with a chat skin:<\/p>\n\n\n\n

    \n
  1. What happens when the answer is genuinely not in my content? You want a refusal and a route to a human, not a plausible paragraph.<\/li>\n
  2. Does it cite the page it used, and deep-link to the section?<\/li>\n
  3. How is content refreshed when I publish or change a page?<\/li>\n
  4. Can the same content serve WhatsApp, Slack or an internal assistant later, or is this index single-purpose?<\/li>\n
  5. Where does inference run, and is my visitors’ conversation data used for training?<\/li>\n<\/ol>\n\n\n\n

    Category context for that decision is in enterprise AI chatbot platforms<\/a>, and cost models in enterprise chatbot pricing<\/a>.<\/p>\n\n\n\n

    What to measure<\/h2>\n\n\n\n
    \n
    Metric<\/th>Why it matters<\/th><\/tr><\/thead>
    Answer rate<\/td>Share of questions answered from content rather than deflected to a form<\/td><\/tr>\n
    Citation rate<\/td>Uncited answers are where errors hide<\/td><\/tr>\n
    Honest refusal rate<\/td>Near zero means it is guessing<\/td><\/tr>\n
    Handover quality<\/td>Does the human receive context, or start cold<\/td><\/tr>\n
    Assisted conversion<\/td>Sessions with a chat interaction that convert<\/td><\/tr>\n
    Content gap list<\/td>Questions your site cannot answer, ranked by frequency<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

    Work the gap list weekly. It is a content roadmap generated by real visitor demand, which is a better prioritisation signal than any keyword tool.<\/p>\n\n\n\n

    Frequently asked questions<\/h2>\n\n\n\n

    How do I add an AI chatbot to my website?<\/h3>\n\n\n

    Ingest your site, documentation and help centre; triage out stale or superseded pages; configure grounding and refusal behaviour; build a 30 to 50 question evaluation set with correct answers; wire handover so a human receives full context; then place it where intent is highest, including inside the contact form. Most of the work is content triage and evaluation, not installation.<\/p>\n\n\n\n

    Will an AI chatbot give wrong answers about my product?<\/h3>\n\n\n

    It will if it is retrieving stale pages or has no refusal path. Exclude superseded content from the index, require citations on every factual claim, and test explicitly with questions your content cannot answer to confirm it declines rather than improvises.<\/p>\n\n\n\n

    Where should the chatbot appear on the site?<\/h3>\n\n\n

    Higher-intent placements outperform a universal corner bubble: next to pricing tables, at the end of documentation pages, and inside the contact form where it can answer before submission. Keep it keyboard navigable and screen-reader accessible wherever it appears.<\/p>\n\n\n\n

    Do I have to tell visitors they are talking to an AI?<\/h3>\n\n\n

    In the EU, yes. Article 50 transparency obligations under the AI Act have applied since 2 August 2026 and require people to be informed they are interacting with an AI system unless it is obvious from context. Regardless of jurisdiction, a visible label is good practice and costs nothing.<\/p>\n\n\n\n

    Can the same chatbot work on WhatsApp and Slack too?<\/h3>\n\n\n

    It should. Use one retrieval layer and one set of grounding rules, with tone, length and available actions varying per channel. Separate indexes per channel is how organisations end up giving three different answers to the same question.<\/p>\n\n\n\n

    Next step<\/h2>\n\n\n\n

    Write down the 30 questions visitors actually ask you, with the correct answer and the page it lives on. Then test any platform, IntelloWork<\/a> included, on that set rather than on a demo. If you plan to extend to internal use later, read the chatbot integration guide<\/a> before you commit to an index.<\/p>\n\n\n\n