When business email goes down, people still need to know whether to turn up, wait or use another way to reach you. Agree in advance where they should look, who will send the first update and who takes over if that person is unavailable. Then try sending and receiving a test update without signing in to the affected account.
Who needs to hear from you first?
Suppose a repair business loses its shared inbox while crews are heading to jobs. Staff need to know where to get schedule changes. Customers with appointments that morning need a direct answer about their visit. Other customers may only need to know where to check for an update. Each group can use a different route.
Staff
Use an approved call or text list if it reaches the people who need to act. Give the sender and deputy access to the current list outside the affected mailbox. Ask recipients who coordinate the next shift to confirm they received the message.
Customers with urgent work
Call the contacts you agreed to use for time-sensitive work. Keep the approved numbers somewhere the sender can reach during the outage. Check that the phone service can operate without the affected account.
Other customers
If many customers need the same information, give them a known public address for service updates. Put that address in places they already use, such as your support page or onboarding material, so they can find it when email is unavailable.
Give one person responsibility for sending updates and name a deputy who already has the permissions to take over. The Google SRE workbook on incident response describes how teams assign communications, prepare contact lists and practise with an agreed channel. A small business can use that idea without adopting a full incident management structure.
Could the backup fail with your email?
Trace the route from the sender to the recipient. Can the sender open the contact list, sign in to publish and complete any verification step? Can an employee or customer find and read the update without the affected mailbox or sign-in? A second app can have the same weak point if it uses your normal account. A public page can still depend on that account for publishing, or on the same service for delivering its email alerts.
Cloudflare documents a separate notification system for its own status page. It illustrates a separation you can ask about when choosing a route. Check your own publishing and delivery setup before relying on it. A short rehearsal with an existing phone list or status address may tell you more than buying another tool.
What should the first update say?
Give the confirmed impact, what the reader should do now and where and when they can expect the next update. Give a time you can meet. If you cannot estimate when email will return, give the time of the next check-in. Keep names, account details and customer information out of public messages.
A repair business might post: Our booking email is unavailable this morning. If you have a visit booked today and need to check the time, call the number on your booking confirmation. We’ll update this page at 11:00 local time. If you suspect someone has gained access to the system, follow your security response plan. The people permitted to send updates and the details they can share may differ.
Try it before the next outage
Write down who needs to hear first, the sender and deputy, where each audience should look, what each route depends on and who will give the next update. In a quiet test, ask the deputy to send a clearly labelled practice message to a small group without signing in to the normal email account. Have one person try from a staff device and another from outside the business. For a public page, use a test post that won’t alert customers. Record which parts worked, fix any route that still relies on the affected account and repeat that part of the test.
Review what your fallback depends on
We work on business email and infrastructure. Bring the routes you want to test and the accounts they rely on. We can discuss which dependencies to check first.
Discuss your email infrastructure
Questions about updates during an email outage
Can our status page use our normal company sign-in?
Check what happens when that sign-in is unavailable. If neither sender can publish, choose a route with a tested way to publish outside that account. Check separately that customers can open the update.
How will customers know where to look?
Share the status address or contact route before there is an outage. Use a place customers already know, such as a support page or their booking information. Give priority customers the contact agreed for time-sensitive work.
Who sends the update if the owner is unavailable?
Name a deputy in advance and make sure they can access the approved contact list and send or publish a message. During the rehearsal, have that person send the test update.