Live Chat Typing Indicators and Wait Messages: What to Show

Live chat typing indicators and wait messages are small details with a large effect on how a visitor judges your support. A chat that shows nothing for fifteen seconds feels broken, even if a good answer is on its way. A chat that says “typing” for two minutes feels dishonest. This guide explains what visitors should see while they wait, how long different waits feel, what to write in a wait message for a human and for an AI assistant, and how to avoid the signals that make a chat feel slower than it is.

Talkmio is an AI live chat. Its assistant, Mio, answers from your own content and hands the chat to your team when a person is needed, so a visitor can wait for either of them. Both cases need clear expectations, and both are mostly a matter of wording and rules rather than design.

Why Live Chat Typing Indicators Matter

A typing indicator is a promise: someone or something is working on your message. In a face-to-face conversation we get the same signal from posture and eye contact. In a chat window the only signals are the indicator, the timing and the words. When those are consistent, visitors relax and wait. When they are not, visitors repeat their message, open a second chat or leave.

The key is that the indicator must be true. An indicator that runs while nobody is looking at the chat is a small lie, and visitors notice it faster than most teams expect. If your system shows the indicator only when something is actually happening, it builds trust. If you can control the rule, tie it to real activity and stop it when the activity stops.

How Long Different Waits Feel

Research on response times, summarised by the Nielsen Norman Group in its article on response time limits, describes three thresholds: about a tenth of a second feels instant, about one second keeps the flow of thought and about ten seconds is the limit of attention. A chat is slower than a button click, but the same logic applies. The table below turns it into practical targets.

Wait	What visitors feel	What to show
Under 1 second	Instant	Nothing extra; show the message sent state
1 to 5 seconds	Normal for an AI answer	A typing indicator
5 to 15 seconds	Starting to doubt	Indicator plus a short line such as “Looking this up”
15 seconds to 2 minutes	Wondering if anyone is there	A clear message that a person is joining and roughly when
Over 2 minutes	Likely to leave	Offer e-mail follow-up, stop pretending to type

These numbers are guides, not laws. A visitor who is buying a product tolerates less waiting than one reading a help page, and a visitor who has already waited once tolerates even less.

What Visitors Should See While Mio Answers

An AI assistant answers quickly, usually within a few seconds, so a short typing indicator is all that is needed. The danger is the opposite: a fast answer that appears all at once can feel abrupt when the visitor expected a person. A short pause and a brief message that makes clear this is Mio keeps expectations honest. Our guide to naming your chat assistant explains why a clear name and a one-line description set the right tone.

If an answer takes longer because the question is complex, a wait message helps: “One moment, I am checking our pages.” Avoid fake delays. Adding an artificial pause to make an AI look human is not needed and tends to annoy people who notice. Keep answers short enough to read quickly, as our article on AI chatbot answer length recommends.

What Visitors Should See While a Person Is Coming

When Mio hands the conversation to your team, the wait changes character. A person may need a minute to open the Inbox, read the history and find the information. In Talkmio the conversation gets a “needs human” badge, your team gets a browser notification in the Inbox and, if nobody is online, an e-mail and a push notification on the mobile app. The visitor, meanwhile, sees only what you have written.

Write the hand-off message as a small contract: say that a person is joining, give a realistic time and tell the visitor what they can do meanwhile. “I am connecting you with a colleague. They usually reply within a few minutes. You can keep adding details here.” is better than “Please wait”. Avoid “Someone will be with you shortly”, because “shortly” means something different to everyone. If your first-reply target is five minutes, say five minutes. In Talkmio you set a response time target in Settings, and conversations without a first reply in that time get an “overdue” badge, which is a useful signal for your team. The article on first response time in live chat goes deeper into targets.

Wait Messages for Offline and Busy Hours

When nobody is online, the most important sentence is when the visitor will hear back. Talkmio lets you set business hours and offline texts per website. When the whole team is offline, visitors are asked for an e-mail address before their first message, and your later reply from the Inbox goes out as an e-mail. Write the offline text as a plain statement: “We are offline until 9:00 on Monday. Leave your e-mail and we will reply then.” Do not say “as soon as possible” if you mean Monday.

Busy periods need a different message. If a sale has doubled your volume, say so briefly: “We are busier than usual. Mio can answer most questions right now, and a person will join if needed.” Honesty about delay costs less goodwill than silence. For the planning side, see our guide to offline hours and shift planning.

Wording Examples You Can Adapt

Good wait messages are short, concrete and calm. Here are patterns that work across industries. For a quick lookup: “Let me check that for you.” For a hand-off: “I am passing this to a colleague who can see your order. They will reply here in about five minutes.” For an offline chat: “We are away until tomorrow morning. Leave your e-mail and we will answer there.” For a long wait: “Thanks for waiting. Everyone is busy, so we will e-mail you the answer if you prefer.”

Avoid emojis that suggest a person is typing when Mio is, avoid jokes about robots that hide the fact that the visitor can ask for a person, and avoid exclamation marks in the middle of a problem. The goal is to be clear. Our guide to live chat greeting messages collects tested opening lines.

Common Mistakes With Waiting

Most complaints about waiting trace back to a handful of avoidable mistakes. The first is the endless indicator: dots that keep moving after the agent has stopped writing, or that start when a visitor opens the chat window and nobody is there. The second is the silent hand-off, where Mio passes the chat to a person and the visitor sees no change, so they type the question again. The third is the unrealistic promise, such as “we reply instantly” on a page whose team is offline half the day.

The fourth mistake is a mismatch between channels. If your chat says you reply in five minutes but your e-mail channel takes a day, visitors who move from one to the other feel misled. Align the statements. The fifth is ignoring the visitor’s own wait: a form that takes a long time to submit, a page that loads slowly or a widget that opens late. A visitor who has already waited for the page is less patient with the chat.

A simple habit prevents most of these. Once a month, read ten conversations from start to finish and note every point where the visitor repeated themselves, asked “hello?” or left. Each of those moments marks a wait that was not explained. Fix the wording first, then the rules, and only then the design. The effort is small compared with the support you save when visitors stay in the chat instead of repeating their question three times.

Accessibility and Screen Readers

Visual cues are not enough. A typing indicator that only animates is invisible to someone using a screen reader, so a status update needs to be announced in text. The W3C explains this idea in its guidance on status messages: changes that matter should be exposed to assistive technology without moving focus. Check your own widget with a screen reader or ask your web team to confirm what it announces.

Also think about motion. Animated dots are harmless for most people but distracting for some, and a respectful design reduces or removes animation when the visitor has asked their device to limit it. Our guide to live chat widget accessibility lists the checks to run.

Test the Waits the Way a Visitor Experiences Them

The best test is to be the visitor. Open your site on a phone on a mobile connection, start a chat, and time what you see. Ask a question Mio can answer, one it cannot, and one that asks for a person. Do this at a busy hour and at night. Write down every moment when you were unsure whether anything was happening, and fix those moments first, usually by changing a message, not the system.

Use Try Mio in the Talkmio dashboard to check the answer and the time it took, and read Reports for first-reply time and busiest hours. Plans and limits are on the Talkmio pricing page. For the wider background on how chat messaging evolved, see the overview of instant messaging.

Frequently Asked Questions

Should a chat show a typing indicator for an AI assistant?

A short indicator is fine while an answer is being prepared, because it is true. Do not add artificial delays to make an AI look human. If an answer takes longer than a few seconds, add a short line saying what is happening.

How long is too long to wait in live chat?

Visitors start to doubt after about ten to fifteen seconds of silence and often leave after one or two minutes. Show a clear message when a person is coming, say roughly when, and offer an e-mail reply if the wait will be longer.

What should a wait message say when a person is joining?

Say that a person is joining, give a realistic time and tell the visitor what to do meanwhile. For example, say that a colleague will reply in about five minutes and that the visitor can keep adding details. Avoid vague words like shortly.

What should the offline message contain?

State when you are back and what happens next. In Talkmio the visitor is asked for an e-mail before the first message when the whole team is offline, and your reply from the Inbox goes out by e-mail. Say the day and time, not as soon as possible.

Is a typing indicator an accessibility problem?

Only if it is purely visual. Make sure status changes are also available as text to screen readers, as the WCAG status messages guidance describes, and reduce motion for visitors who have asked for it. Test the widget with assistive technology.

Where do I change the offline and welcome texts?

In Talkmio, open Websites, choose your site and edit the widget settings: colour, position, assistant name, welcome and offline texts, business hours and the pre-chat form. Changes apply within five minutes, so you can adjust wording after testing.

The Bottom Line

Live chat typing indicators and wait messages work when they are true, specific and consistent: a short indicator while Mio answers, a clear hand-off message when a person is coming and an honest offline text with a day and time. Test the waits on a phone, fix the moments of doubt and keep the wording calm. Start free with Talkmio, set your welcome and offline texts and try the chat as a visitor would before you announce it.