Staff to your traffic, not a rule of thumb
There is no universal agent-to-visitor ratio worth copying, because it depends on your concurrency (how many chats one agent handles at once), your chat length, and how bursty your traffic is. Start from data you already have: when do conversations actually arrive, and how long do they run? Every other decision follows from that shape.
Concurrency is the real lever
One agent rarely handles one chat at a time. Simple, high-deflection questions might let an experienced agent run three or four concurrently; complex, emotional, or sales conversations demand one at a time. Set a concurrency cap you can actually sustain — the point where quality starts slipping is your ceiling, and pushing past it trades a visible metric (chats answered) for an invisible one (chats answered well).
Read your arrival curve
Pull a few weeks of chat timestamps and plot them by hour and weekday. Almost every team finds the same thing: demand clusters into a few peak bands, not an even line. You staff the peaks, not the average — an average headcount leaves the busy hours underwater and the quiet hours overstaffed.
Coverage windows and the handoff
- Define real hours. Decide the windows you will genuinely staff, and show them. A widget that looks live at 2 a.m. and answers nobody erodes trust faster than an honest "back at 9."
- Cover the seams. The riskiest minutes are shift changes and lunch. A visitor who waits through a handoff gap remembers the wait, not the reason.
- Plan the tail. Chats started five minutes before close still need finishing. Schedule a wind-down, not a hard cutoff.
When offline beats thin
One overwhelmed agent covering a twelve-hour window delivers worse service than a well-staffed six-hour window plus an honest offline form the rest of the time. If you cannot staff a period to your own quality bar, go offline for it deliberately: set expectations, capture the email, and promise a reply time you will hit. Underpromising and delivering beats a live badge over an empty chair.
Scale the schedule, not the anxiety
As volume grows, add coverage at the proven peaks first, lean on the AI layer and canned responses to lift each agent's sustainable concurrency, and re-plot the arrival curve every quarter — traffic shape drifts with seasons and marketing. In MyLiveChat you can watch the live queue and your own history to see where the pressure actually is before you hire against a guess.