How to set live chat hours when nobody on the team works 24/7

The short version

• Start with one reliable two-to-four-hour coverage window.
• Choose the window from visitor and conversion patterns, not office habit.
• Show accurate online and offline states.
• Collect the question and contact route after hours.
• Promise a response window the team can meet on its worst normal day.

Choose the first coverage window

Look at high-intent visits, checkout starts, bookings, and conversation attempts by hour. Overlay the times somebody can answer without abandoning higher-value work. A shorter reliable window is better than all-day availability nobody owns.

If data is thin, begin with the busiest overlap between customer activity and team capacity, then review after two weeks.

Name an owner and a backup

One person owns new conversations during each window. A second person steps in when the owner is unavailable or the queue crosses a simple threshold. At handoff, unresolved conversations get a note and a named next owner.

Make offline useful

• State that the team is away.
• Ask for the question before requesting contact details.
• Explain the next response window in the customer's timezone when possible.
• Send the message into the same inbox as live conversations.
• Do not send an instant greeting that implies a human is present.

Review reliability, not just speed

Track median first response during staffed hours, missed conversations, replies delivered inside the offline promise, and conversations that changed channel because the handoff failed. Expand hours only when the existing window is dependable.

FAQ

Recommended next steps

FAQ