How an ISP communicates during a service outage determines whether subscribers remember the outage or remember how the ISP handled it. Most subscribers understand that infrastructure fails occasionally. They do not forgive being left in the dark while it does.

The communication failure pattern in most ISP outages is consistent: the NOC team is focused entirely on resolving the incident, nobody has time or clear ownership to communicate with subscribers, and by the time the service is restored, frustrated subscribers have generated a volume of inbound calls and complaints that take days to clear. Pre-defined communication procedures, with templates and clear ownership, solve this problem without adding significant workload during the incident itself.

The Communication Principles

Communicate early, before you know the cause. Subscribers who see a status update within 15 minutes of an outage starting are measurably less likely to call support than those who see nothing for an hour. The update does not need to contain the cause or the expected resolution time: "We are aware of a service disruption affecting customers in [area]. Our team is investigating and we will provide an update within 30 minutes" is sufficient and accurate.

Communicate on a schedule. If the first update says you will provide another within 30 minutes, the second update must appear within 30 minutes even if it only says "investigation is ongoing, next update in 30 minutes." Missed update commitments damage subscriber trust more than the outage itself.

Separate the corporate client communication from the mass subscriber communication. Corporate CIR clients with SLAs and technical contacts need direct outreach, specific information about their circuit's status, and regular updates from an account manager or senior operations contact, not a mass SMS. Having a separate communication track for corporate clients with direct contact information for each is an operational requirement if you have a CIR business.

Communication Channels

For mass subscriber notification: WhatsApp broadcast (the most effective channel for reaching Pakistani subscribers quickly), SMS to subscriber contact numbers (higher reach than WhatsApp for subscribers without smartphones), and a website status page or social media update for subscribers who check proactively.

The status page approach, where a simple web page shows current service status and incident history, is worth building once and maintaining. It reduces inbound call volume because subscribers can check status without calling support, and it creates a record of incidents and their resolution for operational and regulatory purposes.

For corporate clients: direct call or WhatsApp message to the primary technical contact, followed by email with more detail for the record.

Message Templates

Pre-written templates reduce the cognitive load of communication during an incident when attention is already stretched. The templates below cover the standard communication moments for a significant outage:

Initial notification (within 15 minutes of incident confirmation): "We are currently experiencing a service disruption affecting internet connectivity in [area/region]. Our operations team is actively working to resolve this. We will provide an update in 30 minutes. We apologize for the inconvenience."

Update template (every 30 minutes until resolution): "Update on the service disruption reported at [time]: [brief status update - investigation ongoing / root cause identified, working on resolution / service being restored to some customers]. Expected restoration: [time estimate if available, or 'under investigation']. Next update in 30 minutes."

Resolution notification: "Service has been restored as of [time]. The disruption was caused by [brief cause description] and affected [area/subscriber group] for approximately [duration]. We apologize for the impact and have taken steps to prevent a recurrence. Thank you for your patience."

For corporate clients, the initial notification should also include: which specific circuit is affected by name or circuit ID, the expected SLA impact, and the direct contact number for the senior operations contact handling the incident.

What Not to Say

Do not commit to resolution times you cannot keep. A "will be resolved in 30 minutes" that extends to two hours is more damaging than "currently unknown resolution time."

Do not explain technical details in subscriber-facing communications unless they are relevant. Subscribers do not need to know the BGP session was withdrawn: they need to know the internet is down and you are fixing it.

Do not go silent. A status update that says "no change, still working on it" is better than no update, because silence reads as abandonment.

For operators who want outage communication procedures documented as formal runbooks that can be executed by any team member during an incident, RunBook AI generates communication procedure documentation from the templates and process descriptions above. For the broader NOC design that positions the right team members to own communication during incidents, NOC Enablement & Monitoring covers the full operational structure.