Real-Time Capacity
Evaluates live agent count, active chats, and queue depth at the exact moment a visitor reaches this step. No stale data, no guessing.
The Queue Gate module checks real-time agent availability and queue depth before routing a visitor to live chat. If agents are free, the visitor is connected instantly. If the queue is full, the workflow offers intelligent alternatives — AI chat, callback requests, or self-service — instead of making visitors wait in a long queue.
The Queue Gate module is a real-time capacity check that sits between your visitor and the live chat handoff. Before attempting to connect a visitor to an agent, the Queue Gate evaluates two things: whether any agents are currently online and accepting chats, and how many conversations are already waiting in the queue. Based on these signals, it routes the visitor down one of two paths — "available" or "busy."
This is fundamentally different from a simple "online/offline" toggle. An agent can be online but already juggling five simultaneous chats. The Queue Gate knows this. It measures actual capacity — not just presence — so you can set thresholds like "route to live chat only if fewer than three visitors are already waiting." When the threshold is exceeded, the busy branch activates and the visitor is offered an alternative experience that still feels helpful rather than abandoned.
Without a Queue Gate, visitors are dumped into a queue and left watching a "waiting for agent" spinner that may take minutes — or never resolve. With it, you proactively manage expectations and provide alternatives. Studies consistently show that offering an immediate alternative (even AI-powered) produces higher customer satisfaction than a long queue wait, making the Queue Gate one of the most impactful modules you can add to any workflow.
Evaluates live agent count, active chats, and queue depth at the exact moment a visitor reaches this step. No stale data, no guessing.
Set maximum queue length or concurrent chats per agent. When the limit is hit, the busy branch activates and visitors get alternatives.
Route overflow visitors to AI chat, a callback request form, a self-service FAQ, or an offline message — whatever fits your support model.
Visitors who receive an immediate alternative instead of a queue wait are far less likely to leave your site. Protect conversions and satisfaction.
The Queue Gate is best placed immediately before a Human Chat handoff node. You've already qualified the visitor — perhaps through a greeting, data collection, and Time of Day check — and now you need to know whether an agent can actually take the chat right now. That's the Queue Gate's job.
Think of it as a bouncer at the door of your live chat room. If there's space, the visitor walks straight in. If not, they're politely redirected to an equally valuable experience. This keeps your live chat quality high (agents aren't overwhelmed) and your visitor experience smooth (nobody stares at a loading spinner).
A SaaS company uses the Queue Gate to manage surges during product launches and outages.
Queue Gates are most effective when configured thoughtfully. These tips will help you balance agent workload with visitor satisfaction.
Start with a conservative threshold (e.g., queue of 2–3) and adjust based on average handle time. A low threshold keeps wait times short; a higher one maximises agent utilisation.
When the busy branch activates, tell the visitor why. "Our team is experiencing high demand — let me help you with AI instead" is far better than a silent redirect.
Use a Time of Day module before the Queue Gate. There's no point checking agent capacity after hours when no one is logged in.
End the busy branch with a way for visitors to still reach a human — a callback form, email capture, or "try again later" message with your hours.
The Queue Gate evaluates two metrics: the number of agents currently online and accepting chats, and the number of visitors already waiting in the queue. You can configure a threshold on either or both. If the threshold is exceeded, the "busy" branch activates.
Yes. The Queue Gate queries live agent status at the exact moment the visitor reaches that step in the workflow. There is no caching or delay — the decision is based on current conditions.
Yes. You can place multiple Queue Gate modules in your workflow, each checking a different department or agent group. For example, your sales team might have a threshold of 2 while your support team allows up to 5 queued visitors.
The Queue Gate evaluates at the moment the visitor reaches it. If agents go offline later, the live chat handoff module handles that scenario separately. For maximum resilience, combine the Queue Gate with a Time of Day check to avoid sending visitors to an empty queue.
The Queue Gate works alongside these modules to create resilient, capacity-aware chat workflows.
Add a Queue Gate to your workflow and give every visitor an instant, helpful experience — whether an agent is free or not.