Translate staffing into a queue rule
Choose a modest initial concurrency limit based on the responders’ work, not the maximum offered by the interface. A technical question with long reading time may need a different boundary from a short product clarification. Decide what should happen when everyone reaches that limit. The queue should make the wait visible and preserve a route to an asynchronous answer rather than silently converting overload into unanswered conversations.
Verify the available LiveChat controls
LiveChat’s documentation describes queuing when agent chat limits are reached and an option for manual pickup. Inspect the settings available in your current plan and workspace; do not infer their exact names or defaults from an old screenshot. Record whether work is assigned automatically or accepted manually. That difference changes who is responsible for noticing waiting visitors, so it belongs in the team’s operating instructions as well as the configuration.
Test a fictional full-capacity moment
Have the configured number of conversations occupy the available responder, then create another harmless visitor request. Observe the waiting message, the agent’s view and what happens when capacity becomes available. Repeat with the responder unavailable. Do not promise an estimated wait unless the implementation supports it reliably. Offer a clear alternative for a visitor who cannot remain on the page and verify where that message will be owned.
Review the queue after real operation begins
Look at waiting time, abandoned exchanges and the quality of active responses together. A shorter queue achieved by overloading everyone may be a worse service. If one repeated topic dominates arrivals, improve the relevant website information before increasing limits. Save the tested configuration and any change reason. This guide explains an operating method; it does not claim that a specific limit is safe for every team or that queue controls prevent all message loss.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LiveChat queue configuration — Merchant documentation · livechat.com · Merchant-controlled · checked 2026-09-19