Outage-Proof IT and Phones for Burnaby's Storm Season

Every fall the same thing happens. A windstorm rolls in off the Strait, a tree drops onto a line, and half a strip mall goes dark right before lunch. The lights come back eventually. The question is what your business lost while they were off: calls, bookings, a day of files, or a customer who tried once and went elsewhere.

This is a practical plan for keeping your phones answered and your data safe through storm season. It covers where AI actually helps, and where it doesn't.

How bad do outages get here?

Worse than most people remember. BC Hydro says that "in 2024, over 1.4 million BC Hydro customers faced weather-related outages, the highest on record," in its 2025 storm season news release. The same release notes the utility tripled its vegetation clearing budget to $150 million because drought has weakened trees near power lines.

The good news is that most outages are short. In its August 31, 2026 storm season article, BC Hydro reports it restored power to 75% of affected customers in under 12 hours and 90% within 24 hours during the 2024 storm season. Read that the other way, though. One in ten affected customers waited more than a day. So a sensible plan assumes a few hours without power, and it doesn't fall apart if that stretches past 24.

What actually breaks when the power goes out

Most small offices in Burnaby and New Westminster now run their phones over the internet. That's cheaper and more flexible, but it has one big weakness. The CRTC's consumer notification template for VoIP providers is blunt about it: VoIP service "depends not only on your continued subscription (and payment) for the service, but also on Internet connectivity and power to function." It recommends keeping "an alternative phone service (such as a cellular telephone) handy."

BC Hydro's business outage checklist says the same thing from the utility side. It warns that "cordless phones and your company's phone system may not work without electricity" and tells you to contact your phone, security and fire system providers to find out how those systems behave during and after an outage.

Your modem, router, desk phones and phone system all need power. If any one of them goes dark, your main number either rings into nothing or sends people to a voicemail box nobody can check.

Cell networks are your backstop, and there's some protection there too. Under the federal Memorandum of Understanding on Telecommunications Reliability, in effect since September 9, 2022, twelve carriers, including Bell, Rogers, TELUS and Shaw/Freedom, agreed to provide emergency roaming "when technically feasible" during a major event. That roaming is capped at what a carrier can handle without materially hurting service to its own customers, so it's a safety net. Don't treat it as a guarantee.

Step 1: Put the answering layer somewhere that isn't your building

The single most useful change is to make sure your main number is answered in the cloud, not by a box in your back room. If the call routing lives with your carrier or a hosted voice platform, a dead office router doesn't stop the phone from being answered.

From there you have options, from cheap to capable:

• Simple forwarding. If your office line fails to connect, calls forward to a manager's cell. It costs almost nothing, and for a lot of small shops it's enough.
• A hosted auto attendant. A recorded greeting that tells callers you're affected by an outage, gives your hours, and takes a message.
• An AI receptionist. An AI voice agent running in a data centre can keep answering questions, booking appointments and taking detailed messages while your office is dark. When the power comes back, your staff work through a queue instead of a pile of missed calls.

Whatever you pick, build in a fallback. Twilio's Programmable Voice failover guide describes a fallback URL the platform calls if your main call handler errors out or can't be reached, and says that fallback "should point to a different availability zone, region, or even cloud provider." If neither responds, it says "an error is logged and a pre-recorded message is played back to the caller." That's the pattern to copy: AI first, a plain forward or recorded message second, never silence.

Step 2: Plan for the AI side having a bad day too

This is the part AI vendors don't advertise. The models behind AI receptionists are shared services, and they get busy. As of September 2026, Anthropic's Claude API errors documentation lists a 529 `overloaded_error` and warns that it "can occur when the API experiences high traffic across all users." The same page says its official SDKs retry transient failures twice by default.

Nothing about that is specific to storms, but it's a reminder that the AI layer is one more thing that can fail. A well-built setup treats the AI as the first option, not the only one. If it can't respond within a few seconds, the call should drop to a forward or a recorded message automatically.

Step 3: Protect the files, not just the phones

Power cuts are rough on hardware. BC Hydro's checklist recommends surge protection for sensitive equipment, knowing your UPS backup capacity "in minutes," and waiting 15 minutes after power returns before reconnecting non-essential equipment.

For data, the Canadian Centre for Cyber Security's Tips for backing up your information (ITSAP.40.002) recommends the 3-2-1 rule: "3 copies of your information (1 original and 2 backups), saved on 2 different media types, with 1 copy kept off site." It also recommends keeping one backup offline and regularly testing that you can actually restore from it.

Its companion guide, Developing your IT recovery plan (ITSAP.40.004), asks you to "identify and prioritize critical business functions, applications, and data," set a recovery time objective, and name who does what. It's also clear on one point: "Testing is critical."

A one-page storm plan

Here's an illustrative plan for a small Metro Vancouver office. Adjust it to fit yours.

1. Write down the path a call takes to reach you: carrier, router, phone system, handsets. Circle anything that needs wall power.
2. Move call routing to a hosted service and set up an after-hours or failure forward to at least two cell phones.
3. If you add an AI receptionist, give it a storm script (outage notice, hours, callback promise) and a non-AI fallback.
4. Put the modem and router on a UPS and time how many minutes it actually lasts.
5. Set up 3-2-1 backups with one offline copy, then do a test restore before November.
6. Print a contact list (BC Hydro, your IT support, carrier, key staff) and keep it somewhere you can reach without a computer.
7. After each outage, spend 15 minutes noting what broke and fix one thing.

Where this doesn't apply

This plan won't suit everyone, and it isn't a cure-all.

If you can't sell without the building, AI won't change that. A restaurant with no power can't cook. An AI receptionist can take reservations for tomorrow and tell people you're closed, which is useful, but it won't save the day's revenue.

Low call volume may not justify AI. If you get a handful of calls a day, forwarding to a cell phone does most of the job for close to nothing. Save the money.

Never route 911 through anything clever. The CRTC notice warns that VoIP 911 calls can fail during power or internet outages. Staff should call emergency services from a cell phone.

Cell service can fail too. Emergency roaming under the MOU depends on spare capacity. In a big regional event, towers lose power and networks get congested.

A UPS buys minutes, not a day. With 10% of affected customers waiting over 24 hours in 2024, battery backup covers short blips. It won't carry you through a long outage. Generators are a bigger, costlier decision that needs a qualified electrician.

AI tooling still has rough edges. Voice agents can mishear names and numbers on bad cell connections. Review transcripts after a storm rather than trusting every booking blindly.

Sources

1. BC Hydro. "La Niña, drought and storm readiness gap: Generational divide among British Columbians." News release, 2025. https://www.bchydro.com/news/press_centre/news_releases/2025/storm-season.html
2. BC Hydro. "Storm season is coming. Are you ready?" 2026. https://www.bchydro.com/news/conservation/2026/storm-season-is-coming.html
3. BC Hydro. "Prepare your business for a power outage" (checklist B16-337). Undated. https://www.bchydro.com/content/dam/BCHydro/customer-portal/documents/corporate/safety/power-outage-plan-for-businesses.pdf
4. Canadian Radio-television and Telecommunications Commission. "9-1-1 Obligations of Local VoIP Service Providers in Canada." Modified 2026. https://crtc.gc.ca/eng/phone/911/voip.htm
5. Innovation, Science and Economic Development Canada. "Memorandum of Understanding on Telecommunications Reliability." Modified 2025. https://ised-isde.canada.ca/site/ised/en/memorandum-understanding-telecommunications-reliability
6. Canadian Centre for Cyber Security. "Tips for backing up your information (ITSAP.40.002)." 2024. https://www.cyber.gc.ca/en/guidance/tips-backing-your-information-itsap40002
7. Canadian Centre for Cyber Security. "Developing your IT recovery plan (ITSAP.40.004)." 2026. https://www.cyber.gc.ca/en/guidance/developing-your-it-recovery-plan-itsap40004
8. Twilio. "Programmable Voice Failover Best Practices." Accessed 2026. https://www.twilio.com/docs/voice/twilio-voice-failover-best-practices
9. Anthropic. "Claude API errors." Accessed September 2026. https://platform.claude.com/docs/en/api/errors

Want a second pair of eyes on your storm plan? Autana Solutions is based in Burnaby and helps local businesses set up phone answering, including AI, that keeps working when the lights go out. Book a free call and we'll walk through your setup together.