Offline and After-Hours Chat Messages: 25 Examples That Keep the Lead

When nobody on your team is online, your chat widget still has to say something, and that one message decides whether a visitor leaves an email address or leaves the site. If it says "an agent will be with you shortly" at two in the morning, the visitor waits for nobody; if it says "we'll be in touch", they cannot tell when.

If you run website chat for a small team, as a founder, a shop owner, a support lead or an agency, the guide below is for you: the three jobs of an offline message, 25 copyable messages by situation, the email-first handoff, PepoChat's Team availability modes, common mistakes and tone notes by industry. Greetings and "I don't know" replies are separate jobs, covered in our 30 chatbot welcome message examples and 20 chatbot fallback messages.

PepoChat is our product, and its settings are named where they matter; every message works in any chat tool. The PepoChat behaviour below was checked against the product documentation and code on 19 October 2026, and every research figure was read on the publisher's own page the same day.

What are the three jobs of an offline chat message?

An offline chat message has three jobs: say honestly that no person can reply right now, give a reply time you can keep, and ask for one thing so the conversation can continue. A message that skips one of the three leaves the visitor guessing.

An offline chat message, also called an away message or an after-hours auto-reply, is what a chat widget tells a visitor who needs a person while nobody on the team can reply in the chat. With an AI support agent on the widget, an offline message no longer means the chat is closed. The agent keeps answering from your knowledge base at any hour, so the offline message covers only the human handoff: the moment a conversation needs someone from your team.

1. Say honestly that no person can reply right now

Name the state in plain words: no one from the team is online, or no one answers this chat live. Nielsen Norman Group's first usability heuristic, visibility of system status, holds that a system should keep people informed about what is going on, and Aurora Harley's article on it warns that "a lack of information often equates to a lack of control." A visitor who knows nobody is there can decide what to do; a visitor who is not told keeps waiting.

Honesty covers who is speaking, too. Raluca Budiu's NN/g study The User Experience of Chatbots advises being upfront about using a bot and offering an escape hatch, such as a real person or another channel, when the bot cannot help. At night, an email reply is that escape hatch.

2. Give a reply time you can keep

Give a day, an hour and a time zone, or a number of business days, never "soon". Customers expect fast replies: in Jeff Toister's March 2020 survey of more than 3,200 people, mostly in the US, UK and Canada, a one-hour email reply met the expectations of 88 percent of respondents, and nearly a third expected a reply within the hour. No small team meets that overnight, which is why the promise has to be specific rather than fast.

Real teams are slower: Gorgias's April 2026 benchmark puts the median first response of ecommerce brands in its $10M GMV band at 6.3 hours (data as of March 2026), and our first response time benchmarks collect more figures by channel. Promise the time you meet in a busy week, such as "by 12:00 tomorrow, London time", and let the AI support agent take the questions that cannot wait.

Waiting without information loses visitors even when people are online. LiveChat's customer service report, with data last updated in 2024, found that customers waited an average of 4 minutes 18 seconds in a chat queue before reaching an agent, and 27.4 percent left the queue before being served. The same report puts average chat availability at 17 hours 58 minutes a day, leaving about six hours uncovered even at companies that use live chat software.

3. Ask for one thing, then confirm

Ask for the one detail you need to reply, which is almost always an email address, and say why: so the answer reaches the visitor after they close the page. Ask in one line, once. A five-field form inside a chat bubble is a form wall, and the guide to chatbot lead generation explains why answering first and asking later works better.

Then confirm. Repeat that the reply will go to the address the visitor gave, and say when it will arrive. Confirmation is the step most companies skip: in SuperOffice's benchmark of 1,000 companies (page last updated March 2023), 90 percent did not acknowledge that a customer's email had arrived, and 62 percent never replied at all.

25 offline chat message examples by situation

The 25 messages below are grouped by situation. Each is under 40 words and under 300 characters, the limit of PepoChat's away message field, and ends with a single ask so it works in any chat tool. Replace the cities, times and holidays with yours, and keep the time zone.

In PepoChat, the agent adds the email question itself, in the same message as your away message, and skips it when the visitor's address is already known. In the Away message field, keep the status and the reply time and leave out the request for an email, so the question appears only once.

After-hours messages for weeknights

Weeknight messages are the ones visitors see most often. Name the hour the team returns and the time a reply will arrive, in your own time zone.

Weekend away messages

A weekend is a long night: name Monday's opening and the hour a reply will arrive, and say why you want the email.

Public holiday and closure messages

Holiday messages need the reason, the return date and room for the backlog; name the holiday, because visitors abroad may not know it. PepoChat's schedule is weekly, with no holiday calendar: switch the holiday off, put the return date in the away message, and switch the day back on afterwards.

Messages for when the team is at an event

Switch the message before the team leaves, not when the first complaint arrives. If someone still covers the chat, give the slower reply time instead of pretending to be closed.

Outage messages

During an incident, acknowledge the problem before the visitor describes it, point to one place for updates, and tell visitors with other questions why replies are slow. Do not guess a fix time: promise the update instead.

Launch-week and busy-season messages

Launches, sales and press coverage multiply messages for a week or two. Stretch the promise for that period rather than missing the usual one every day, and add the launch or sale terms to your knowledge base so the agent can answer them alone.

Email-only messages: "we'll get back to you by email"

For a team that never watches the chat live, the message is the same day and night: nobody answers here live, replies come by email, and here is when.

"The AI is still here" messages

These messages say what the AI has already handled and what waits for a person. In PepoChat, the agent stops replying in a conversation it has handed over, so do not invite more questions in the same thread; for something new, a visitor can start a new chat from the widget's menu.

How does an email-first handoff work when nobody answers live?

An email-first handoff is a handoff in which the AI agent asks for an email address, confirms it and then passes the conversation to people who will answer later, instead of promising that a person will join the chat. It works in seven steps:

1. Answer first. The agent answers everything your knowledge base covers; many after-hours questions never need a person.
2. Say the away message when a person is needed: the visitor asks for one, the knowledge base has nothing relevant, something fails, or the visitor is frustrated.
3. Ask once, in the same message. One short line asking for the email, never a form.
4. Hand over either way. Answer or not, the conversation goes to the team, so a refusal never becomes a dead end.
5. Leave a way back. A visitor who said no should still be able to add an address later.
6. Alert the team with the transcript and the address in one message, so nobody asks the visitor to repeat themselves.
7. Reply where the visitor will see it. Overnight visitors have usually closed the tab, so reply by email, not only in the chat.

PepoChat runs these steps automatically whenever nobody can reply in the chat: outside your hours with My team answers during business hours, and at all times with No one answers live chat, we follow up by email. The agent says your away message, asks once for the visitor's email address in the same message (plus any fields you ticked under lead capture), and hands the conversation over after the visitor's reply, whether or not it contains an address; an address the visitor gives is saved to Contacts. The agent skips the question when the session already has an address; the human handoff docs describe every trigger.

Two safety nets cover the rest. An escalated conversation shows a Get a reply by email card above the message box until the visitor leaves an address, which also catches handovers the agent never announced, such as the Free plan's monthly cap of 200 AI replies or a failed reply. Every workspace member gets an email headed "A visitor needs a person" with the reason, the last three messages, an Open conversation button and, when the address is known, a Reply by email button.

One detail decides whether the promise is kept: PepoChat does not email visitors when you reply in the team inbox. A reply typed in the inbox appears in the widget when the visitor reopens the chat in the same browser within their 24-hour session. For an overnight visitor, use the Reply by email button in the alert or the Send Email button in the inbox's visitor panel.

Business hours or email-only: which Team availability mode should you choose?

Choose business hours if someone really replies in the chat during set hours, and email-only if replies happen in batches whenever someone has time. PepoChat's Team availability card, on the Widget Customization page, offers three options under After a handoff. The AI support agent keeps replying around the clock in all three; the option changes what it promises about people, what the widget shows and when it asks for an email.

Settings checked against PepoChat's widget customization docs on 19 October 2026.

With business hours on, the schedule runs in the timezone you choose, such as Europe/Berlin, with one opening and closing time per day; Monday to Friday, 09:00 to 17:00, is the default, and overnight hours are not supported. The widget's Contact screen swaps "Available 24/7" for your schedule. The Away message holds up to 300 characters; left empty, the agent uses an automatic line with your real return day, time and zone, or "No one is on live chat right now, but our team follows up by email." in email-only mode.

How to set up Team availability in PepoChat

1. Open Widget Customization in the dashboard and scroll to the Team availability card.
2. Under After a handoff, pick the option that matches how your team really works.
3. For business hours, choose the Timezone, then set each day's switch, opening time and closing time.
4. Write the Away message: the status and the reply time from one of the examples above, without the email request.
5. Click Save Settings.
6. Click Test the agent and type "I'd like to talk to a person". Test replies are free, but the escalation email to your team is real.

To test the outside-hours version during the day, switch today off and back on afterwards. The away message is one field shared by both offline modes, so after a holiday or a conference, put your usual text back, or next week's night visitors will read about a trade show that has ended.

What are the most common offline chat message mistakes?

The most expensive mistake is a promise nobody keeps: "someone will be right with you" at night, an "online" badge over an empty office, or an email address collected and never answered. Each one turns a visitor who was willing to wait into one who feels ignored.

Collecting emails nobody answers hurts most, because the visitor did everything you asked. The SuperOffice test above shows the pattern at scale, with most companies never replying. In PepoChat, check that at least one person keeps Email me when a visitor needs a person switched on under Profile → Notifications, since each member can opt out, and start every working day with the inbox filtered to Escalated and Unassigned. Then skim the night's Unresolved conversations: a visitor who closed the tab instead of answering the email question has not been handed over yet.

Fake presence covers the typing dots, the "online" badge and the human name on the bot. Each buys a few seconds of patience and spends the visitor's trust; the human handoff guide covers these anti-patterns. With business hours on, PepoChat's status line changes itself at the boundary, refreshing about once a minute while the widget is open.

Hiding the widget after hours looks tidy and removes the part of your support that works at night; the guide to 24/7 support without a night shift walks through the overnight routine instead.

How should an offline message sound for ecommerce, SaaS, clinics and agencies?

Match the message to what your visitors worry about at night: an order, a blocked account, a health question or a project. The three jobs stay the same; the details and the tone change.

Ecommerce

Shoppers after hours mostly ask where an order is, whether it will arrive in time and how returns work. Let the agent answer those first, including live order status if your store is connected (see chatbot order status for Shopify and WooCommerce). Save the person for refunds, damaged parcels and address changes, and keep the tone brisk. Example: "Refunds need a person, and the team is offline until 9:00 tomorrow, Dublin time. They'll see everything you've written here, so just leave your email and they'll reply by noon."

SaaS

Software customers are often mid-task and in another time zone. The agent can answer how-to questions from your documentation, while account changes, billing and bug reports need a person. Point to the status page during incidents, use the product's own terms, and promise in business days for a global audience. Example: "Billing changes need someone from our team, who are offline until Monday 9:00, Toronto time. Leave the email on your account and we'll reply within one business day."

Clinics and health practices

Clinics need two lines no other business does: the chat gives no medical advice, and emergencies go elsewhere. Do not ask for symptoms or health details in an offline message; ask only how to reach the visitor. With a connected calendar the agent can still book appointments at night, and after-hours phone calls are a separate problem, covered in the AI receptionist guide. Example: "The clinic is closed until 8:00 tomorrow. If this is an emergency, call your local emergency number now. For anything else, leave your email and reception will reply by 10:00." US practices covered by HIPAA should first read what a clinic chatbot may collect.

Agencies and consultancies

Agencies hear from two groups at night: clients, who expect their own contact, and prospects, who want to know whether a call is worth booking. Use first names, keep the tone warm, and give each group its own route. Example: "The studio is closed for the evening. Clients: your account manager will reply by 10:00 tomorrow, London time. New projects: leave your email and we'll send times for a call."

What to do next

Pick the three messages closest to your situations, cut each to the status and the reply time, and paste the one you use most into your away message. Ask for a person in a test chat to see the whole handoff, then decide who answers the morning queue. The customer service chatbot script examples show full conversations around the handoff, including an after-hours one, and you can create a free PepoChat workspace to set up Team availability and the test drawer without a credit card.