Practical guide
Communicate service interruptions without creating more confusion
Customers value early, accurate information during an interruption. Poorly targeted or speculative updates can generate more support demand than silence.
Connect messages to verified incidents
An incident owner or operational system should determine when a disruption is confirmed, which customers are affected and when it is resolved. Messaging automation must not invent an estimated restoration time.
Use a stable incident reference so staff can connect replies with the correct event.
Target the affected audience
Select recipients using service area, route, product or account data rather than broadcasting every incident to every customer.
Prepare separate language for acknowledgement, progress and resolution. Send progress only when it adds useful information.
Design the support escape route
Customers may have a different issue that happens at the same time. Offer a way to report that their case does not match the notice.
Give agents the incident context so they can answer consistently and recognize genuine exceptions.