Call Avalanche

A call avalanche is a sudden, massive spike in inbound calls - often many times normal volume within minutes - usually triggered by a power outage, storm, system failure or public incident that affects many customers at once.

What is a call avalanche?

A call avalanche - also called a call storm, call spike or call surge - happens when a single event makes a large share of your customers ring at once. In a contact centre that normally receives a few dozen calls an hour, a widespread power cut can bring thousands in the first hour. Queues that were empty a minute ago fill faster than agents can log in.

The term is used most in energy and utilities, where storms, earthquakes and network faults cut supply to whole regions, but any organisation can face one: a bank whose app goes down, a telco with a network outage, a retailer issuing a product recall, or a government agency announcing a new scheme.

Why call avalanches break normal contact centres

Contact centres are staffed to forecast. Workforce management tools and Erlang C models plan for expected volume, plus a margin. A call avalanche sits far outside that margin, so a few things happen at once:

  • Queues explode. Average speed of answer goes from seconds to an hour or more, and service level collapses.
  • Callers abandon and redial. High abandonment doesn’t reduce demand - frustrated customers ring back, so the same person may count as five or ten calls.
  • Phone lines saturate. Without enough capacity in the telephony layer, callers hear an engaged tone or the call drops before it ever reaches a queue.
  • Urgent calls get stuck. Most callers in an outage want the same thing: what’s happening and when will it be back on. But mixed into that queue are hazard calls about fallen lines and calls from medically dependent customers. If everyone waits in one queue, the calls that matter most wait longest.

The anatomy of an outage call avalanche

In a typical storm event, call volume follows a recognisable shape. There’s a near-vertical spike in the first 30 to 60 minutes as power goes off, a long plateau of status and restoration questions while crews work, and smaller secondary spikes whenever an estimated time of restoration changes or is missed. Each new update - on the website, by SMS or in the media - can trigger its own wave.

That shape matters, because most of the volume is repetitive and informational. The same handful of questions account for the bulk of calls, which makes them well suited to automation and proactive messaging.

How organisations manage a call avalanche

The most resilient approach combines several measures rather than relying on any one:

  1. Deflect what you can. Proactive outage notifications, outage maps and up-to-date IVR messages answer the question before the customer has to ring.
  2. Answer the rest instantly. An AI voice assistant can hold thousands of simultaneous conversations, give the latest information from your outage management system and log new faults.
  3. Add people fast. Surge capacity from a partner with already-trained, shared agents covers calls that need a human.
  4. Prioritise by risk. Route safety and vulnerable-customer calls to people first, using rules agreed before the event.
  5. Stay up yourself. A contact centre with home-based agents across many locations keeps running even when the storm hits its own city.

The organisations that cope best plan for the avalanche before it arrives. That means agreeing scripts, escalation rules and capacity in advance rather than improvising on the night.

How Telnet Helps

Where Telnet comes in

Call avalanches are the work Telnet was built for. We have answered New Zealand’s electricity fault lines for decades - for Vector since 1999 - and today handle fault calls for around three-quarters of New Zealand households.

We absorb an avalanche with three layers that switch on together:

  • Tulip, our AI voice assistant answers every call on the first ring with accurate outage updates and logs fault reports, at whatever volume arrives. During Cyclone Tam, Tulip handled 33% of all inbound calls with zero hold time.
  • Shared, trained agents move onto your lines within minutes through our blended resourcing model, instead of the weeks recruitment would take.
  • Your escalation rules send safety calls and vulnerable customers to a person first, so the urgent calls never wait behind the repeat ones.

Because you pay per interaction rather than per seat, this cover costs little in a quiet month and scales when the storm arrives.

FAQ

Call Avalanche FAQs

What causes a call avalanche?

Anything that affects a large number of customers at the same moment: a storm or earthquake that cuts power, a network or system outage, a billing error, a product recall, or a public announcement. Everyone affected picks up the phone within minutes of each other, so volume rises far faster than any roster can respond.

What's the difference between a call avalanche and a normal peak?

A normal peak, such as a Monday morning, is predictable and can be rostered for. A call avalanche is unplanned, arrives within minutes and can reach many times normal volume. Workforce planning can’t staff for it, so it has to be absorbed with automation, shared overflow capacity and proactive messaging.

How do you stop a call avalanche from overwhelming a contact centre?

Reduce the calls you can, and answer the rest instantly. Proactive outage notifications and IVR or website updates cut repeat calls; an AI voice assistant answers routine status questions at any volume; and a surge partner adds trained agents for the calls that need a person. Telnet combines all three - see our emergency and surge call centre.

Ready to scale?

Outsourced contact centre
for New Zealand & Australia.

30+ years. 100% onshore. The leading provider to the energy & utilities industry.

Get in Touch