Start with time people can actually protect
Write each responder’s chat coverage blocks after meetings, fulfilment, breaks and existing support duties. An eight-hour workday is not eight hours of uninterrupted chat capacity. Include the time needed to read context and finish notes after the visitor leaves. If the team has no protected blocks, the first decision is whether to narrow the channel’s opening hours, not which software offers the largest simultaneous-chat setting.
Build an illustrative capacity line
Suppose two people each protect one hour and a complete conversation typically consumes ten minutes of attention, including follow-up. Dividing 120 available minutes by ten gives twelve conversation-equivalents before any buffer. This is deliberately simplified arithmetic, not a safe service limit. Arrivals cluster, questions differ and interruptions happen. Reserve some attention rather than scheduling to the theoretical maximum, and replace the fictional handling time with observations from your own pilot.
Separate concurrency from attention
A person can have several conversations open while waiting for replies, but that does not multiply their judgement or writing speed. A high concurrency setting may simply leave more customers waiting between messages. Test a small limit and inspect delayed responses before increasing it. Track the point at which answers become careless, handoffs lose context or other work is abandoned. That boundary matters more than the maximum number the interface permits.
Revisit the assumption after a busy session
Compare the worksheet with a short, representative coverage period. Record arrivals, unresolved work and the reason each conversation took longer than expected. Do not punish a responder for careful investigation by treating all long conversations as failure. Adjust coverage, scope or prepared information before adding more simultaneous work. Keep the worksheet as a planning aid with dated assumptions; it should make uncertainty visible rather than manufacture a staffing forecast from a handful of chats.
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