Support Bots and Staffing: How Many People Do You Still Need? An Hour-by-Hour Calculator for Small Teams

Support bots change how many people you need for chat, but rarely to zero, and almost never evenly across the day. A bot that settles 40% of chats doesn’t cut your staffing by 40%: it trims the quiet hours more than the busy ones, and it leaves the longer, harder chats for people. This guide walks through the simple maths of chat staffing, shows what a bot really changes, and gives you a calculator that turns your chat volume and opening hours into how many people you need at each hour of the day.

4numbers you need: volume, bot share, minutes, concurrency
25%buffer for breaks and slow chats
1busiest hour that sets your minimum team
0per-seat charges on LiveChatBot

⚡ In short

  • Staffing depends on four numbers: chats per hour, the share the bot settles, minutes per human chat and chats per person at once.
  • Plan for your busiest hour, not your daily average. That hour sets the minimum team.
  • Bots remove the short, easy chats, so the chats left for people take longer on average.
  • Outside your online hours, the away form and tickets keep chats from being lost.
Support bots in LiveChatBot: the LiveChatBot shared inbox with a conversation open
How it looks in LiveChatBot: the LiveChatBot shared inbox with a conversation open.

The myth

Why a 40% bot doesn’t mean 40% fewer people

When owners first add a bot, they often expect staffing to drop in proportion: if the bot handles 40% of chats, surely we need 40% fewer people. It rarely works out that way, for three reasons.

The bot takes the easy chats. The questions a bot settles alone are the short ones: timings, prices, delivery areas. Those took a person a minute or two. The chats left over are complaints, custom requests and anything involving an order, which take longer. So the chats drop by 40%, but the minutes drop by less.

Peaks don’t shrink evenly. Staffing is set by your busiest hour. If the bot takes 40% off a peak of 20 chats an hour, you still have 12 chats in that hour, which may still need two people.

You can’t hire 0.6 of a person. Below a certain volume, you need one person online or none. A bot often turns “one-and-a-bit people” into “one person”, which is a real saving, but not a proportional one.

None of this makes support bots less useful. It just means the honest way to plan is hour by hour, with your own numbers, which is what the calculator below does. If you’re still deciding what the bot should handle, our auto chat bot audit helps you sort chats first; this guide assumes you know roughly what share the bot will settle.

Free tool

Work out how many people you need, hour by hour

Start with your chats per day and opening hours. For the best result, count a week of chats per hour and paste your own pattern.

The arrival shapes are illustrative patterns, not industry data. For real planning, count a week of your own chats per hour and paste them in. Nothing is stored.

The maths

Four numbers, one formula

The calculator uses a simple formula you can also do on paper. For each hour of the day:

  1. Chats this hour = chats per day × the share that arrive in this hour.
  2. Chats for people = chats this hour × (1 − the share the bot settles).
  3. Person-minutes needed = chats for people × minutes per chat.
  4. People needed = person-minutes ÷ 60 ÷ chats each person handles at once.
  5. Add a 25% buffer for breaks, slow typers and the chat that takes 20 minutes, and round up.

A worked example

An illustrative clothing store gets 120 chats a day, with the busiest hour (7 pm to 8 pm) bringing about 12 of them. The bot settles 40%, leaving about 7 chats for people. Each takes about 6 minutes, so that's roughly 43 person-minutes. One person handling two chats at once covers 120 chat-minutes an hour, so one person is enough, even with the buffer.

Without the bot, the same hour has 12 chats and 72 person-minutes. Still one person on paper, but with no slack at all; one long complaint and the queue builds. The bot doesn't remove the person, it removes the stress.

Where the numbers come from

Chats per day and per hour come from your inbox history. Minutes per chat: time ten typical chats with a stopwatch, from the person's first reply to the last message. The bot's share: count chats closed without a person over two weeks. Concurrency: watch your team. Most people manage two simple chats at once; three is a stretch.

Reading the result

What each number on the calculator means

Use them to plan a rota, not as targets.

🤖

Chats settled by the bot

The daily chats nobody on your team needs to touch. Check this against reality after two weeks: count chats closed without a person.

⏱️

Person-hours of cover

The total online time your team needs each day, including the buffer. Split it across shifts.

📈

People at the busiest hour

Your minimum team at peak. If it's 2, someone must be free to help the main person at that hour.

🌙

Chats when nobody is online

These see the away form. If the number is large, consider moving or extending your online hours.

Peaks

Plan for the busiest hour, not the average

Averages hide the problem. A shop with 120 chats a day averages about 9 chats an hour over a 13-hour day. But if a third of those arrive between 6 pm and 9 pm, the evening needs twice the cover of the morning.

Find your peak

Count chats per hour for a full week. Most inboxes show the time of each chat; a quick tally on paper is enough. You'll usually see one or two clear peaks: lunchtime and evening for consumer businesses, mid-morning and mid-afternoon for business customers.

Put your strongest person on the peak

The busiest hour is when wait times grow and mistakes happen. That's not the slot for a new team member on their first day.

Move work out of the peak

Proactive messages, follow-ups and ticket replies can wait. Schedule them for quiet hours so the peak is only live chats.

Use the bot hardest at the peak

Make sure the questions most common at your peak are answered by the bot. If evening chats are mostly "is COD available?" and "when will it deliver?", those saved replies do the most good at 8 pm.

Festivals and sales are different days

Diwali week or a sale weekend can bring several times the normal volume. Run the calculator again with those numbers and plan extra cover in advance. Our peak-day playbook covers the details.

The bot's share

Measuring what your bot really settles

The single most important input when planning around support bots is the share of chats the bot settles. It's also the one people guess wrong most often, usually too high.

Count settled, not touched

A chat where the bot answered and then a person had to step in isn't settled. Count only chats that ended without any person replying, and where the visitor didn't come back with the same question within a day.

Watch for false successes

A visitor who gets a wrong answer and leaves looks the same as a visitor who got the right answer. Read a sample of 20 bot-only chats each week. If several end with the visitor giving up, your real share is lower than the count suggests.

Expect it to grow slowly

In the first weeks, the share usually rises as you add answers for the questions that keep reaching your team. After that it levels off. Plan with today's number, not the number you hope for in six months.

Know what shouldn't count

Complaints, refunds and anything involving money should go to people, even if a bot could technically reply. A higher bot share achieved by keeping unhappy customers away from people is a false saving.

In LiveChatBot, the AI Agent answers from your knowledge, and the free keyword bot answers from saved replies when AI isn't available. Both appear in the inbox alongside your team's chats, so you can review them together.

Building the rota

From the calculator to a weekly plan

An illustrative two-person team using the example numbers above.

HoursExpected chats per hourCoverNotes
10:00 – 13:003 – 5Person ATicket replies and follow-ups between chats
13:00 – 16:005 – 6Person A (B covers lunch)Steady; good time for proactive messages
16:00 – 19:006 – 9Person BEvening build-up starts
19:00 – 21:0010 – 12Person B + owner on the Android appPeak: chats only, no other tasks
21:00 – 10:00FewNobodyAway form collects contacts; tickets wait for the morning

Because LiveChatBot has no per-seat charges, adding the owner as a backup at the peak costs nothing. The Android app lets them answer from anywhere. For a full weekly schedule, see our shift plan for small teams.

After hours

What happens to chats when nobody is online

The calculator's last number, chats arriving when nobody is online, is worth taking seriously. Those visitors are real customers, and they decide in seconds whether to wait, leave a message or go elsewhere.

With opening hours set in LiveChatBot, the chat switches to the away form outside your hours, collecting an email or phone number so you can reply later. Offline messages can become tickets, with an owner and a status, so the morning shift starts with a clear list instead of scrolling through yesterday's chats. The bot keeps answering the questions it can, at any hour.

Two things make after-hours work well. First, tell people honestly when you'll reply: "We're back at 10 am and reply to every message in order." Second, actually clear the list first thing, before new chats start arriving. If after-hours messages wait until the afternoon, the away form becomes a black hole.

If the calculator shows many chats arriving late in the evening, consider shifting your hours rather than adding them. Opening an hour later and closing an hour later often matches customers better at no extra cost.

Run the calculator with your real numbers, build a rota around your busiest hour, and review the bot's share every two weeks. Support bots then do what they're good at: taking the easy chats, any time of day, so your people can give the hard ones proper attention. Start free on livechatbot.in.

Frequently asked questions

Do support bots replace support staff?

Rarely completely. They take the short, repetitive chats, which trims quiet hours and reduces pressure at peaks, but the longer chats still need people.

How do I calculate how many chat agents I need?

For each hour: chats for people × minutes per chat ÷ 60 ÷ chats each person handles at once. Add about 25% for breaks and slow chats, and round up.

How many chats can one person handle at once?

Usually two for typical chats. Three is possible for very short, simple chats; one for complex or sensitive ones.

What share of chats can a bot settle?

It depends entirely on your questions. Measure it: count chats that ended without any person replying over two weeks, and read a sample to check they were really settled.

What if nobody is online?

Set opening hours so visitors see the away form, which collects an email or phone number, and turn offline messages into tickets for the next shift.

Keep reading

Related guides

📘

Software Chatbot for SaaS and App Support: Turn Vague Bug Reports Into Tickets Your Developers Can Fix

Read the guide →

🧭

SMS Chatbot Examples: 8 Two-Way Text Flows Annotated, the Character Limits Behind Them and a Free Segment Checker

Read the guide →

🛠️

Simple Chatbot in Five Answers: How to Build the Smallest Bot That Actually Helps, and Try It Before Going Live

Read the guide →

Plan your team around the busiest hour

Let the bot take the easy chats and put your people where they matter. Start free on livechatbot.in.