A live chat waiting message is the handful of sentences a customer sees between sending a question and getting the first human reply. Its job is to confirm that the message arrived, say honestly whether anyone is working right now, and point to what the customer can do if they would rather not wait. Without it, customers write a second time or close the tab.
It does not cover setting a target response time or deciding the order in which your team works. If you are still defining what your company promises, start with the guide to customer support SLAs. Below are the four elements of a good waiting message, templates for three situations and steps for checking your widget.
Four things customers want to know while they wait
Whatever the industry, someone waiting in chat asks the same questions. Did my message actually get through? Is anyone there? What happens now? What can I do instead of sitting in front of the screen? A good message answers all four before the customer asks them out loud or gives up.
Scroll the table sideways to see all columns.
| Customer question | What to show | What to avoid |
|---|---|---|
| Did my message arrive? | Delivery status and a case number, if you use one | Silence after clicking Send |
| Is anyone available? | Real team status and business hours | A green dot with nobody on duty |
| What happens next? | The channel and rough timing of the reply | A vague "we'll be in touch soon" |
| What can I do now? | A second route: phone, form, help article | A single path with no way out |
Confirming receipt is reassuring but not enough: the customer still does not know whether to wait five minutes or until tomorrow. Only all four elements together let the customer decide: stay, come back later or choose another channel.
Confirm receipt, but do not pretend it is a reply
In Meetlead, a sent message shows a sending state in the widget and then changes to sent or read. If the connection fails, the customer sees "Not sent" and can retry without retyping. When persistent tickets are enabled, the case number appears in the chat and in confirmations.
The first of Jakob Nielsen's usability heuristics states that a system should keep users informed about what is going on through appropriate feedback within reasonable time. Nielsen Norman Group. The article covers interfaces in general, not how long customers wait in chat.
An acknowledgment is not an answer to the question. A "thanks, we'll reply shortly" message removes uncertainty, but it should not imitate a conversation or contain a promise you cannot back up. We explain why it is left out of metrics in our article on first response time in chat. For the customer, it matters that the message is short and does not pretend to be a person.
Show availability that matches reality
The status in the chat header is a promise. If the widget says the team is available, the customer expects minutes, not hours. In Meetlead, an operator counts as available only when they have the panel open with an active connection and the current time falls within their schedule. When the last person disconnects, the widget switches to offline mode immediately, so the status does not stay green after hours.
Do not invent anything more precise than the status. If your tool does not show a queue position or a live estimated wait, keep "you are third in line" and "we'll reply in 2 minutes" out of your templates. It is safer to say during which hours the team replies in chat and where a message sent outside those hours will go. For longer absences, see our guide to customer contact during holidays and sick leave.
Shopify's customer service guide recommends showing support hours on your site and, for chat, saying when the team is back while offline. For email support, it suggests an automatic receipt confirmation with your hours and the approximate wait, and warns that a stated response time must be kept. Shopify. The article contains no data on how such messages change customer behavior.
Message templates for three situations
We wrote the texts below for a fictional bike accessories shop that answers chat on weekdays from 9 a.m. to 5 p.m. Adjust the hours and channels to your own business.
Tell us how we can help. We reply in this window, and the status in the chat header shows whether someone from the team is available right now. If you have your order number, add it straight away so we can check things faster.
I can see your question and I'm checking stock in the warehouse. This will take longer than a usual reply, typically up to fifteen minutes. I'll write here as soon as I know whether that model is available.
Nobody from our team is on chat right now. We reply on weekdays from 9 a.m. to 5 p.m. Leave a message with your email address and we will answer by noon on the next business day. For an urgent order issue, you can request a phone call.
The first template is fixed chat window copy and the third is offline copy; in Meetlead you set both in the widget builder, under Chat and Offline mode. The second is not automated; it is a short operator message for when a check takes time. Keep recurring wording like this as shared response templates instead of rewriting it each time.
An alternative instead of open-ended waiting
Not every customer wants to sit by the chat window. Your waiting message should therefore point to a second route that actually works at that moment. The simplest options are an after-hours message form, a callback request and a help article answering the most common question.
In Meetlead, the offline form appears when nobody is available, and you set its copy, including the response-time promise and the confirmation screen, in the widget builder. Callback requests require the Phone / Callback app to be active; the "as soon as possible" option works only while the team is available, and time slots come from the schedule. We explain when this channel makes sense in our guide to website callbacks. If you enable the Help tab in the widget, customers can look for an answer themselves before anyone replies.
Watch out for alternatives that do not exist. Sending people to a hotline that is closed at weekends or to an email address nobody checks is worse than an honest "we'll reply on Monday". List only channels someone actually staffs at the times you state. Templates for evenings and weekends, plus the order for working through replies the next morning, are in the guide to after-hours website enquiries.
How to check your own messages in five steps
Once a quarter, or after every change to your business hours, go through the steps below as a customer, ideally on a phone.
- Open the chat outside business hours.Check that you see offline mode rather than a green status. Read the header, the form description and the response-time promise.
- Send a message during business hours.See what the customer sees after clicking Send: the message state, the case number if you use one, and the empty-chat text shown before the question is sent.
- Compare promises with the schedule.Every hour and date in your copy must match the team schedule, including public holidays and vacations.
- Read every language version.If your widget runs in Polish, English and German, check each version. A change of hours in one language easily misses the others.
- Test the second contact route.Submit the offline form and, if you use callbacks, a phone request too. Make sure each request reaches the person who will handle it.
In the panel, the team sees how much time has passed since the first unanswered message and can sort conversations by longest wait. That is a tool for your side; show customers only what your team can actually keep. Our page on customer support in Meetlead shows how this works in practice. If waits grow because agents are running too many chats at once, set a concurrent chat limit from your own data.
Questions about waiting messages
Should I show customers an estimated wait time? Only if it rests on something your team really monitors, such as business hours and a next-business-day reply rule. A fixed number of minutes written into a template quickly drifts away from reality at peak times. It is safer to describe availability and the reply channel, and let the operator give a specific time in the conversation once they know the situation.
Should the message apologize when nobody is available? It does not have to. Customers need to know when they will get a reply and what to do in an urgent case, not several sentences of apology. For an ordinary after-hours message, it is better to state the day and time of the reply straight away.
