Chatbot Messages Inventory: The 10 Slots Every Website Bot Fills, the Ones Most Businesses Forget, and How to Keep Them All in Step (Free Inventory Builder)

Chatbot messages are written in bits: a welcome line when you install the widget, an away message when you set opening hours, a proactive message when you try Flows, a reply or two when you train the bot. Nobody ever looks at them all together, so gaps and contradictions creep in. This guide gives you a simple inventory of the ten message slots a website bot can fill, shows you where each one lives, which ones small businesses usually forget, and how to keep times, prices and promises consistent. A free tool builds the inventory for you and flags what to fix.

10message slots to check
4slots that matter most
30 minto build your inventory
Every 3 monthsto review it

⚡ In short

  • Your bot doesn’t send one message. It sends up to ten different ones, each triggered by a different moment.
  • Write them all down in one place: slot, when it shows, the exact text, and the date you last checked it.
  • The four that matter most: welcome, fallback, handover and away. Missing any of them leaves visitors stuck.
  • Check every time, price and wait across all slots. They should tell the same story as your website.
Chatbot messages 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.

The problem

Why chatbot messages need an inventory, not more examples

There’s no shortage of example lines online, and they’re useful when you’re staring at an empty box. But most small businesses don’t have a writing problem. They have a visibility problem.

Think about how your bot’s messages got there. The welcome text was typed on the day you installed the widget, maybe a year ago. The away message was written when you set opening hours, before you started opening on Sundays. A proactive message was added during a sale and never taken down. The fallback is whatever the tool shipped with. Each was written in a different settings screen, on a different day, sometimes by a different person.

Nobody ever reads them side by side, so nobody notices that:

  • the proactive message promises “24/7 support” while the away message says you’re closed until 10 am,
  • the welcome line asks a question but the bot can’t answer half the replies people give,
  • the handover message says “connecting you now” but doesn’t say what happens if nobody is free,
  • there is no follow-up at all, so a visitor who goes quiet hears nothing more.

An inventory fixes that. It is a single list of every message your website chat can send, with the moment that triggers it and the date you last checked it. It takes about 30 minutes to build. Once you have it, reviewing your bot becomes a ten-minute read instead of a hunt through settings pages.

If your problem is writing a single line well, our guides to welcome messages and plain bot wording will help. This guide is about the whole set.

The ten slots

Every message a website bot can send, and when

Not every business needs all ten. The first column is the slot name the free tool below understands.

SlotWhen it showsWho sends itWhere it usually lives
welcomeChat window opensWidgetWidget settings (welcome text)
grabberBeside the closed chat buttonWidgetAttention grabber card
proactiveA chosen page, source, country or visit countFlowFlows
followupVisitor didn’t reply to the first messageFlowFlows (follow-up message)
fallbackThe bot has no answerBotBot settings and knowledge
handoverChat passes to a personBot or teamSaved replies or bot settings
awayOutside opening hoursWidgetOpening hours and away form
confirmAfter the away form or contact details are sentWidget or teamAway form, saved replies
rescuerA chat is about to go unansweredFlowFlows (chat rescuer)
closingThe chat endsTeamSaved replies

Step 1

Collect every message in one sitting

Open a plain text file and your chat dashboard side by side. Go through each place below and copy the exact text, word for word, into the file. Put the slot name and a colon in front of each line, like `welcome: Hi, how can we help?`. That format is what the free tool reads.

Widget settings. Copy the welcome text and, if you use one, the attention grabber card text. If you have welcome translations for other languages, note them too; they’re part of the same slot.

Flows. Open each active Flow. Copy its proactive message and its follow-up message, and note the conditions it runs on (which page, which device, which visit number). If you use the chat rescuer, copy that message as well. Turn off any Flow you no longer recognise.

Opening hours. Copy the away message and the text around the away form. Then check what happens after someone sends the form: is there a confirmation line, and does it say when you’ll reply?

The bot. Ask it something it can’t possibly know, like “what’s the weather in Shimla”. Whatever it says is your fallback. Then ask for a person and copy what it says. That’s your handover.

Saved replies. Look for the replies your team sends at the end of a chat, or when they take over from the bot. Those are your closing and handover lines.

Don’t rewrite anything yet. The point of this step is to see what visitors actually see today, including the parts nobody remembers writing.

Free tool

Build your inventory and find what to fix

Paste the lines you collected. The tool lists all ten slots, marks each one as ready, to fix or missing, checks every time and price you mention, and gives you a plain-text inventory to save.

Paste every message your bot and widget send, one per line, starting with its slot name and a colon. Slot names: welcome, grabber, proactive, followup, fallback, handover, away, confirm, rescuer, closing. Leave out the slots you don’t have yet.

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

Step 2

The four slots that matter most

The tool scores four slots as important because each one covers a moment where a visitor can get stuck with nowhere to go.

Welcome

This is the first thing anyone sees when they open the chat. A welcome that only says “Hi! How can we help?” works, but one that names two or three common reasons people chat (“Checking an order, or looking for a size?”) gets people typing faster, because it tells them what’s allowed. End it with a question.

Fallback

Every bot misses sometimes. What matters is what it says next. “Sorry, I didn’t understand” with nothing after it is a dead end. A good fallback offers a way forward: a person, a contact option, or two topics the bot does know. Our guide to error moments has more on this.

Handover

When a chat passes to your team, the visitor needs to know two things: that a person is coming, and roughly how long it will take. “Connecting you now” answers neither if nobody picks up for ten minutes. Add a realistic wait and what happens if nobody’s free. The handover guide covers the full flow.

Away

Outside opening hours the away message does all the work. It should say you’re closed, when you’re back, and how you’ll reply to anyone who leaves details. LiveChatBot’s away form collects an email or phone number; set it up with our opening hours guide.

If any of these four are missing or flagged, fix them before anything else.

Step 3

The forgotten slots: follow-up, confirmation and closing

In most inventories the same three slots come up empty. None of them is urgent on its own, but each one quietly loses conversations.

Follow-up. A visitor sees your proactive message, reads it and doesn’t reply. Without a follow-up, that’s the end. A short second message a little later, such as “Want me to check delivery to your pin code?”, gives them an easy reason to answer. Make it a question they can reply to in one word. Flows let you add one to any proactive message; see how to create a chat flow.

Confirmation. Someone fills in the away form at 11 pm. What do they see? If the answer is a blank “Thanks”, they don’t know whether it worked or when to expect a reply. Say when you’ll get back to them and on which channel: “Got it. We’ll WhatsApp you after 10 am tomorrow.”

Closing. Most chats just stop. A closing line (“Glad that’s sorted. If anything else comes up, this chat is here”) ends things warmly and tells people they can come back. Save it as a saved reply so your team can send it in one tap.

The other two optional slots, the attention grabber and the chat rescuer, are worth adding once the core is solid. The grabber helps on busy pages where people don’t notice the chat button. The rescuer catches chats when your team is stretched.

Before and after

What a quick inventory fix looks like

Illustrative messages from a made-up saree shop, the same ones loaded by the tool’s example.

Proactive
🚩 Before“Dear customer, kindly let us know if you require any assistance with your purchase as our team is available 24/7 to help you instantly with all your queries.”
✅ After“Need help picking a saree for a wedding? Ask me about fabric, sizes or delivery.”
Fallback
🚩 Before“Sorry, I did not understand that.”
✅ After“I’m not sure about that one. I can help with delivery, returns or sizes, or I can pass you to our team.”
Handover
🚩 Before“Connecting you to our team now.”
✅ After“Passing you to our team. Someone usually replies within 5 minutes; if we’re busy, leave your number and we’ll call you back.”
Confirm (was missing)
🚩 BeforeNothing. The form just closes.
✅ After“Thanks, we’ve got your number. We’ll WhatsApp you after 10 am tomorrow.”

Step 4

Check that every message tells the same story

Once all your messages sit in one list, read them top to bottom as if you were a visitor who sees every one of them. You’re looking for four kinds of mismatch.

Times. If the away message says 10 am to 7 pm, no other message should say “we’re always here” or “24/7”. If you’ve started opening on Sundays, every message that mentions days needs updating. The tool’s “Facts to double-check” list pulls out every time and wait it finds so you can compare them at a glance.

Prices and numbers. Delivery charges, free-shipping thresholds, return windows and COD limits change. When they do, the website gets updated and the chat messages often don’t. Every ₹ figure in your messages should match your pricing or policy pages today. We wrote a separate guide to mismatched facts across channels if your WhatsApp and email auto-replies have the same problem.

Promises. “Instant”, “immediately” and “right away” are promises. Only use them if you can keep them at 9 pm on a Saturday. A realistic “usually within 10 minutes” builds more trust than an instant reply that never comes.

Voice. If the welcome is friendly and casual but the proactive message reads like a bank letter (“kindly”, “dear customer”, “do the needful”), the bot feels like two different people. Pick one voice and rewrite the odd one out.

Fix the mismatches in the dashboard, then update your inventory file with the new text and today’s date.

Step 5

Give each message a one-line spec

The inventory tells you what each message says. A one-line spec tells you what it’s for, so the next person who edits it doesn’t break it. For each slot, write four things next to the text:

  • Goal: what the visitor should do after reading it. “Type a question.” “Leave a phone number.” “Wait two minutes.”
  • Must include: the one fact it can’t lose. For the away message that’s your opening time; for the handover it’s the wait.
  • Length: a target, such as under 160 characters for chat bubbles and under about 90 for a grabber card. Short messages fit phone screens without scrolling; our pacing guide explains why.
  • Owner: who is allowed to change it, and who checks it after a price or hours change.

For example, a spec for the away slot might read: “Goal: leave a number. Must include: opening time and that we reply on WhatsApp. Length: under 160. Owner: shop manager.”

This sounds formal for a small shop, but it saves real trouble. Most broken chatbot messages were never written badly; they were edited by someone who didn’t know why a line was there. A spec gives them the reason in one line.

Keep the inventory and specs in one shared file, such as a Google Doc or a note pinned in your team’s WhatsApp group, so everyone edits the same copy.

Quarterly review

Ten-minute inventory check

Review progress

Keeping it current

When to update the inventory between reviews

A quarterly check catches slow drift, but some changes should trigger an update the same day. Keep a short list of triggers in the inventory file itself:

  • Opening hours change, including holiday and festival hours. Update the away message, the confirmation line and anything that mentions a wait.
  • Prices, delivery charges or policies change. Search your inventory for every ₹ figure and number of days.
  • A sale or campaign starts or ends. Add the proactive message when it starts and put a reminder in your calendar to remove it when it ends.
  • Someone new joins the team and starts sending closing or handover lines. Point them to the saved replies so they use the agreed wording, with {name} where it helps. See saved replies.
  • You add a new page or product line that people will ask about. Check that the welcome and fallback still mention the right topics.

The point isn’t paperwork. It’s that every visitor, at any hour, on any page, gets messages that are true today and lead somewhere. With all your chatbot messages in one list, that stops being something you hope for and becomes something you can check in ten minutes.

Getting started

Build your inventory this afternoon

Set aside 30 minutes. Copy every message from your widget settings, Flows, opening hours, bot and saved replies into one file with slot names in front. Paste it into the tool above, fix the important slots first, then the forgotten ones, then the mismatched facts. Save the inventory it gives you and put a review date in your calendar.

LiveChatBot’s free plan includes the widget with welcome text and attention grabber card, Flows with proactive messages, follow-ups and the chat rescuer, opening hours with an away form, saved replies with {name}, the AI Agent with a small free monthly allowance and a free keyword bot, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.

Frequently asked questions

How many chatbot messages does a small business website need?

Four are essential: a welcome, a fallback for when the bot has no answer, a handover to a person, and an away message for after hours. Follow-up, confirmation and closing lines are the next three to add. Many small sites run well on those seven.

What is a message inventory?

One list of every message your website chat can send, with the moment that triggers it, the exact text and the date you last checked it. It lets you review the whole set in minutes instead of opening each settings screen.

How often should I review my bot’s messages?

Every three months, plus the same day whenever opening hours, prices, delivery charges or policies change, or when a sale starts or ends.

Why does the tool flag 24/7 when I have an away message?

Because the two contradict each other. If your chat has opening hours, a promise of round-the-clock or instant help will be broken for anyone who visits after hours.

Does the inventory tool send my messages anywhere?

No. It runs entirely in your browser and nothing is sent or saved. Copy the inventory it builds into your own file.

Keep reading

Related guides

📘

Chatbot Marketing Examples for the Indian Calendar: 14 Seasonal Campaigns, Month by Month

Read the guide →

🧭

Chatbot Marketing Funnel: How to Turn Anonymous Visitors Into Leads, Buyers and Repeat Customers

Read the guide →

🛠️

Chatbot Maker Red Flags: 10 Things That Look Great in a Demo but Cost You Later

Read the guide →

Every message, true and in step

Set your welcome text, Flows, away form and saved replies in one dashboard, and keep them consistent. Start free on livechatbot.in.