The fastest way to lose trust in chat is to offer a real person and then not provide one. A visitor clicks "talk to someone", waits four minutes, and gets nothing. They would have been happier if you had never offered.
Live human takeover is genuinely useful. A team member marked on duty can step into a conversation from the inbox when the assistant has done what it can. But it only works if on-duty means someone is actually watching. Setting live chat on duty hours is less a software setting than a staffing decision, and small teams usually get it wrong by being too generous.
The goal is fewer hours that are honoured, rather than a long window that nobody watches.
Start from when chats arrive
Most owners set on-duty hours to match the office: nine to five, Monday to Friday. Then they discover that half their conversations arrive at lunchtime and after 7pm, and the nine-to-five window mostly overlaps with the hours when staff are on the phone or on site.
Look at your conversation history before choosing. You are looking for two things: the hours with the most chats, and the hours when someone at your business can realistically keep an inbox open and reply within a few minutes.
The best on-duty window is where those two overlap. If there is barely any overlap, that is useful to know too. It means the assistant plus good follow-up is your main channel, and live takeover is a bonus for a couple of hours a day.
What counts as actually on duty
Being on duty should mean something specific. Agree it with your team in one sentence each:
- Inbox open. Not in a tab somewhere, but visible.
- Reply within five minutes. Or whatever number you set, as long as it is short and honest.
- Not on a customer call or a job. A receptionist who is also on the phones is not on duty for chat during a rush.
- Go off duty when you step away. Lunch, school run, a meeting. Switching your status off takes seconds and stops visitors being left hanging.
That last one is where most live backup fails. People forget to go off duty, and the assistant keeps offering a person who has gone to get a sandwich.
Outside on-duty hours
When nobody is on duty, the assistant keeps working. It answers from your content, captures leads and can open a numbered support ticket. The one thing it should never do is imply a person is about to appear.
Visitor: Can I speak to a real person about my invoice? Assistant: The team is not online right now, they are usually around on weekday afternoons. I can take your details and a short note about the invoice, and someone will pick it up when they are back. Would that help? Visitor: Yes, it's invoice 4471, I think I was charged twice. Assistant: Thanks. I have opened ticket 1182 with that note. What is the best email for them to reply to?
That reply is honest about availability, sets a rough expectation and turns the request into something your team can act on. Tickets land in the support inbox on Pro, so the morning person has a list instead of a mystery. Our guide to support tickets from chat covers how to word those.
Be careful with the expectation. "Someone will reply within an hour" at 11pm on a Friday is a promise you will break. "When they are back" or "on the next working day" is safer.
A rota for small teams
A written rota stops on-duty time from evaporating. Here is an example for a four-person service business with chats clustering around lunch and early evening. Swap in your own people and hours.
| Day | 11:30–14:00 | 17:00–19:00 | Backup if absent |
|---|---|---|---|
| Monday | Priya | Sam | Owner |
| Tuesday | Sam | Priya | Owner |
| Wednesday | Jo | Sam | Priya |
| Thursday | Priya | Jo | Sam |
| Friday | Sam | Nobody (assistant only) | None |
| Saturday | Owner, 10:00–12:00 only | Nobody | None |
| Sunday | Nobody | Nobody | None |
A few things this rota does on purpose. It covers the two busiest windows rather than the whole day. It names a backup, because the rota breaks the first time someone is ill. It is honest about Friday evening and Sunday, where the assistant runs alone. And the early evening slot suits someone who prefers a later start.
Four and a half hours a day of real cover is a lot more valuable than a nominal nine-to-five that nobody honours.
Setting it up step by step
- Pull a month of conversations and note which hours they arrive in.
- Ask each team member which windows they can genuinely watch the inbox.
- Pick one or two windows where demand and availability overlap.
- Switch on the transfer-to-human action for the assistant, and write when it should offer a person. Our guide to deciding when a person takes over helps with that wording.
- Tell the assistant your usual availability in its instructions so it can describe it honestly.
- Write the rota, including backups, and put it somewhere everyone sees.
- Run it for two weeks, then check how many takeover requests went unanswered.
Signs your hours need changing
Review after a fortnight. If visitors are asking for a person and the transcripts show nobody took over, your window is too wide or the on-duty person is too busy. Narrow it.
If the on-duty person spent two hours watching an empty inbox every day, move the window, or drop it and rely on tickets and quick morning follow-up. If lots of takeover requests arrive at one specific time outside your hours, that is the slot to add next.
Also check lunch. Many small businesses find the hour they most need cover is the hour everyone is away from their desk, which is why covering lunch and busy hours gets its own guide.
Your next move
Before touching any setting, pull last month's conversations and tally them by hour. Then have a ten-minute conversation with your team about who can watch the inbox and when. Put the answer in a table like the one above, pin it up and start with the smallest window you are sure you can keep.
Widen it only once you have kept the narrow one for a month. The setup steps for takeover are in the docs.