Adding an AI chat assistant to your website: options and risks
The main ways to add an AI chat assistant to a business website, what each involves, and the risks to plan for before it starts talking to customers.
An AI chat assistant on your website can answer common questions at any hour, help visitors find the right page, and collect enquiries while you sleep. It can also give a customer a wrong answer with total confidence, under your company's name. Both are real, and the difference comes down to how you set it up.
This guide covers the main options and the risks to plan for. For how to run AI-assisted support more broadly, including when to hand off to a person, see AI for customer support.
First, decide what it's for
Write down the job in one sentence before you look at products. Good examples:
- "Answer questions about opening hours, services, and booking, and pass everything else to our team."
- "Help shoppers find products and answer shipping and returns questions from our policy pages."
- "Collect project enquiries outside business hours and book a discovery call."
A narrow job is easier to set up, test, and trust. "Answer anything about our business" is where problems start.
The three main options
1. AI features in a help desk or chat tool
Many customer support and live chat platforms now include an AI assistant that answers from your help articles and hands off to your team inside the same tool. If you already use one for email support or live chat, this is often the quickest route.
Good for: businesses with existing support content and a team that answers chats. Watch for: pricing models that charge per AI answer or resolution, which can be hard to predict. Check the current plans.
2. Website platform add-ons
Website builders and e-commerce platforms such as Shopify, Wix, Squarespace, and WordPress have AI chat apps and plugins, some from the platform itself and many from third parties. They can often read your existing pages and product catalog.
Good for: small sites and stores that want something running quickly. Watch for: the quality and privacy terms of third-party apps vary widely. Apply the questions in how to evaluate an AI tool. For WordPress, treat a chat plugin like any other plugin that touches visitor data: keep it updated and remove it if it's abandoned.
3. A custom assistant
A developer builds an assistant using an AI provider's API, connected to your content and, sometimes, your systems (booking, order lookup, CRM). This gives you the most control over what it knows, how it answers, and where data goes.
Good for: businesses with specific workflows, higher volumes, or stricter data requirements. Watch for: ongoing usage costs, maintenance, and the extra security work involved in connecting it to live systems. This is the kind of build Chykalophia does, and it's worth getting right rather than fast.
The options side by side
Help desk or chat tool
Good for
Businesses with existing support content and a team that answers chats.
Watch for
Per-answer or per-resolution pricing that can be hard to predict.
Platform add-on
Good for
Small sites and stores that want something running quickly.
Watch for
Third-party apps vary widely in quality and privacy terms.
Custom assistant
Good for
Specific workflows, higher volumes or stricter data requirements.
Watch for
Ongoing usage costs, maintenance and extra security work.
The risks to plan for
Wrong answers
AI assistants can invent answers, including prices, policies, and promises you don't offer. Courts and tribunals may hold a business responsible for what its chatbot says. In a widely reported 2024 case, a Canadian tribunal held Air Canada responsible for inaccurate refund information its website chatbot gave a customer.
How to reduce it:
- Restrict the assistant to answering from your own approved content
- Tell it to say "I don't know" and offer a person when the answer isn't in that content
- Keep policy pages current, because the assistant will repeat whatever they say
- Exclude topics where a wrong answer is costly (pricing exceptions, legal, medical, financial advice)
Manipulation (prompt injection)
Visitors can try to trick an assistant into ignoring its instructions, revealing its setup, or saying something embarrassing. If the assistant can take actions (look up orders, issue discounts, send emails), the stakes rise. The OWASP Top 10 for large language model applications lists prompt injection as a leading risk.
How to reduce it: give the assistant the fewest permissions it needs, require confirmation for any action, never put secrets in its instructions, and test it with deliberately awkward questions.
Privacy
Visitors type all sorts of things into chat boxes, including personal and sensitive details. You need to know where those conversations go, how long they're kept, and whether the provider uses them to train AI models.
- Update your privacy notice to describe the chat and the provider
- Check the provider's data terms and sign a data processing agreement if you're subject to GDPR or similar laws
- Discourage sensitive information in the chat, and don't use a general chat assistant for health or payment details. See HIPAA basics for websites handling health info if you're in healthcare.
AI and your customer data covers this in more depth.
Being clear it's an AI
Visitors should know they're talking to an AI. It's honest, it sets expectations, and some laws require it in certain situations. For example, the EU AI Act includes transparency rules requiring people to be told when they're interacting with an AI system. Label it clearly ("AI assistant") and avoid giving it a human name and photo that suggest otherwise.
Accessibility
A chat widget must work with a keyboard and screen readers, have enough color contrast, and not cover important content on small screens. Test it with the same care as the rest of your site. See ADA & WCAG: web accessibility compliance.
Cost and abuse
Usage-based AI pricing means a spike in traffic, or someone deliberately spamming your chat, can raise your bill. Set usage limits and alerts where the tool allows.
Before you launch
0 of 6 done
- Write the job description and the off-limits list.
- Clean up the content it will learn from. Remove outdated pages, conflicting policies, and old prices.
- Set the handoff. Decide when it passes to a person, how, and who answers. Make "talk to a person" easy to find.
- Test with 50 or more real questions, including tricky, rude, off-topic, and manipulative ones. Record the wrong answers and fix the content or settings.
- Update your privacy notice and label the assistant as AI.
- Launch quietly, then review conversation logs weekly for the first month.
Saved in this browser only.
Frequently asked questions
Will a chatbot reduce my support workload?
It can reduce repetitive questions if your content is good and the scope is narrow. It also adds work: reviewing logs, updating content, and handling handoffs. Measure both.
Can it book appointments or look up orders?
Yes, many tools can connect to booking and e-commerce systems. Each connection adds risk, so start with answering questions and add actions once you trust it.
Should we remove our contact form?
No. Some visitors prefer forms or email, and some questions need a person. Keep other ways to reach you.
Related guides
Learn more
Go deeper on chykalophia.com
Talk it through
Want a second pair of eyes on this?
Book a free discovery call, up to an hour. Bring the question you're stuck on and we'll tell you honestly what we'd do.
Already a client? Email support@chykalophia.com.
Last updated
AI and your customer data: privacy basics
What happens to customer information you put into AI tools, how to choose settings and plans that protect it, and simple rules your team can follow.
Automating repetitive admin with AI and Zapier or Make
How to combine automation tools like Zapier or Make with AI steps to take repetitive admin off your team's plate, with examples, a build process, and the safeguards to add.