How Work Keeps Moving When Email Goes Down
In this fictional example, a customer calls to move a delivery from Tuesday to Thursday. The person who answers can take the call. Can they also reach dispatch, find out whether Thursday is open and get the new date back to the customer while the inbox is down?
On November 12, Microsoft reported that users had trouble connecting to Exchange Online mailboxes. Its updates said core Teams messaging and online meetings were largely functional during the broader incident, while some Exchange-dependent tasks, including meeting scheduling, could fail. Microsoft reported an earlier, separate Teams interruption that day. That distinction matters if you’re trying to keep work moving. Try the handoff in the existing chat and ask dispatch to confirm that the message arrived. Microsoft incident reports reproduced by Penn
Follow the request through the business
Take the delivery change as an example. The customer already has a number they can call. The person answering needs a place to hand off the request and a way to see whether dispatch picked it up. If the usual team chat works, put the order number, requested date and person responsible for the callback in one existing channel. Have dispatch reply there once it has checked the route. If the route is full, the caller can go back to the customer with a real choice instead of a promise someone else will have to unwind.
If chat is down too, use the phone route you’ve already agreed on. For a small team that might be the dispatch desk first, then the person covering it. Give the person who takes the request ownership of the callback until someone explicitly accepts it. A voicemail can leave a routine request pending. Whoever took the customer’s call still owns the callback until dispatch accepts the handoff. Confirm a new date only after dispatch checks the route. If today’s driver is already on the road, you need someone to answer and confirm what the driver should do.
Outside the company, the best channel may be different. Your staff might share a chat channel, but a supplier or customer may never see it. If your office phones run through the same internet connection as everything else, try the fallback from a phone on cellular service during a drill. A number is useful only if someone can dial it and someone else knows to answer.
Decide where the agreement goes
In ordinary work, the email thread often holds the history. During an outage, a chat message and two phone calls can leave different people with different versions of the same delivery date. If the order system works, have the person confirming the new date update it while the customer is still on the phone. If it’s unavailable, use one designated temporary log with access limited to the people handling the work. Record the order number, the confirmed delivery date, who confirmed it and whether the customer agreed. Copy the decision into the order record when it comes back and mark the temporary entry as transferred. That gives the next shift somewhere to look before it calls the customer or sends the truck.
The Department of Energy’s September 2026 communications drill asked participants to test alternate routes with their incident-response partners. A small business can borrow the test without borrowing the utility sector’s plan. Department of Energy drill guide
Run a fictional delivery change with email closed. Tell everyone it’s a drill and keep test changes out of live orders. When dispatch confirms Thursday, the person who took the call should be able to tell the customer the new date and show the next shift where it was recorded. If the date exists only in a voicemail or someone’s chat history, the next shift still has to figure out what to put on the truck.
No name or email needed. Select a rating to add details; click it again to clear it.