A forwarding rule is not a continuity plan until it has survived a test. FEMA continuity guidance uses a 12-hour maximum acceptable outage as a planning reference for essential functions. That is a government continuity concept, not a universal customer-service target; a plumbing emergency line, medical practice, and consulting office will choose different recovery objectives.

Start with the function, not the phone vendor

Define the essential outcome: callers can reach an informed person, urgent cases follow an approved route, and a recoverable record exists. Then map dependencies from the published number through carrier, PBX, internet connection, power, identity provider, CRM, notification channel, and destination staff.

A “redundant” softphone that uses the same building internet connection is not independent. Neither is a backup destination whose staff cannot see the current escalation roster.

Put units on continuity claims

Use two time measures:

  • Recovery time objective: maximum planned time to restore the phone function.
  • Recovery point objective: maximum tolerable loss of call records, messages, or configuration.

Add a service measure: percentage of test calls that reach the correct destination within the defined time. Report the number of attempts, locations, carriers, test window, and failure modes. Five successful internal calls do not prove performance across every external carrier.

A quarterly test sequence

  1. Obtain approval and notify affected staff; never simulate public emergencies.
  2. Place test calls from at least two external carriers.
  3. Disable or bypass one dependency at a time in a controlled manner.
  4. Confirm routing, greeting accuracy, message capture, urgent escalation, and restoration.
  5. Measure time from declared failure to successful alternate answer.
  6. Record every dependency that remained shared.

Exercise tabletop scenarios for loss of office power, internet, PBX administration, primary carrier, and CRM access. NIST SP 800-34 supplies a broader contingency-planning lifecycle, while CISA resources help organizations consider communications and cyber resilience.

Where external coverage helps—and where it does not

An answering service can provide a separate destination, people, and documented routing workflow. It cannot guarantee the originating carrier will deliver the call, repair the client's DNS or CRM, or replace emergency services. Preserve an alternate published channel and instruct staff how to update public status messages.

Review weekend emergency call patterns when setting test windows, and see the services overview for supported call handling.

The evidence limitation is important: public continuity guidance describes planning practices, not the probability that a particular business will remain reachable. Only controlled tests and incident records establish local performance.

FAQ

Does call forwarding prove redundancy?

No. The alternate route may share carriers, power, internet, administration, or data systems with the primary route.

How often should routing be tested?

Quarterly is a practical starting cadence, with an additional test after material carrier, PBX, roster, or script changes.

Should a test include a real emergency message?

No. Use clearly labeled test traffic and approved scenarios so the exercise cannot be confused with a public emergency.