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

When tickets spike during an outage, stop answering them one by one. Declare an incident, name one person who speaks for it, publish one short update, and paste that same update into every channel on a fixed rhythm. Keep a list of everyone who wrote in, so each of them hears when it is fixed. Support's job in the first ten minutes is to tell engineering what customers are seeing and to stop the team writing twenty different explanations.
The published guidance is short and it agrees.
Declare early. Google's SRE workbook says to "declare incidents early and often", and that its experience is that managed incidents get resolved faster. Support is often in a position to make that call first, because customers report what monitoring has not caught. Agree in advance that support can raise one.
Split the roles. Google's model separates an incident commander, an operations lead and a communications lead. The communications lead is the public face, and only the operations team changes the system. PagerDuty's public playbook has a customer liaison who drafts customer messages, gets the commander's approval, and passes back how many customers are reporting the problem and what they see.
Write it down in one place. Google keeps a living incident document with the most important facts at the top. Support should read from that and nowhere else.
Prepare the words. Google suggests two or three ready-to-use templates. PagerDuty keeps a default first message for when the scope is still unknown.
Update on a rhythm. Atlassian's Statuspage guidance suggests updates every 30 minutes, or whatever suits the situation, and the same message on every channel.
Own it. The same page points out that customers may not care that another provider caused the problem. To them it is your service.
Don't estimate the fix. PagerDuty advises against giving resolution times, because a missed estimate frustrates people more than none. Give the time of the next update. That is a promise you can keep.
The principle that holds almost everywhere: an outage is mostly a matter of your contract, and consumer law sits underneath it where the customer is a consumer. A personal data incident is a separate track with its own clock, and it can start in the middle of an outage. Whether a given outage breaches anything depends on the facts. This is general information and not legal advice. Check the rules in your own market and read your own terms.
| Market | Service failure | If personal data is involved |
|---|---|---|
| US | We know of no general federal outage credit rule, so your contract and SLA do the work | Listed companies file Form 8-K Item 1.05 four business days after deciding a cyber incident is material. Other rules may apply, so take advice |
| UK | Services must be performed with reasonable care and skill for consumers | Notify the regulator within 72 hours where feasible, unless risk to people is unlikely |
| EU | Digital services have a minimum 2-year guarantee. If the supplier can't fix a fault in reasonable time, a consumer can ask for a price reduction or end the contract | 72 hours where notification is required. Availability incidents count as breaches, including ransomware and lost data with no backup |
| Australia | Consumer guarantees require due care and skill. Business buyers under A$100,000 can be covered | Assess a suspected breach within 30 days. Includes loss of personal information likely to lead to unauthorised access |
| India | Check local advice for your contract type | CERT-In directions require listed cyber incidents, including denial of service attacks, to be reported within 6 hours of noticing |
| Canada | Check local advice for your contract type | Notify individuals as soon as feasible once you determine a real risk of significant harm, which also triggers a report to the regulator |
| Singapore | Check local advice for your contract type | Notify the PDPC within 3 calendar days of determining a breach is notifiable, after an assessment within 30 days |
Support does not decide any of this. Support's job is to notice the words "I can see someone else's data" and escalate at once. Decide before the incident who that goes to.
Service credits. Read your own SLA before someone asks. A common shape is that of Google Workspace: 99.9% monthly uptime, credits of 3, 7 or 15 days depending on how far it falls, a support case within 30 days or the credit is lost, and credits as the sole remedy under the SLA. If your contract requires customers to claim, say so in the closing message. Hiding it just produces a second wave of tickets.
| Situation | Owner | First move | Never |
|---|---|---|---|
| Several tickets, same symptom | Support lead | Raise an incident, give engineering the count and samples | Wait for a dashboard to agree |
| Confirmed outage | Communications lead | Post first update, share the macro | Let each agent describe it in their own words |
| Partial, some customers only | Communications lead | Say who is affected and who isn't | Report "all systems normal" for the rest without checking |
| Someone sees another customer's data | Security and legal | Escalate at once, preserve the message | Discuss it in a public reply or call it a glitch |
| Enterprise customer with an SLA | Account owner | Personal note, link to the status page | Promise a credit before checking the contract |
| Public post | Support | Short reply, status link | Argue about whether it was "really down" |
| Customer's own problem during an outage | Support | Check it against the incident first | Paste the outage macro without reading |
Fill in the brackets. Use the same wording in every channel.
Status update, first
We're investigating a problem with invoice PDF exports. Exports may come out blank or fail to load. Other features are working. Next update by 2:45pm UTC.
First reply to a customer
Hi Daniel, you're not doing anything wrong. Invoice PDF exports are failing for a number of customers and we're working on it. You don't need to do anything or send more details. I've added you to the list and you'll hear from us as soon as it's fixed.
Public reply
It's on us, and we're working on it. Live updates here: [status link]. Nothing you need to do on your side.
Update when there is no news
Still working on invoice PDF exports. We've ruled out the template service and we're looking at the file store. No fix yet. Next update by 3:15pm UTC.
Closing reply
Hi Daniel, exports are working again as of 4:02pm UTC. Anything you exported between 2:04pm and 4:02pm may be blank, so please export those again. We'll publish what happened by Friday. Sorry for the lost afternoon, particularly with a client waiting.
Hard case: asking for compensation
Hi Daniel, I understand. Under your plan, service credits apply when monthly uptime falls below the level in our SLA, and we'll know that figure at month end. If it applies, I'll put the credit through and tell you the amount. I can't promise one today, but I will come back to you on 3 December either way.
Hard case: the customer's problem isn't the outage
Hi Mei, we do have an export problem today, but your error looks different. It's a permissions message, and the export issue doesn't produce one. Can you check whether your role changed recently? If it's not that, send me the time it happened and I'll look at it myself.
These times are a suggested starting point. They are not a benchmark, so adjust to your product.
Before anything breaks
During
After
It is working when customers quote your status page back to you and fewer people ask whether it is just them.
This is an example scenario. The product, people and messages are made up to show how Relay works. It is not a customer story.
Ledgerly is an invoicing tool. Around 2pm UTC its PDF exports start failing.
Daniel Okafor emails: "Every invoice export gives me a blank PDF since about 2pm. I have a client waiting." Mei Lin posts on X: "@ledgerly exports are broken again? Getting a spinning wheel then nothing." A Reddit thread asks: "Is anyone else's Ledgerly export dead today or is it just me?" Arjun Mehta emails: "Export button does nothing. Is this a known issue?"
Four messages, three channels, one outage. Those messages are grouped as one theme, invoice export failing. Export complaints normally come once or twice a day, so a dozen inside fifteen minutes crosses the alert threshold and the alert goes to the team's Slack channel with the count, the channels and samples. The owner of exports picks it up with a clock running.
The team writes one update. Each customer gets a reply built from it on the channel they used, and an agent approves each one. The X post gets a short public reply. When the fix ships, every message in the theme is still linked, so the closing note goes to the whole list.
The shared inbox, tagging, theme grouping, crisis alerts with learned baselines, Slack and signed webhook alerts, routing, SLA clocks, the war room view, drafted replies that a person approves and reopen rate reporting run in Relay today. Gmail and Outlook connect once you add an access token, public replies on X and Reddit need each channel's token, and email alerts work once an email sending key is added.
Status page updates and Jira, Linear and GitHub sync are on the way. Until then, the team posts the status update and files the incident in its own tools. If you hear about outages from angry customers first, contact us. For the reply side of a public pile on, see how to do online reputation management. For bug reports that arrive without an outage, see duplicate bug reports.
Atlassian's guidance suggests every 30 minutes or whatever suits the situation. The promise that matters is the time of the next update, so make it one you can keep. Post at that time even if the news is that nothing has changed.
PagerDuty's playbook advises against it, because unmet estimates frustrate customers. Say what you are doing and when you will next update. Give a time only when the fix is already rolling out.
One named person, separate from the people fixing the problem. Google's model calls this the communications lead, and PagerDuty calls it the customer liaison. Have the incident lead approve each message before it goes out, as things can change while you draft.
It depends on your contract, your SLA and the local law where the customer is a consumer. Read the SLA before an incident, including how a customer must claim. Take advice on larger losses.
Relay learns the usual volume for each theme and raises an alert only when a theme climbs well above it and stays there. A busy Monday lifts every theme a little. An outage lifts one theme a lot.
No. Relay drafts each reply from the update your team wrote, and a person approves it before it goes out. On a large outage, plan for that approval time.
SaaSHow to answer a SaaS customer who was charged twiceCheck whether it is a true duplicate, refund before the bank gets involved, give a reference number, and keep amounts out of public replies.8 November 2026 · 12 min read
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 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


