Disaster recovery answering: plan the phone outage path

01 / Continuity during a phone outage

Name the failure that the backup must handle.

Separate an unanswered desk phone from a local power failure, loss of office internet and a carrier incident. For each scenario, ask the carrier what it can detect, which route remains available and whether an administrator must act. Do not assume that a rule configured on a local device still runs after that device loses power.

AT&T Phone for Business documents Safe Call Forwarding for network outages or power outages when battery backup is exhausted. It lists that separately from busy and no-answer forwarding. The page was last updated December 7, 2022 and was reviewed here on October 22, 2026. Confirm availability and behavior for your own account rather than applying those conditions to another product.

02 / Continuity during a phone outage

Map the backup destination’s dependencies.

For a proposed answering destination, list how its staff receive calls and how your office receives their records. Then consider the dependencies shared with the failed site. A second handset at the same powerless office may not solve the intended problem. Ask the provider to describe which parts of its delivery depend on your office connection.

Keep phone coverage separate from field-service availability. During an outage, a receptionist may be able to collect a request while your staff cannot access the schedule. Prepare an approved temporary message that states the actual next step without confirming a visit, diagnosis or response time the team cannot support.

Separate three responsibilities in the plan: the carrier routes the published number during a supported fault; the answering provider maintains its own service under its applicable continuity terms; your business decides who can receive and act on requests. Ask the answering provider for its own incident communication, alternate delivery and restoration process. AT&T’s forwarding documentation does not establish that provider’s continuity or any disaster-recovery capability of Revo.

03 / Continuity during a phone outage

Prepare activation authority and a limited test.

Name a primary administrator and backup who are already authorized on the carrier and answering accounts. Record where approved instructions can be found without storing passwords in the runbook. Ask whether a routing change requires support, an online account or another channel that might be unavailable during the incident.

Agree a test window with the relevant providers and use consenting test callers. Prefer a provider-supported simulation over disconnecting live office equipment. Record whether the backup activated, which greeting played, whether the request arrived and who acknowledged it. The test should check the proposed failure path, not just a normal call to the backup number.

04 / Continuity during a phone outage

Define recovery and reconcile requests.

Before an incident, decide who authorizes a return to the normal route and what evidence that person needs. Ask the carrier whether restoration is automatic or manual and whether the backup settings remain configured afterward. Keep the temporary message accurate until the office can support its normal workflow.

After the route returns, make an inbound test and confirm that the intended greeting, mailbox and request delivery work. Reconcile requests captured during the interruption so a caller does not disappear between two inboxes or receive duplicate callbacks. Record unresolved requests, responsible staff and the next review time.