Chatbot Conversation Storyboards: Write Your Top Question’s Chat Five Ways Before You Build Anything (Free Storyboard Builder)

Chatbot conversation planning usually stops at one tidy exchange: the visitor asks, the bot answers, done. Real chats wander. People open with “hi”, ask for things you don’t sell, or want a person at 11 pm. This guide shows how to storyboard your most-asked question five ways, on paper, in about twenty minutes, so the bot already knows what to say on each path before you set anything up. A free builder writes the five paths from your own details.

👤 What the visitor seesPath 2 · vague opener
hi
🤖 AI AgentHi! I can help with delivery, prices, plant care and orders. What would you like to know?
do you deliver to pune
🤖 AI AgentYes, we deliver to Pune in 2 to 4 days. Delivery is free on orders over ₹799.

Illustrative shop. The bot offers choices instead of a bare “How can I help?”

⚡ In short

  • Pick your single most-asked question. Storyboard it before you build any bot.
  • Write five paths: smooth, vague opener, something you don’t offer, a person during hours, a person after hours.
  • Read every path aloud. Fix any line that sounds like a form or leaves the visitor wondering what to type.
  • Only then load the answers, welcome text and opening hours into your chat tool.
Chatbot conversation in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Why storyboard

One answer is not a conversation

Most people set up a bot by writing answers. That’s a good start, but an answer is only one message. What the visitor experiences is the whole exchange: how the chat opens, what happens when they’re vague, what the bot says when it can’t help, and how the chat ends.

Film makers solve the same problem with storyboards. Before they shoot, they sketch every scene so they can spot gaps while changes are still cheap. You can do the same for a chat. A storyboard is just the full chat written out as lines, “Visitor:” and “Bot:”, for each likely path.

Why bother, when you could just switch the bot on and watch? Three reasons:

  • Gaps show up on paper. When you write path 3, you’ll notice you have no polite way to say “we don’t do that”. It’s far better to find that now than in a live chat with an annoyed visitor.
  • Tone becomes consistent. Writing all five paths in one sitting keeps the voice the same from greeting to goodbye.
  • Setup gets faster. Each line in the storyboard maps to a setting: the welcome message, an answer in the knowledge, a saved reply, the away message. You fill them in instead of inventing them in the settings screen.

Start with one question, the one customers ask most. If you don’t know which it is, our guide on how to build a chatbot from the questions you already get shows how to find it in an hour. One well-storyboarded question teaches you the pattern for all the others.

The five paths

Every question can travel five ways

Write each path for the same top question. Together they cover most of what really happens in a small business chat.

✅

1. Smooth path

The visitor asks clearly. The bot answers, offers a next step and closes politely.

👋

2. Vague opener

The visitor types “hi” or one word. The bot offers a few choices and gets to the answer in one turn.

🚫

3. Something you don’t offer

The visitor asks for something outside your business. The bot says no plainly and offers the nearest yes.

🙋

4. A person, team online

The visitor asks for a human during your hours. The bot passes the chat on and sets a time expectation.

🌙

5. A person, after hours

The same request when nobody is online. The bot collects a contact and says when the team will reply.

Path 1

The smooth path: answer, offer, close

Start with the happy case, because the other four paths borrow from it. Write it in four or five lines:

  1. Visitor: the question, in the customer’s own words. Not “What are your delivery options?” but “do you deliver to pune”. Copy it from a real WhatsApp message if you can.
  2. Bot: the answer, key fact first. If it’s a yes/no question, start with “Yes” or “No”. Add the one detail people usually ask next, like the price or the time.
  3. Bot: a next step, phrased as a question. “Would you like the link to our indoor plants?” A chat that ends on a bare fact leaves the visitor to work out what to do.
  4. Visitor: a likely reply, such as “no thanks” or “yes”.
  5. Bot: a short close with your business name.

Two things to watch. First, length: a reply longer than about 220 characters becomes more than one bubble on a phone screen, so split it or cut it. Our guide to chatbot answers that fit a phone screen has the details. Second, don’t stack questions. “Would you like the link, or shall I tell you about our offers, or do you need anything else?” is three questions in one; the visitor answers none of them.

When the smooth path reads well aloud, you have the core of every other path. In a good chatbot conversation, the answer and the next step stay the same whichever path the visitor takes to reach them.

Path 2

The vague opener: offer choices, don’t interrogate

A large share of chats start with “hi”, “hello”, “price?” or a single product name. If your bot replies “How can I help you today?”, the visitor has to do all the work, and many simply leave.

Storyboard this path with a better second line. Instead of an open question, name what the bot can help with: “Hi! I can help with delivery, prices, plant care and orders. What would you like to know?” That one line does three jobs. It shows the bot is useful, it hints at the words to use, and it tells the visitor what’s out of scope without saying so.

Keep the list to three or four topics. A list of ten reads like a menu at a train station. Pick the topics from your own most-asked questions, in the order customers ask them.

Then write the rest of the path: the visitor asks the top question, and the bot gives exactly the same answer and next step as in path 1. Consistency matters here. If the answer changes depending on how the chat started, visitors and your team both lose trust in it.

One-word messages like “price?” need their own care, because the bot has to ask which product. Our guide to clarifying questions for one-word messages covers that case in depth. For the storyboard, just make sure your opener path gets to a real answer in no more than two bot turns.

In LiveChatBot, the second line of this path is a good starting point for your welcome message, which you can set in the widget settings and have translated automatically for visitors who use other languages.

Path 3

Something you don’t offer: say no, then offer the nearest yes

Every business has things it doesn’t do. A plant shop doesn’t repot plants at your home. A tutor doesn’t take Class 12 physics. A bakery doesn’t deliver outside the city. Visitors will ask anyway, and this is the path where bots most often go wrong: they guess, they waffle, or they answer a different question.

Storyboard a plain, kind no:

  • Visitor: “do you repot plants at home?”
  • Bot: “Sorry, we don’t repot plants at your home. We can email you our free step-by-step repotting guide. Would that help?”

The pattern is: say no in the first sentence, using the visitor’s words; offer the nearest thing you *can* do; end with a question. The nearest yes might be a guide, a related product, a different service, or simply “our team can suggest someone local”.

Avoid three common mistakes. Don’t apologise at length; one “sorry” is enough. Don’t pretend: “We may be able to help with that!” when you can’t wastes everyone’s time. And don’t leave the no hanging with nothing after it, because that’s where visitors close the tab.

If you use an AI bot, put your “we don’t” list in its knowledge too. A line like “We do not offer home visits or repotting at the customer’s address” stops the AI from filling the gap with a hopeful guess. Our AI chatbot design guide shows how to write instructions like this.

Writing this path is also a useful business check. If many visitors ask for something you don’t offer, that’s a signal worth noting, maybe even a new service.

Paths 4 and 5

A person, now or later

The last two paths start the same way: the visitor types “can I talk to a real person”. What happens next depends on the clock, so write both.

Path 4: the team is online

The bot should agree straight away and set an expectation: “Sure. I’m passing this chat to our team now; someone will join in a minute or two. What would you like to ask them?” Asking for the question while they wait means your team joins with context instead of starting with “Hi, how can I help?”

Then make sure the promise is real. If your team usually takes five minutes, say five. A promise of “a minute or two” that turns into fifteen does more damage than an honest estimate. Our handover guide covers the wording and timing in detail.

Path 5: nobody is online

This is the path most bots get wrong, because they say “connecting you now” and nobody ever comes. Write it honestly: “Our team is online 10 am to 7 pm, Monday to Saturday, and is away right now. Leave your email or phone number and your question, and they will reply when they are back.”

Then close the loop: “Got it, thank you. Someone will get back to you during working hours.”

In LiveChatBot this path is handled by opening hours and the away form, which collects an email or phone number when nobody is online; offline messages can become tickets so none get lost. See setting live chat opening hours for the steps.

Together, these two paths turn “I want a human” from a dead end into a smooth part of the chatbot conversation, whatever time it is.

Free tool

Build your storyboard in two minutes

Enter your top question, your answer and a few details. The builder writes all five paths, flags weak spots like a missing next step or an answer too long for a phone, and gives you the full script to copy.

Fill in your business details. The tool writes one question’s chat five ways: the smooth path, a vague opener, something you don’t offer, a request for a person during hours, and the same request after hours.

Runs only in your browser; nothing is sent or saved.

Before and after

Lines that change once you storyboard

Vague opener
🚩 Before“Hello! How can I help you today?”
✅ After“Hi! I can help with delivery, prices, plant care and orders. What would you like to know?”
After the answer
🚩 BeforeThe chat ends on the delivery fact.
✅ After“Would you like the link to our bestselling indoor plants?”
Something you don't offer
🚩 Before“We may be able to help with that! Please contact us.”
✅ After“Sorry, we don't repot plants at your home. We can email you our free repotting guide. Would that help?”
A person, after hours
🚩 Before“Connecting you to an agent…” and then silence.
✅ After“Our team is online 10 am to 7 pm, Monday to Saturday. Leave your email or phone and they will reply when they are back.”

Test it

Read it aloud, then hand it to someone else

A storyboard on screen always looks fine. Read aloud, its problems jump out. Do this before you build anything.

Read every path aloud, in both voices. Say the visitor lines in a customer's voice and the bot lines in yours. Any line you stumble over is too long or too formal. Any line where you think "and then what?" is missing a next step.

Check the hand-offs between lines. After each bot message, ask: does the visitor know what to type next? If not, the message needs a question or a clear choice.

Give it to someone who doesn't know your business. A friend, a family member, a new staff member. Ask them to play the visitor and type their own replies, while you answer from the storyboard. Every time they say something you didn't plan for, write it down. That's your next path.

Time the after-hours path. Look at the promise in path 5 and check it against what your team really does. If replies the next morning usually happen by 11 am, say "by 11 am".

Keep the storyboard file. It doubles as a test script. After you set the bot up, run each path in your live chat and check that the replies match. Our guide to chatbot dialogue turn-taking has a free tool that counts the turns in a transcript, which is handy for checking that the live chat doesn't take longer than the plan.

If the storyboard survives all of this, it's ready to build.

Build from it

Where each line of the storyboard goes

A finished storyboard maps almost line by line onto settings in your chat tool. In LiveChatBot, this is where each piece goes:

  • The vague-opener line becomes your welcome message. See writing a live chat welcome message.
  • The answer from path 1 goes into the AI Agent's knowledge, so it can answer the question in any wording. Our guide to training your AI chatbot explains how.
  • The same answer and the "we don't" reply also go in as saved replies. When AI replies are unavailable or the monthly allowance is used up, the free keyword bot answers from saved replies, and your team can use them too. See using saved replies.
  • The after-hours lines become your opening hours and away form settings.
  • The next-step offer can become a link in the answer, or a widget card if it's something like a WhatsApp button.

If you want a proactive opener on a particular page, such as the delivery page, a Flow can send a message based on the page, the visitor's country or their number of visits. Our chat flow guide shows the steps.

Once your first question is live, storyboard the second most-asked one, then the third. Most small businesses find that five or six storyboards cover the bulk of their chats. Each chatbot conversation you plan this way takes less time than the last, because paths 3, 4 and 5 barely change from one question to the next.

Checklist

Your storyboard is ready when

Storyboard progress

Getting started

Storyboard your top question today

Take your most-asked question, open the builder above, and fill in your details. Read the five paths aloud, fix whatever the builder flags, and ask one other person to play the visitor. Then put the lines into your chat settings: the welcome message, the answer, saved replies, opening hours and the away form.

LiveChatBot's free plan includes the chat widget, an AI Agent with a small free monthly allowance, a free keyword bot that answers from saved replies, the team inbox, the Android app, Flows, opening hours with an away form, and tickets, for two websites with 100 visitors per website each month. See pricing and start free at livechatbot.in.

Frequently asked questions

What is a chatbot conversation storyboard?

It's the full chat written out line by line, Visitor and Bot, for each likely path a question can take. You write it before setting up the bot so gaps and awkward lines show up while they're easy to fix.

Why five paths and not just one?

Because real visitors don't all ask clearly. The five paths cover the usual cases: a clear question, a vague opener, a request you can't meet, and a request for a person during and after your hours.

How long should each path be?

Usually four or five messages. If a path needs more than about three bot turns to reach an answer, simplify it.

Do I need an AI bot to use this method?

No. The storyboard works for an AI bot, a keyword bot or a team replying by hand. The lines become your welcome message, answers, saved replies and away message.

Does the storyboard builder save what I type?

No. It runs entirely in your browser, and nothing is sent or saved.

Keep reading

Related guides

📘

Chatbot Companies: Send These 12 Questions in Writing Before Any Demo, Then Grade the Reply (Free Vendor Reply Checker)

Read the guide →

🧭

Chatbot Code Python You Can Run Today: Generate a Script From Your Own FAQ, Then Add Memory, Lead Capture and a Web Endpoint (Free Code Generator)

Read the guide →

🛠️

Chatbot Design Blueprint: Sketch Your Bot's Menu Tree on Paper and Catch Problems Before You Build

Read the guide →

Plan the chat, then switch it on

Turn your storyboard into a welcome message, AI answers, saved replies and an after-hours away form. Start free on livechatbot.in.