AI & Automation2 min read

Most website chatbots frustrate more than they help. How to choose its job, give it the right knowledge, set limits and hand over to a person at the right moment.

Crest Design team
AI chatbot for websites guide cover

A chatbot can be the most useful thing on your website or the most annoying. The difference is rarely the AI model. It is what the assistant knows, what it is allowed to do, and what happens when it can't help. Here is how we plan AI chat assistants that customers actually use.

Decide the one job it does first

The most common mistake is launching a bot that tries to do everything. Pick the job that costs your team the most time today:

  • Answering the same questions: pricing, delivery times, returns, opening hours.
  • Qualifying leads: asking two or three questions and booking a call with the right person.
  • Helping people choose: recommending a product, plan or service based on what they need.
  • Order support: tracking, changes and returns for an online store.

Get one job working well, then add the next. A narrow assistant that answers correctly beats a broad one that guesses.

Give it the right knowledge

Modern assistants answer from your own content rather than from general knowledge. That content needs to be good:

  1. 1Collect the sources: service pages, FAQs, policies, product data and help articles.
  2. 2Fix the gaps: if a question comes up often and your website doesn't answer it, write the answer first. Your visitors benefit even without the bot.
  3. 3Keep it current: connect the assistant to the pages themselves, so updating the website updates the bot.
A chatbot is only as good as the website it learns from.

Set clear limits

Tell the assistant what it must never do: promise discounts, give legal or medical advice, or invent an answer when it isn't sure. Write its tone of voice the way you would brief a new team member, so it sounds like your brand rather than a generic robot.

Plan the hand-off to a human

Every good assistant knows when to step aside. When a visitor asks for a person, gets frustrated or has a question the bot can't answer, it should:

  • Collect their name, email and question.
  • Create a contact or ticket in your CRM, with the conversation attached.
  • Notify the right person straight away, by email, Slack or WhatsApp.

This is where chat becomes automation: the conversation lands in the same system your team already works in. If that system is HubSpot, our HubSpot CMS guide explains how the website, forms and CRM fit together.

Measure what matters

Skip vanity numbers like total chats. Track the questions answered without a person, the leads captured, the calls booked, and the questions the bot couldn't answer. That last list is gold: it tells you exactly what to add to your website next.

What it looks like in practice

For Insight Monster, a marketing platform, we built an AI chatbot that answers visitors and captures leads, feeding them into the platform's own CRM. The same approach works on a services site, a SaaS product or a Shopify store.

Thinking about an assistant for your site? Tell us the job you want it to do, or read our list of automations to set up first.

(over to you)

Planning a build like this?

Tell us what you're building and we'll come back with ideas and next steps.