YES

As of 13 August 2026, AI can build an FAQ chatbot for your business website.

This still needs a person who signs their name to it.

Can you do it?

15 minutesto a draft.

1 hourto something you’d act on.

Cost, all in£0/month

Skill neededpower-user

Who has to check ityou

What the alternative costsThe alternative is a purpose-built product such as CustomGPT, which creates a no-code chatbot from your business content with citations.

If this goes wrong: the bot gives a confident but outdated answer, and a customer acts on it before your team notices.

What to actually do

  1. Hand it to a person

    The route this page recommends

    A person who owns the outcome does this end to end, worth it when the failure is dear.

  2. Use a tool built for this

    Second choice

  3. Do it yourself

    The distant third

    A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

    How to actually do it

    1. Open your current website, FAQ, help-centre articles, delivery terms, returns policy, opening hours, contact details and escalation procedure, then copy the current versions into one document.
    2. Remove obsolete offers, old prices, internal notes and personal customer information from that document before giving it to an AI tool.
    3. Paste the document and the business details into the prompt, including the exact human contact route for complaints, refunds and questions the bot cannot answer.
    4. Ask the AI tool to produce the welcome message, answer set, fallback wording, escalation wording and suggested buttons in separate sections.
    5. Create an account with a purpose-built chatbot tool such as CustomGPT, upload the approved document, and configure the bot to use that content rather than general web answers.
    6. Embed the generated chatbot on a private test page of your website and ask it every question in your existing FAQ, including questions with missing information and deliberately unclear wording.
    7. Compare each reply against the current source document, correct unsupported or outdated answers, test the human hand-off route, and only then publish the chatbot on the customer-facing site.
    8. Set a recurring task to update the source document and retest the bot whenever your prices, policies, products, opening hours or contact routes change.

    Prompt

    Build the content and conversation plan for an FAQ chatbot for this UK business website.

Business: [business name]
Website: [website URL]
Main customer questions: [list]
Current FAQ, help articles and policies:
[paste the complete text here]

Create:
1. A short welcome message.
2. The FAQ questions the bot should answer, grouped by topic.
3. Clear answers using only the supplied content. Do not invent prices, availability, delivery times, legal rights, guarantees or business policies.
4. A fallback reply for questions the content does not answer.
5. An escalation reply that sends complaints, refunds, account problems, safeguarding concerns, requests for personal data, and anything uncertain to a named human contact or support route.
6. Suggested buttons for the most common questions.
7. A list of claims and answers that need checking before publication.

Use plain British English. Keep answers concise. Say when information is missing or may be out of date. Do not ask customers for passwords, payment card details or unnecessary personal information. Format the result so it can be copied into a no-code website chatbot builder.

    Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

What it gets wrong

Even on a YES, the friction has a name: verification cost, legal accountability and context depth.

How we scored this

Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.

AxisScore (0–2)
Output2
Inputs2
Verification1
Liability1
Effort delta2
Total8 / 10

The methodology and its thresholds are published in full.

FAQ

Can AI build a chatbot for my website?
Yes. Current no-code AI tools can use your website and help documents to create an FAQ chatbot and provide code or an embed for your site. You still need to supply accurate content, test the replies and define when a person takes over.
What do I need to give an AI chatbot?
Give it your current FAQ, product information, delivery and returns policies, opening hours, contact routes and escalation rules. Remove personal customer data and tell it not to invent an answer when the source documents are silent.
Can an AI FAQ chatbot answer every customer question?
No. It can handle questions covered by your source content, but it can fail on unusual wording, exceptions, complaints and information that has changed. Configure a clear fallback and send uncertain or sensitive conversations to a human.
How do I stop my website chatbot giving wrong answers?
Use approved source documents, restrict the bot to those documents, and test every important FAQ against the current version before publishing. Retest it after changes to prices, policies, products, opening hours or contact details.

Nearby answers

All Help docs & FAQs rulings

Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.

The newsletter

AI news, new answers and product picks, straight to your inbox.