The client heard about the outage before you called
The scenario:
A cloud provider you depend on goes down and your client's systems are affected. The client hears about it from their own staff complaining in a group chat before your team gets a notification email out. The outage was not your fault. Being the last to know about your own client's problem is what they remember.
Have a message ready to fire the moment you get confirmation, before the client has to ask first. The same applies to any dependency you don't control. Trust rises and falls on how fast you tell them about a problem, not on how fast you fix it.
The workflow:
Step 1 - Pre-draft the skeleton before you need it.
Ask your AI tool of choice to draft a fill-in-the-blank outage notice template now, covering what's affected, what you know, what you don't know yet, and when the next update comes. Writing this from scratch during an actual outage costs you the ten minutes that matter most.
-
Step 2 - Set the trigger to monitoring, not to a person remembering.
Wherever possible, tie your outage notice process to the same alert that tells your team something is down, so sending it does not depend on someone thinking to do it under pressure.
-
Step 3 - Draft the follow-up cadence in advance too.
Ask your AI tool to draft the update-every-thirty-minutes message and the all-clear message as templates now, so during a real outage your team is filling in blanks, not composing prose while also fixing the problem.