Chloe M.Google reviewOrder arrived damaged and nobody has replied to my email in three days.

Say something within 15 minutes, before you know the cause. Name what customers are seeing, say you are working on it, and give the time of the next update. Then keep that promise on a fixed rhythm, with the same words on every channel, until it is fixed. Afterwards, tell everyone it is over, say what they need to redo, explain how credits work, and publish a short account of what happened.
This is the communication playbook. For handling the flood of tickets itself, see how to handle a spike of support tickets during a SaaS outage.
Three public sources cover most of it, and they point the same way.
Speak before you understand. Google's SRE workbook says that unless you acknowledge an incident is happening and being addressed, people will assume nothing is being done. Atlassian's Statuspage guidance is to acknowledge quickly, summarise the known impact and promise further updates.
Fast first message, steady rhythm. PagerDuty's own incident guide has the first message posted within 5 minutes of the incident call starting, a second with the scope within 5 minutes of that, then updates at least every 20 minutes for the first two hours. Atlassian suggests every 30 minutes, or whatever suits the situation. Those are two vendors' practices. Neither is an industry benchmark.
One voice, separate from the fixers. Google's model has a communication role that is the public face of the response, while only the operations team changes the system. PagerDuty calls the person a customer liaison: they write the message, get the incident commander's approval, then send it.
Templates written in advance. Google recommends two or three ready-to-use templates.
No guesses. PagerDuty's rules for the liaison are "Never lie, and never guess" and "Don't estimate resolution times".
The principle that holds almost everywhere: for most software companies, what you owe customers during an outage is set by your contract, and the contract usually promises an uptime figure and a credit. It rarely promises a message. Regulated sectors are the exception. This section is general information and not legal advice. Check your own contracts and your own market.
What published SLAs look like. Two examples, as their pages read in November 2026.
| Google Workspace | Amazon EC2 (region level) | |
|---|---|---|
| Promise | 99.9% monthly uptime | 99.99% monthly uptime |
| Credit | 3, 7 or 15 days of service, by how far uptime falls | 10%, 30% or 100% service credit, by how far uptime falls |
| How to get it | Support case within 30 days of becoming eligible, or the credit is forfeited | Support case received by the end of the second billing cycle after the incident |
| Limit | Capped at 15 days a month. Sole and exclusive remedy under the SLA | Sole and exclusive remedy, unless the agreement says otherwise |
The pattern to notice: uptime is measured over a month, the customer has to claim, there is a deadline, and the credit is the only remedy the SLA gives. Read yours before the next incident.
Where a rule adds a duty.
If you sell to firms like these, expect your contract with them to pass some of that clock down to you. If personal data is exposed, a separate set of deadlines starts. The market table for that is in the ticket spike post.
Every time in this guide is a suggested starting point, not a benchmark. Adjust to your product and team size.
At a five-person company the incident lead and the communicator may be the same founder. Write the message, then go back to the fix.
| Stage | Suggested timing | What the message carries |
|---|---|---|
| Acknowledge | Within 15 minutes of declaring | Symptom, "investigating", next update time |
| Scope | Within 30 minutes | Who and what is affected, what still works, any workaround |
| Updates | Every 30 minutes for the first two hours | What changed, what was ruled out, next update time |
| Long incident | Hourly after two hours, said out loud | That the fix will take time, and the new rhythm |
| Resolved | When the incident lead confirms recovery | Time fixed, what to redo, whether data was lost |
| Follow-up | Within 5 working days | What happened, what changes, how to claim credits |
Post whenever the impact changes, whatever the clock says. And avoid empty updates. PagerDuty warns about notification fatigue from content-less updates. An update with no fix still needs one new fact, even if the fact is what you ruled out.
Atlassian's advice is consistent updates across all channels. The wording is shared. The jobs differ.
| Channel | Its job | Owner | Never |
|---|---|---|---|
| Status page | The single source of truth. Every other message links here | Communication lead | Leave it green while tickets pile up |
| In-app banner | Reach people who are in the product and confused | Product or engineering | Depend on it if the app itself is down |
| Social replies | One line and the status link, where people are asking | Support or social team | Explain causes or argue in threads |
| Start and end of serious incidents, and the follow-up note | Communication lead | Send every 30-minute update to the whole list | |
| Ticket replies | The approved wording, plus anything specific to that customer | Support agents | Improvise a cause or a fix time |
| Account calls | Customers with SLAs or large exposure | Account owner | Promise a credit before reading the contract |
Host the status page somewhere that does not share infrastructure with your product.
Say what you do know, in customer terms: the symptom, the scope, what you have ruled out and what you are trying next. As PagerDuty's guide puts it, customers don't care that application-server-123 is having issues, they care that they are not getting notifications.
The Microsoft 365 outage that began on 12 November 2026 shows the pattern at scale. Microsoft's first public post, at about 12:50pm US Eastern time, said only that it was "investigating reports of users experiencing issues accessing Exchange Online". Overnight it said its attempts to improve service were "not taking as expected". It first described the problem as limited to the Americas, then confirmed any region could be affected. On Friday it apologised and promised a full report once its assessment was done. Write "at least" in front of any scope you have not confirmed. Our lessons from the Microsoft 365 outage cover it in detail.
Three more rules for this stage:
Fill in the brackets. Times in UTC, or the time zone most of your customers use.
Acknowledge
We're investigating a problem with [feature]. Some customers are seeing [symptom in plain words]. We'll post the next update by [time].
Scope
[Feature] is failing for customers [on plan, in region, or "on all plans"]. [Other features] are working normally. [Workaround, or "There is no workaround yet."] Next update by [time].
Update with no fix
Still working on [feature]. We've ruled out [cause] and are now testing [next step]. No fix yet. Next update by [time].
Long incident
This is taking longer than we want. The fix needs [plain description], and we don't have a reliable finish time. We're moving to hourly updates. Next one by [time].
Resolved
[Feature] has been working again since [time]. Anything you [did] between [start] and [end] may need to be redone: [specific instruction]. No data was lost. [Or: what was lost.] We'll publish what happened by [date].
Follow-up email
On [date], [feature] was unavailable for [duration]. The cause was [one plain sentence]. We have [change already made] and will [change still to come] by [date]. If your plan includes an uptime commitment, here is how to claim a credit: [steps and deadline]. I'm sorry for the disruption. Reply to this email and it comes to me. [Name, role]
Hard case: a customer wants a fix time
I can't give you a time I'd trust, and I'd rather not guess and be wrong. What I can promise is an update by [time], on [status link] and here in this thread.
Decide three things before the incident ends.
Internally, Google's SRE book describes a postmortem as a written record of the incident, its impact, the actions taken, the root causes and the follow-up actions.
The customer version is shorter. Atlassian's Statuspage help reduces it to three parts: apologise, show you understand what happened, explain your remediation plan. In practice:
Leave out staff names, internal system names and anything you have not verified. Link the note from the status page incident and send it to everyone you tagged.
Relay pulls customer messages from connected channels (email, chat, WhatsApp, social posts, reviews and app store reviews) into one inbox, and drafts replies that a person approves and sends.
The limits, stated plainly. Each channel works only after you connect your own account or key. Drafts come from templates today. Nothing is sent automatically, so plan for approval time on a large incident. The companion listener's alerts on new negative mentions are basic today, crisis mode is switched on by hand, and an automatic volume-spike trigger is on the roadmap. Relay is not a status page tool. You will still need one.
If outage replies currently live in five tabs, talk to us. See also how Relay works.
Atlassian suggests every 30 minutes or whatever suits the situation, and PagerDuty uses at least every 20 minutes for the first two hours. Pick a rhythm you can keep, state the next update time in every message, and slow down openly if the incident runs long.
The status page first, then everything else links to it. Social replies should be one line and a link, because a thread is a poor place to keep a record. Email is for the start and end of serious incidents and for the follow-up note.
Say what customers are seeing, who is affected, what you have ruled out and when you will next update. PagerDuty's rule for its customer liaison is "Never lie, and never guess". A wrong guess gets quoted back for weeks.
Only what your contract and local law require, which depends on your SLA wording and on whether the customer is a consumer. Many published SLAs make the customer claim within a deadline, as Google Workspace and Amazon EC2 do. Take legal advice on larger claims.
No. Relay is the inbox for the messages customers send you, with drafted replies a person approves. Your team posts status updates in its own status tool.
GuidesIntroducing Relay: your online reputation in one placeWhat Relay is, the gap it was built for, what it does today, what it does not do yet, and who should choose something else.29 October 2026 · 6 min read
GuidesHow to do online reputation management, step by stepFind what people say about your business, answer it within the rules, fix what caused it. A plan, a triage table and replies you can copy.9 November 2026 · 11 min read
GuidesHow to automate customer support without trapping your customersWhat to automate, what to keep with a person, what the law says about AI disclosure, and how to tell whether automation is really working.9 November 2026 · 12 min readGet a personalised 30 minute demo on your own channels and policies. We show you Relay handling your real conversations, then set it up with you.
Brands we work with


