Planning · 8 min read

How to plan a chatbot for your business

Most chatbots that disappoint were never planned: they were switched on. This guide walks through the eight decisions that make a bot useful, in the order the free designer asks them.

Updated 15 November 2026 · Sources at the end

In short

  • Start from the job, not the technology: what should the bot take off your team’s plate?
  • Launch with three to five jobs and the 15 to 30 questions customers ask most.
  • Decide when a person takes over before you write a single answer.
  • Set a goal with a number and a date, and test with real questions before launch.

1. Start with the job, not the technology

The first question is not “which platform?” but “what should this bot do that a person does now?” Answering repeat questions, taking bookings, qualifying leads and helping new customers get started are the common answers. Pick one main job and write down what success looks like.

Businesses are moving quickly. Among UK businesses already using AI, 44% use it in customer service (opens in a new tab). But the barrier most of them name is skills: 67% of businesses using AI cite limited skills or expertise (opens in a new tab). A plan is how you make up for that: it turns a vague wish into decisions anyone can check.

Write it as a sentence

“Answer 40% of support chats without a person within three months, with first replies under a minute.” A number and a date make it testable.

2. Choose three to five jobs for launch

List every job the bot could do, then mark each one “at launch”, “later” or “not now”. Three to five jobs at launch is plenty. Each job needs its own answers, its own testing and sometimes its own connection to another system, so a long list slows everything down.

  • Good first jobs: questions with one right answer, asked often, that need no judgement
  • Later jobs: things that need a connection to another system, such as order look-ups or bookings
  • Not for a bot: complaints, refunds outside policy, anything sensitive or emotional

3. Write the answers before choosing a platform

The answers are the bot. Collect the questions customers actually ask, from your inbox, phone notes and reviews, and write one short answer to each. In Gartner’s global research, customers could not find relevant content in 43% of failed self-service attempts (opens in a new tab); a bot without the right answers fails the same way.

Writing the answers first also tells you what kind of bot you need. Twenty fixed answers suit a scripted bot; hundreds of help articles suit AI that answers from your content. The guide on writing your bot’s answers goes into detail.

4. Give it a voice, and say it is a bot

Decide the bot’s name, tone and first message. The first message should say it is an automated assistant and what it can help with. Then list the words and topics it should avoid. A short, friendly, plain-English voice works for most businesses.

5. Decide when a person takes over

This is the decision that most affects how customers feel about your bot. In a 2026 survey for Citizens Advice, 40% of people who tried to reach a human after meeting a chatbot found it difficult or impossible (opens in a new tab). Decide the triggers (asking for a person, a complaint, a payment problem, repeated confusion), the route (call back, live chat, email) and the hours, and what the bot says out of hours.

Read more in handing over to a person.

6. Pick the channels and how it answers

Where are your customers already asking? A website chat, WhatsApp, Instagram, email or inside your app. Start with one or two. Then choose how the bot answers: scripted, AI from your content, or a mix. The guide on AI or scripted bots compares them.

7. Set the numbers you will watch

Choose three or four measures before launch: how many problems the bot solves, how many conversations it hands over, what customers say when asked, and the questions it misses. Note where you are today, so you can tell whether it worked. See measuring a chatbot.

8. Test with real questions, then launch small

Before launch, try the bot with 30 or so real questions, worded the way customers word them, and agree a pass mark. Fix the misses by improving the answers, not by adding tricks. Then launch on one channel, read the conversations every week for the first month, and add jobs from what you learn.

The free bot designer does all eight steps in your browser, with a test chat that runs your plan and a readiness check before you export it.

Questions people ask

How long does it take to plan a chatbot?

An afternoon for a simple bot, if you have your common questions to hand. Writing good answers takes longest; the rest is a series of short decisions.

Do I need technical knowledge?

No. Planning is about your customers and your business. The technical choices follow from the plan, and a builder can make them with you.

What if my business is too small for a chatbot?

If the same questions take up hours each week, a simple bot can help even a small business. If they do not, a good FAQ page may be enough. The automation finder helps you check.

Design your bot in an afternoon

Free, no sign-up. Pick its jobs, write its answers, set the handoff, then test it in your browser and export the plan.