August 18, 2026
Flu Season and Other Call Surges: Phone Coverage That Scales
A clinic call volume surge — flu season, a school outbreak, the first Monday after a holiday closure — arrives faster than you can hire for it. Routing absorbs part of it. A call queue holds callers in order instead of dropping them, and any staff member can log into that queue from their own handset for an afternoon and log out at four.
Why does a surge break a front desk that works fine in June?
Because the failure is not linear. Volume rises maybe half again, but hold times rise much faster, and abandonment rises faster still.
The mechanism is ordinary queueing behavior. When arrivals approach the rate at which your staff can finish calls, waiting time climbs steeply rather than proportionally. Two people who comfortably handle June's traffic are not "slightly behind" in January — they are underwater, and the callers who hang up are disproportionately the ones with the least patience and the most urgent need.
Surge calls are not evenly distributed, either. They cluster in the first ninety minutes after the phones open, because people call when they wake up sick.
Ring group or call queue: which survives a surge?
A ring group is right for normal volume. A queue is right for a surge, and the difference is what happens to caller number four.
Ring group | Call queue | |
|---|---|---|
Caller arrives, all staff busy | Hears ringing, then voicemail or nothing | Waits in position with music on hold |
Order preserved | No | Yes, first in first out |
Staff join for one shift | Everyone in the group always rings | Agents log in and out by feature code |
You can see the backlog | No | Live queue status: who is logged in, who is waiting, how long |
Reporting | Answered or not | Abandons, wait time, per-agent counts |
Most clinics we set up run both: a ring group for the two front-desk phones during ordinary weeks, and a queue that the main number routes to during the season. Call groups and queue setup are separate objects, so you can build the queue in October and point the number at it in December.
For the general comparison outside a clinic context, see ring groups vs call queues.
How do you add temporary agents without adding phones?
Queue agents log in and out from any handset with a dialable feature code. Nobody needs a new phone, a new extension, or an administrator.
This is the part that makes a queue worth the setup. During a surge, the medical assistant with a lull between rooming patients, the billing coordinator, and the practice manager can all take queue calls from the phones already on their desks. They dial the agent login code, take calls for two hours, dial the logout code, and the queue stops offering them work. Their calls are attributed to them in reporting, so you can see afterward who actually carried the load.
Two rules make it hold up. Put login and logout on the shift checklist — an agent who forgets to log out rings a dead desk and inflates every wait-time number you have; the queue agents guide covers the pause and wrap-up states. And name a surge roster in advance, because deciding who backs up the front desk at 8:15am on the first bad Monday is a decision you want made in October.
What do you watch while the surge is happening?
Live queue status, and specifically three things: how many callers are waiting, how long the longest one has been holding, and how many agents are logged in.
That third number is the one that is usually wrong. A queue with nine callers waiting and two agents logged in is not a volume problem, it is a staffing-state problem, and it is fixable in thirty seconds by asking two more people to dial the login code.
Check it at the start of the morning block, not after the complaints arrive. Practice managers who keep the live view open on a second monitor during the season catch the 8:20am pileup while it is still a pileup rather than a voicemail backlog.
Which calls should not reach a person at all?
Move the predictable, low-judgment traffic off the queue before the season starts. Every call that does not need a human is a slot returned to the callers who do.
- Hours, address, and closure announcements belong in the auto attendant greeting, where a caller gets the answer in eight seconds without waiting.
- Billing and records get their own menu option pointing at their own voicemail boxes, returned in the afternoon lull.
- Prescription requests get a dedicated box whose greeting states exactly what the caller must say: patient name, date of birth, medication, pharmacy.
- After-hours and lunch are handled by time conditions, not by whoever remembers to change the greeting.
Keep the menu short anyway. Under load, a five-option menu costs you more calls than it diverts.
What do you do after the surge?
Read the queue report while the season is still fresh. Two figures matter: peak concurrent waiting by hour of day, which tells you how many agents the surge actually required, and abandon rate by wait time. If abandons cluster before twenty seconds, your greeting is too long or the menu is too deep; if they cluster after ninety seconds, you needed more agents logged in.
Weekly call reports arrive by email throughout the season, which is usually enough to notice the trend line turning up before the front desk tells you.
One note on the AI features: Signal's voicemail transcription and call summaries are off by default on every account, because they send audio and text to OpenAI and Anthropic and we do not hold a BAA with either. A practice handling PHI should leave them off pending that. None of the surge handling above depends on them.
Frequently asked questions
How do clinics handle seasonal call surges? By absorbing the peak in routing rather than headcount. Point the main number at a call queue so callers hold in order instead of hanging up, pre-designate a roster of staff who can log into the queue from their own handsets during the morning rush, and move hours, billing, and prescription traffic to auto attendant branches and voicemail boxes so it stops competing with appointment calls.
What is the difference between a ring group and a call queue during a surge? A ring group rings several phones at once and has nothing to offer the caller who arrives when everyone is busy. A queue holds that caller in position with music on hold, reports how long they waited, and lets staff join or leave the answering pool by dialing a feature code. Under load, the queue is the one that keeps callers.
Can staff take queue calls from any phone in the office? Yes. Queue agents log in and out with a dialable feature code from the handset in front of them, so a medical assistant or biller can pick up queue calls for two hours without any configuration change. Their answered calls are attributed to them in queue reporting, and logging out stops the queue from offering them further calls.
How do I see how bad the backlog is right now? Live queue status shows who is logged in, who is waiting, and how long each caller has been holding. It is a real-time view, which is what makes it useful — a nine-deep queue with two agents logged in is a problem you can fix during the morning it occurs rather than discover in a report the following week.
What should callers hear when the queue is full? Music on hold and a periodic position or comfort message, and after a wait threshold you choose, an overflow to voicemail with a greeting that states when you will call back. Silence is what makes people hang up. An overflow that promises a same-day callback and is honored is better than a queue that holds someone for six minutes.
Planning next season
The right time to build the surge queue is the quiet month before you need it. If you would like a second opinion on how your main line is configured before the season starts, we will walk through it with you and tell you what we would change.