Identify what actually failed
Check broadband, router power, Wi-Fi, mobile voice/data and business VoIP separately. Record the start time and provider status if available.
Separate internet failure from voice failure, move to an independent route, and make one clear channel the source of truth for staff and customers.
The exact technical response varies by business and incident. This sequence keeps the first decisions focused on people, the critical service and a deliberate fallback.
Check broadband, router power, Wi-Fi, mobile voice/data and business VoIP separately. Record the start time and provider status if available.
Use the pre-agreed alternate connection, mobile device, secondary provider or offline process. Give staff one contact route rather than creating competing messages.
Use cached/offline contacts and records. Publish a short customer update through any working channel and record work that must be reconciled later.
Pre-agreed thresholds reduce hesitation and stop a degraded situation from drifting without ownership.
Use an independent mobile or alternate voice route where available.
Avoid assuming two services on the same underlying network are resilient.
Choose one controlled channel and state when the next update is due.
Use the documented manual process and keep a reconciliation log.
Set a time threshold for relocation, reduced service or closure.
Use live provider, emergency-service and regulatory information during a real incident. GPN is the planning layer, not the authority controlling the incident.