Talking through it
SaaS Outage Communication: What to Tell Customers in the First Hour, the Updates After, and the Note When It Ends
Your app went down at 10:12. By 10:20 there are forty support emails, three angry posts and a sales rep asking what to tell the big account. The software needs fixing. The silence needs fixing first, and it takes one person and one page.
November 21, 2026 · 9 min read
The short answer
To tell customers about a SaaS outage, post one short, true update in a single public place, usually a status page, within the first few minutes: what is affected, what still works, and when the next update will come. Keep that promise even when nothing has changed. When service returns, publish a plain post-incident note covering cause, impact and what changes, without guessing before you know.
On this page
- Customers write their own story when you say nothing
- The first hour: one page, one voice, one clock
- Why a status page beats answering four hundred emails
- Four updates you can draft today and fill in later
- Six phrases that make customers angrier
- The post-incident note customers actually read
- When the outage is in the software, not the message
Customers write their own story when you say nothing
An outage has two clocks. One measures how long the software is down. The other measures how long customers go without hearing from you, and that one does more damage. In the gap, they assume the worst, open tickets, tell colleagues, and start reading competitors' pricing pages. A short message at minute five costs nothing and buys patience the engineers will need by minute ninety.
The instinct of most founders is to wait until there is something to say. There is always something to say: we know, we are on it, here is what still works, here is when you hear from us next. The engineers do not need to stop working for this. Someone else writes it, and that person is named before the outage, not during it.
The outage is the engineers' problem. The silence is everyone else's.
The first hour: one page, one voice, one clock
Communication in an incident works best as a small, boring routine. Write it down now and tape it to the wall, because nobody invents a calm routine at 10:14 with the phones ringing.
- 1
Name the communicator
One person posts updates and answers the sales team. Not the engineer fixing the bug. Everyone else forwards questions to that person and says nothing in public on their own.
- 2
Post the first update within minutes
Three sentences: what is affected, what is not, when the next update comes. Do not wait to know the cause. "We are investigating" is a complete and honest first update.
- 3
Pick one public home
A status page if you have one; a banner in the app and a pinned post if you do not. Every email, ticket reply and social answer points there instead of retelling the story.
- 4
Set the next update time and keep it
Say "next update by 11:00" and post at 10:58 even if the news is "still working on it." A missed update time hurts more than a slow fix.
- 5
Brief the people with key accounts
Give account managers the same words that are public. Private versions drift, and customers compare notes.
- 6
Keep a timeline as you go
Times, symptoms, actions, who did what. It feeds the post-incident note and saves an argument later.
While the communicator handles the outside, the technical side follows its own order: status pages of the providers you depend on, recent deploys, logs, the database. Our web app down checklist covers that triage, and the cloud server outage page covers what to do when the failure belongs to your host.
Why a status page beats answering four hundred emails
Atlassian's documentation for its product Statuspage, read in November 2026, describes it as "a communication tool that helps you inform your users about outages and scheduled maintenance." Subscribers are "typically your customers, end-users, or employees," and "Email and text message notifications can be sent to your subscribers when you create and update incidents," per Atlassian's overview. Our reading, as general advice: you post once, and everyone who subscribed hears it, instead of your team answering each message by hand.

You do not need to invent the format. The companies your app probably depends on already publish theirs. Stripe's status page is titled "Stripe system status." Vercel's status page breaks the service into components such as Builds, Functions, CDN and DNS, shows 90-day uptime, and offers email, SMS, Slack, webhook and RSS subscriptions. Shopify's status page carries a line worth copying for its honesty: "Some issues affecting a small percentage of stores may not be reflected here."
| State | What it tells a customer | When we would use it |
|---|---|---|
| Available | Working normally | The default, and the all-clear |
| Service information | Something to know, nothing broken | Planned maintenance, a slow report, a known quirk |
| Service disruption | Part of it is broken or slow | Logins slow, exports failing, one region affected |
| Service outage | It is down | Nobody can use the core product |
Those four states come from Google's Search Status Dashboard, which reports Crawling, Indexing, Ranking and Serving that way. The wording is useful because it is dull. Nobody reads "service disruption" and thinks you are hiding something. A status page that lists components separately also stops one broken feature from sounding like a dead product.
Four updates you can draft today and fill in later
Draft these in calm weather and store them where the communicator can find them. In the moment, they fill in the blanks instead of composing prose while customers wait. These are our templates, not anyone's standard.
Investigating
"Some customers cannot [action] in [product] since [time]. [Feature] still works. We are investigating and will update by [time]." No cause, no guess, no apology paragraph yet.
Identified
"We found the cause: [plain description, one sentence]. We are fixing it now. [Workaround if any]. Next update by [time]." Name the cause only once you are sure of it.
Monitoring
"A fix is live and [action] is working again. We are watching closely. If you still see problems, reply here or [contact]." This stage stops people from refreshing angrily.
Resolved
"Service has been normal since [time]. We are sorry for the disruption. A summary of what happened and what we are changing will follow by [day]." Then actually send it.
Notice what the templates leave out: a fix time. Nobody knows how long a fix will take until it is done, and a broken estimate becomes the headline. Promise the time of the next update instead, and keep it. If payments are what broke, pair this with our payment processing emergency page, because customers who were charged need a more specific message than everyone else.
Six phrases that make customers angrier
- "A minor issue." It is not minor to the customer who cannot work. Describe the effect and let them judge the size.
- "Due to our provider." Customers bought from you. Name the provider in the post-incident note if it helps, but own the outage in the moment.
- "Should be fixed within the hour." Unless it is already fixed, any estimate is a guess dressed as a promise.
- "No data was affected." Say it only when you know it. If you do not know yet, say you are checking and will tell them.
- "We apologize for any inconvenience." The word any suggests you did not notice how much. Say what broke and that you are sorry for it.
- Silence after "resolved." The post-incident note is where trust is rebuilt. Skipping it tells customers this will happen again.
The post-incident note customers actually read
The final note is short, specific and signed by the company, not a faceless system. Send it within a few days, while people still remember the outage and before rumor writes it for you. A good one fits on a phone screen and answers the five questions customers ask each other.
Put in the note
- When it started and ended, in your customers' time zone
- What customers could not do, in their words
- The cause in one plain paragraph, no jargon
- What you have changed, and what you will change next
- Any credit you are offering, and how to get it
Leave out
- Names of staff who made the mistake
- Blame on a vendor as the whole explanation
- Promises that it will never happen again
- A wall of internal metrics
- Anything your attorney has asked you not to say yet
If your contracts promise uptime, check what remedy they give before you write. Big providers handle this with service credits. Amazon's EC2 agreement, for example, remedies a missed uptime commitment with credits on the bill, which in our reading is not payment for lost business. Read your own terms with the same care. Offering a credit unprompted, when terms allow, can settle the angriest accounts faster than any wording.
When the outage is in the software, not the message
Good communication buys time. It does not fix the app. If your team cannot find the cause, the developer who built the product is unavailable, or the same outage keeps returning every few weeks, that is the call to make. We respond the same business day (hours on our contact page). Repairs to SaaS products, web apps and their integrations are from $575, depending on complexity, with a written estimate before work starts; our emergency pricing page explains what moves the number. Connections to APIs and integrations are restored the same day once we have access.
We will also tell you when not to hire us. If the provider is at fault and the status page is doing its job, the honest advice is to wait and keep updating. The full offer lives on our emergency software repair page. Products that keep falling over may need deeper work under web app development, and founders without a technical lead often start with a fractional CTO. If the database is the casualty, read the database emergency page before anyone restores anything. Our notes for SaaS companies, the emergency repair hub, our published work and who we are round out the picture. DataCram is in San Antonio, building for the web since 1999; call (210) 346-0848.
Questions owners ask in an emergency
As soon as you know customers are affected. The first update does not need a cause: say what is affected, what still works and when the next update will come. Waiting until you understand the problem leaves customers to guess, and their guesses arrive in your support inbox and on social media.
Email works for a small customer list, but a status page lets you post once while subscribers get the update by email or text. Atlassian describes its Statuspage product as a tool to inform users about outages and scheduled maintenance. Stripe, Vercel and Shopify all run public status pages you can study before setting up your own.
Not until the fix is in hand. An estimate that slips becomes the story. Promise the time of your next update instead and keep it, even when the update is that you are still working. Once a fix is live and holding, say so and move to monitoring.
When the outage started and ended, what customers could not do, the cause in plain words, what you changed and will change, and any credit you are offering. Keep it short enough to read on a phone. Leave out staff names, vendor blame as the whole story and promises it will never happen again.
Then it is a breach response first. Involve your attorney and insurer before describing the cause publicly, contact law enforcement where relevant, and follow the notification rules that apply to you, which differ by state. Our data breach page covers the first hours. This is not legal advice.
Yes. We respond the same business day and work on the software while your team runs communication. Repairs are from $575, depending on complexity, with a written estimate before work starts. If the fault is your provider's and waiting is the right call, we will tell you that instead of selling you work.
Keep reading
- The website offerEmergency Website Repair: Who to Call When the Site Is Down, and What Happens After You DoWebsite down and no one to call? A same-business-day reply, fixed WordPress repair prices, from $575 for other platforms, and the checks before we sign off.
- The software offerEmergency Software Repair: Triage, Containment and a Written Root Cause for Broken Custom SoftwareCustom software or a web app broken today? Triage, stop the damage, restore, find the root cause, and a written estimate first. From $575, depending on scope.
- The mobile offerEmergency App Repair: An iOS and Android Developer for Crashes, Store Trouble and Expired CertificatesApp crashing, rejected or pulled from the store? Crash triage, store fixes, certificates and the access we need, from $575 with a written estimate first.
- Broken by an updateApp Not Working After an iOS Update: Prove the Cause, Rebuild With Current Tools, Ship the RepairAn iOS update broke your app overnight. Prove the update is the cause, read crashes by iOS version, rebuild with current tools and test on the new release.
- The bill that took email tooDomain Expired or DNS Broken: Getting the Website and Email Back TodayYour domain expired or DNS broke, and the website and email went with it. ICANN's renewal and redemption rules, MX basics, and who can log in to fix it.
- Undo now, investigate laterSoftware Update Broke Everything? Roll Back First, Then Find Out WhyA release broke production. Roll back to the last good version, check what a rollback cannot undo, then diagnose away from the live site. The first hour.
- Everything in Emergency RepairSee the section
From the Insights desk
- Next.js or PHP? The Better Question Is Who Patches Your SiteApache, NGINX and PHP all shipped urgent fixes between November 11 and 19, 2026. PHP is not the villain, and Next.js has patch days too. The real difference is who installs the fix, how fast, and how much of your site runs code at all.
- The Optimizely Hack Was Not an Outage. It Was a Delivery.On November 16, a flaw in Optimizely's sign-up flow let an attacker slip card skimmers, wallet swappers and iPhone exploits into the testing scripts of 178 organizations, the BBC and Zoom among them. How it happened, what it did, and the fixes, in order.
Get help with the outage behind the update
Tell us what is down, who is affected and what your team has tried. We reply the same business day with what we would check and a written estimate.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.