Skip to content
Chatbotscape
LiveChat's queue configuration article, Zendesk's article on the estimated wait time banner, Intercom's article on sharing expected response time and Microsoft's Dynamics 365 articles on queue position and average wait time were read on 12 November 2026. Settings, plans and wording change, so check each vendor's current documentation.
Chat queue· Support operations
A chat queue is the waiting line for new live chat or messaging conversations that no agent can take yet, usually because every available agent has reached their limit of chats at once. Many platforms can show the waiting visitor their place in line, an estimated wait, or both.
By Chatbotscape Editorial· Methodology· Published 13 November 2026· Updated 13 November 2026

Chat Queue — The Line Before an Agent Picks Up

Quick answer: A chat queue forms when a visitor asks for a person and nobody can take the chat yet. On most platforms that happens because each agent has a limit on how many chats they can hold at once, and every available agent is at it. The queue then holds the chat in order until a slot opens. What the visitor sees while waiting is a setting: a plain "please wait" message, their place in line, an estimated wait, or a bot that keeps helping in the meantime.

When a chat enters the queue

SituationWhat happensExample from vendor docs
Every available agent is at their chat limitNew chats wait in lineLiveChat: customers enter the queue when agents' chat limit has been reached
The team picks chats manuallyEvery new chat waits until someone takes itLiveChat's manual selection mode sends all chats to the queue
Nobody is online in the right teamDepends on the platform: queue, offline message or unassigned inboxZendesk does not show a wait estimate when the group or queue is offline
A bot is answering firstThe chat joins the queue only when the bot hands it to a personZendesk shows the wait banner once a ticket is assigned to a group or queue

The queue is a symptom of capacity, not a feature on its own. Raising chat limits empties it faster but stretches each agent across more conversations; adding people or answering more with a bot shortens it without that trade.

What the visitor can be shown

OptionWhat the visitor readsVendor example
Queue positionTheir place in lineLiveChat's editable queue message with a place-in-line placeholder; Microsoft's "People ahead of you" and "You're next in line"
Estimated waitA time or rangeLiveChat's approximate-minutes placeholder; Zendesk's range in minutes, hours or days
Typical reply timeHow fast the team usually answersIntercom's set or dynamic reply time
Nothing specificA generic hold messageAny platform with the options above turned off

Position is easy to compute and easy to trust. An estimate is more useful but can be wrong, which is why vendors hide it when they lack data.

How vendors estimate the wait

  • Zendesk. A statistical model combines historical waits for the customer's place in line with recent waits for the assigned group or queue, using the last 10 minutes, then the last two hours, then the last seven days, whichever has data. Estimates are shown only for groups or queues with at least one ticket routed in the last seven days. The banner refreshes every minute, shows a range, and changes to "An agent will be with you shortly" once an agent accepts. Zendesk lists it for Suite Team plans and up, with messaging turned on, and does not show it when the agent is the only online member of the group.
  • Intercom. The dynamic reply time is the median first reply time over the past 7 days, updated daily, and includes time spent with a bot. With fewer than 5 conversations in that period, customers see a generic "as soon as they can" style message instead. Teams using balanced assignment can show a live queue position instead of the estimate. See our Intercom review.
  • Microsoft Dynamics 365. Average wait time is an exponential moving average of past connected conversations in the queue, recalculated every 10 minutes; abandoned conversations are excluded. It appears only after at least 20 conversations and when the average is more than one minute. Queue position updates every 30 seconds while the position is under 150.
  • LiveChat. The queue message can include the visitor's place in line and the approximate minutes to wait. The article does not say how the minutes are calculated.

None of these pages publishes data on how much showing a position or estimate changes how many visitors stay.

Where chatbots fit

A bot changes the queue in two ways. Before the queue, it answers what it can and sends fewer chats to people, which shortens the line for everyone else; the handoff design guide explains why that effect grows as a desk gets busier. During the queue, it can tell the visitor what is happening, collect details so the agent does not have to ask again, offer an email follow-up, or answer a simple question while they wait. One limit to know: LiveChat states that bots cannot take chats from its queue. See human handoff and the after-hours chatbot for the case when nobody is coming.

How to tell if the queue is a problem

Watch three things: how long queued chats wait before an agent accepts (the human side of first response time), how many visitors leave while queued, and when in the day the queue builds. Long waits at fixed hours point at staffing. Long waits while agents report spare time point at chat limits or status settings. A queue that never forms but chats still feel slow points at agents answering slowly, not at the queue.

FAQ

What is a chat queue? The waiting line for chats no agent can take yet, usually because every available agent is at their limit of chats at once.

Why do customers end up in a chat queue? Because demand at that moment is higher than the number of open chat slots, or because the team picks chats manually.

Should I show customers their queue position or an estimated wait? Position is simple and reliable. An estimate is more helpful when it is accurate; Zendesk and Microsoft both hide theirs when they lack enough recent data. Many teams show position and add an estimate once they trust it.

How is the estimated wait time calculated? It differs by vendor. Zendesk uses recent historical waits for the queue and place in line, Intercom uses the median first reply time over 7 days, and Microsoft uses a moving average of past connected conversations.

What happens to a chat if the visitor leaves the queue? It depends on the platform. LiveChat moves a chat to its unassigned section if the visitor left after sending a message, and sends replies to the visitor's email.

Can a chatbot reduce chat queue times? Yes, by answering simple questions before the handoff and by collecting details while the visitor waits, so the agent's part takes less time.

Sources