Chatbot Online 24/7, Team Online 9 to 6: Map Who Answers Every Hour of Your Week (Free Coverage Planner)

Chatbot online all day and night sounds like the whole point: switch the bot on and it answers around the clock. But your team works fewer hours than that, takes lunch, closes on Sundays and goes home for festivals. The real job is deciding who answers in each of the 168 hours of the week, what the bot says when it is alone, and how a chat passes from the bot to a person and back. This guide shows how to map your week, find the busy hours where the bot has no backup, and set up each handover. A free planner draws the map for you.

๐Ÿ‘ค What the visitor seesSaturday, 4:20 pm
hi, is the green saree in stock in silk?
๐Ÿค– AI AgentThe team is away right now and back on Monday at 10 am. Leave your email or phone and they’ll check stock and reply first thing.
ok, 98xxxxxx10
Away form saved ยท ticket created for Monday

Illustrative chat: the bot is alone, and says so honestly.

โšก In short

  • A website bot is on for all 168 hours of the week. Your team covers far fewer, often under a third.
  • Every hour falls into one of three modes: team at the desk, someone on the phone app, or the bot alone.
  • Map the modes against when visitors arrive. Busy hours with the bot alone are where you lose people.
  • Fix each gap with honest opening hours, an away form, clear handover rules and a morning routine.
Chatbot online 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 real question

Your bot never sleeps. Your team does

When owners first switch on a website bot, they usually think about what it will say. Far fewer think about when it will be on its own. Keeping a chatbot online every hour is the easy part. Deciding what happens around it is the question that decides how most visitors experience your chat.

Do the arithmetic. A week has 168 hours. A shop team that works 10 am to 7 pm on weekdays, with a one-hour lunch, and half a day on Saturday, is at the desk for about 44 of them. That’s roughly a quarter of the week. For the other three quarters, the bot is either alone or backed up by someone glancing at a phone.

That’s fine, as long as you plan for it. Problems come from the gaps nobody planned:

  • A visitor asks a stock question at 2:15 pm, during lunch, and waits ten minutes for a reply that never comes.
  • A chat starts at 6:50 pm, the team leaves at 7, and the visitor is left mid-conversation.
  • The widget says “We reply in a few minutes” on Sunday, when nobody is in until Monday.
  • During Diwali week the team is off for three days, but the bot keeps promising same-day replies.

None of these is a bot problem. Each is a coverage problem: nobody decided who answers at that hour, or what the bot should say when nobody can. Mapping your week fixes that in an afternoon.

If you want examples of what a good bot conversation looks like in different industries first, see our six industry chats. This guide is about the hours around those conversations.

Three modes

Every hour of your week is one of these

Name the mode for each hour and you know what the bot should say, what it may promise and who picks up next.

๐Ÿง‘โ€๐Ÿ’ป

Team at the desk

Someone is logged in to the inbox and can reply within a minute or two. The bot greets, answers quick facts and hands over anything that needs a person. Promises like “someone will reply now” are true.

๐Ÿ“ฑ

Someone on the phone

Nobody is at a desk, but one person has the Android app with alerts on. Replies take longer and can’t involve looking things up in other systems. The bot should set a realistic wait, such as “within 30 minutes”.

๐Ÿค–

Bot alone

Nobody will reply until the next working day. The bot answers what it knows, says honestly when the team is back, and collects an email or phone number for everything else. No promises of a quick human reply.

Step 1

Write down the hours you really answer

Start with honesty, not the sign on the door. The hours that matter are the hours when someone will actually reply to a chat, and they are almost always shorter than your shop or office hours.

Go through a normal week and note, for each day:

  • When the first person logs in and is ready to answer, not when the shutter goes up. If the first hour is spent on deliveries and cash counting, chat starts later.
  • When the last reply can realistically go out. If the team leaves at 7, the last time a new chat can be handled properly is probably 6:30 or 6:45.
  • Breaks with nobody covering. Lunch is the big one. Also prayer breaks, school runs and the daily bank visit, if they leave the inbox empty.
  • Weekends. Many small businesses are half-open on Saturday and closed on Sunday, which happens to be when online shoppers browse most.
  • Who checks the phone after closing, and until when. Be specific: “Ravi checks the app until 10 pm on weekdays” is a plan; “we usually see messages” is not.

Write it as a simple table, one row per day. Then do the same for unusual weeks: festival closures, stock-taking days, the week the owner is travelling. You’ll use those later.

This is also where teams discover they’ve been promising more than they deliver. If the website says “We’re online 9 to 9” and the real hours are 10:30 to 6:30, that difference is where your slowest replies and most abandoned chats come from. Our guide to live chat response time shows why the first minutes matter so much.

Free tool

Map your chatbot online coverage, hour by hour

Enter your real hours, your lunch break, weekend hours and any phone-app cover after closing. The planner draws all 168 hours, weights them by a typical visitor pattern, and lists your biggest bot-alone blocks with what to set up for each.

Enter the hours your team really answers chats, not the hours on the shop sign. Pick the visitor pattern closest to your business. The planner maps every hour of the week and shows where the bot is alone.

Runs only in your browser; nothing is sent or saved. Visitor patterns are illustrative shapes, not measured data. Use your own visitor tracking for real numbers.

Reading the map

Hours matter less than traffic

The planner gives you two kinds of numbers, and the second one is more important.

Hours are simple: how many of the 168 hours fall into each mode. Most small businesses find the bot is alone for well over half the week. That sounds alarming, but much of it is 1 am to 7 am, when almost nobody visits.

Traffic share weights each hour by how busy it usually is. The planner uses three illustrative shapes: online shops that get busier into the evening and at weekends, local services and B2B firms that peak during office hours, and coaching or education businesses that peak in the evening and on Sundays. These are rough shapes, not measured data, so treat the percentages as a guide. For real numbers, look at when your own visitors arrive in your visitor tracking.

What you’re looking for are busy blocks with the bot alone. In the example (an online shop open 10 am to 7 pm on weekdays and 10 to 2 on Saturday), the biggest gaps are Saturday afternoon and evening, all of Sunday, and weekday evenings after 10 pm. Those are exactly the hours when shoppers have time to browse.

For each big block, you have three choices:

  1. Cover it with people, for example by moving one person’s shift later, or adding phone-app cover on Sunday afternoons.
  2. Make the bot better at it, by writing answers for the questions people ask at that time.
  3. Accept it honestly, with a clear “back on Monday at 10 am” message and an away form, so nobody waits for a reply that isn’t coming.

Most businesses use a mix. The point of the map is to make each choice on purpose.

Edge moments

Five hand-off points that go wrong most often

Most coverage mistakes happen at the edges, when one mode changes into another.

OpeningThe first 30 minutes

Chats that came in overnight are waiting, and new ones are arriving. Answer overnight contacts in order of arrival, but don’t leave a live visitor waiting while you clear the backlog.

LunchThe silent hour

The inbox looks staffed, so the bot keeps saying “someone will be with you shortly”. Stagger breaks or have one person keep the phone app on.

ClosingThe last hour

A chat that starts at 6:50 can run past 7. Decide who finishes open chats, and stop promising instant replies 15 to 30 minutes before close.

WeekendFriday evening to Monday morning

The longest bot-alone block for most teams. The welcome text and away messages must say when the team is back, by day and time.

HolidaysFestival and leave days

Normal hours stop being true. Change opening hours for those dates and add a short note so the bot doesn’t promise replies on a closed day.

What the bot says

Write a line for each mode, not one line for everything

A single welcome message can’t be honest in all three modes. “Hi! We usually reply in a few minutes” is true at 11 am on a Tuesday and false at 11 pm on a Saturday. Write one set of lines for each mode. The desk and phone lines become saved replies your team uses; the bot-alone lines go into the away message and the bot’s knowledge, which show outside your opening hours.

Team at the desk

Keep it short and confident: “Hi, I can answer quick questions, and the team is here if you need them.” The visitor should know a person is close by. When the bot can’t answer, the handover message is: “Let me get someone from the team. They usually reply within a couple of minutes.”

Someone on the phone

Set a realistic wait and limit the promise: “The team is out of the office but checking messages. Replies may take up to 30 minutes.” For anything that needs a system, such as an order lookup, the reply is honest: “I’ll note this for the team to check first thing tomorrow.”

Bot alone

Lead with the time the team is back, then offer what the bot can do: “The team is back on Monday at 10 am. I can answer questions about delivery, sizes and returns now, or take your email and they’ll reply first thing.” Never imply someone is watching when nobody is.

In every mode, the bot answers the same facts the same way. Only the promises about people change. Our welcome message guide has more wording ideas, and saved replies let your team reuse the same lines.

Wording

Same question, three honest answers

Tuesday 11 am ยท team at desk
๐Ÿšฉ Instead of“Please wait, an agent will join soon.” (No time, no help in the meantime.)
โœ… Say“I’ve passed this to Meera on the team. She usually replies within two minutes.” (Illustrative.)
Thursday 9 pm ยท phone-app cover
๐Ÿšฉ Instead of“Someone will reply right away!”
โœ… Say“The team is checking messages tonight; replies may take up to 30 minutes. Order changes are handled tomorrow from 10 am.”
Sunday 4 pm ยท bot alone
๐Ÿšฉ Instead of“We’re online! How can I help?” with nobody coming.
โœ… Say“The team is back Monday at 10 am. I can answer delivery and size questions now, or take your email for anything else.”

Setting it up

Turn the map into settings in LiveChatBot

Once you have the map and the lines, the setup itself is short. In LiveChatBot, everything below is on the free plan.

Opening hours. Enter your desk hours exactly, day by day, not your shop hours. Outside those hours the widget shows an away form that collects an email or phone number. Our opening hours guide walks through it. Leave phone-app cover out of the official hours; it’s a bonus, not a promise.

The bot’s knowledge. The AI Agent answers from the knowledge you give it, so the bot-alone blocks are where that knowledge matters most. Write answers for the questions people ask in those hours first. See training your AI chatbot. If AI replies are unavailable or used up, the free keyword bot answers from your saved replies instead.

The phone app. The person on evening cover needs the Android app with alerts switched on. Agree what they may handle from the phone and what waits for the morning.

Flows. Flows can send proactive messages based on page, source, country, device, browser language, number of visits and more, and the chat rescuer can follow up when a visitor is left without a reply. Use them during staffed hours, when someone can respond to the chats they start.

Tickets. Offline messages can become tickets, with an owner and a status. That turns the away form into a morning to-do list instead of a pile of messages. See turning a chat into a ticket.

Checklist

Coverage setup, start to finish

Coverage plan

Holidays and busy seasons

Plan the weeks that don’t look like a normal week

Your map describes a normal week, but the weeks that hurt are the unusual ones. Diwali, Eid, Christmas, a family wedding, the annual stock-take, a sale that doubles your traffic: each changes who is available and how many people visit.

Make a short list of the dates you already know about for the next three months. For each one, decide three things ahead of time:

  • New hours. Which days are fully closed, which are short? Update the opening hours a day or two before, so the away form appears at the right times.
  • A one-line note for the bot’s welcome text: “We’re closed 1 to 3 November for Diwali and back on the 4th. Orders placed now ship on the 5th.” (Illustrative dates.) Visitors forgive a closure they’re told about.
  • Who clears the backlog on the first day back, and how long it should take. After a three-day closure, there may be a few dozen away-form messages waiting.

Sales and launches are the opposite problem: lots of visitors, and the team is busy with orders. That’s a good time to add phone-app cover in the evening and to make sure the bot can answer the sale’s terms without help. Our peak days playbook covers surges in more detail.

Write these plans into a shared calendar so nobody has to remember. A two-minute change before a holiday saves an hour of apologies after it.

Keep it current

A 15-minute review every Monday

Coverage drifts. Someone changes shift, the lunch break moves, a new person joins the evening cover. Once a week, spend 15 minutes checking that the map still matches reality.

Look at three things in the inbox:

  1. Chats from bot-alone hours. Which questions did the bot fail to answer? Those are the next answers to write, because nobody else could help those visitors.
  2. Away-form messages. How many came in, and how quickly were they answered the next working day? If Monday mornings are always swamped, consider Sunday phone-app cover for a few hours.
  3. Chats at the edges. Look for chats around opening, lunch and closing that waited a long time or ended without a reply. They tell you which hand-off needs work.

Then re-run the planner if anything has changed, and update the opening hours to match. A well-run chatbot online all week is mostly a matter of these small, regular checks, not a one-time setup.

If your bot-alone hours keep turning up the same type of question late at night, our night-shift guide covers what a bot should and shouldn’t answer after hours, and how to hand the rest to the morning team.

Getting started

Map your week today

Open the planner above, enter the hours your team really answers, and look at the three biggest bot-alone blocks. Write one line for each mode tonight. Tomorrow, set your opening hours to match and test the widget at three times of day: during desk hours, after closing and on Sunday.

LiveChatBot’s free plan includes the chat widget, the team inbox, the Android app, opening hours with an away form, Flows, tickets, saved replies, and an AI Agent with a small free monthly allowance, backed by a free keyword bot. It covers two websites with 100 visitors per website each month, with no per-seat charges. See pricing and start at livechatbot.in.

Frequently asked questions

Can a chatbot online all week replace staff?

No. It can answer common questions at any hour and collect contact details when nobody is in, but questions about specific orders, payments and complaints still need a person. The aim is to make every hour honest, not to remove people.

What should my opening hours be?

The hours someone is actually at the desk and can reply within a minute or two. Leave evening phone-app cover out of the official hours, so the bot never promises more than you deliver.

What happens to chats when nobody is online?

Outside opening hours, the widget shows an away form that collects an email or phone number. Those offline messages can become tickets, so the team answers them in order the next working day.

Are the visitor patterns in the planner real data?

No. They’re illustrative shapes for three types of business. Check when your own visitors arrive in your visitor tracking and adjust your plan if your busy hours are different.

How often should I re-check my coverage?

A 15-minute review every Monday is enough for most small teams, plus a quick plan before every holiday, sale or staff change.

Keep reading

Related guides

๐Ÿ“˜

Chatbot Options, Narrowed Down: Cross Off the Routes Your Limits Rule Out and Keep a Shortlist of Two (Free Route Eliminator)

Read the guide โ†’

๐Ÿงญ

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)

Read the guide โ†’

๐Ÿ› ๏ธ

Chatbot Message Examples, Taken Apart: The 4-Part Pattern Behind 24 Good Bot Replies (Free Message Part Finder)

Read the guide โ†’

More to read

More guides on this topic

๐Ÿ“˜

Chatbot for Pet Store Website: Plan Who Answers When, From Morning Food Orders to Late-Night Delivery Worries (Free Coverage Planner)

Read the guide โ†’

Make every hour of your week honest

Set opening hours, an away form and a bot that knows your answers, then let the team pick up the rest. Start free on livechatbot.in.