Every product has a bad day. A region goes dark, a deploy corrupts a queue, an expired certificate takes down logins for four hours during someone's month-end close. You apologize, you fix it, you ship a postmortem — and then you move on, relieved that the churn you feared never came.
Here is what most teams miss in that relief: the customer who watched your product fail, felt the pain, and chose to stay is holding the single most persuasive story you will ever get. Anyone can praise a product that has never let them down. A customer who can say "they went down hard, and I still trust them" is vouching for the thing prospects are most afraid of — not whether your product works on a good day, but what happens on a bad one.
This guide is about capturing that story without being tone-deaf about it.
Why a survived outage is your strongest proof
Prospects don't actually believe your uptime number. They assume everything breaks eventually, so the real question in their head is: when it breaks, will these people handle it like adults? A testimonial from a customer who lived through an incident answers that question in a way no SLA page can.
The credibility comes from the tension in the story. "It's been flawless" is forgettable and slightly unbelievable. "They had a serious outage last spring, the CEO emailed me personally within the hour, and I got a straight explanation the next day — that's when I decided to expand our contract" is unforgettable, because it admits the flaw. The admission is what makes the rest believable.
So the goal is not to hide the outage from the testimonial. The goal is to let the customer describe how you behaved when it counted.
Step 1: Wait until the wound has closed
Timing is everything here, and the most common mistake is asking too soon. In the days right after an incident, the customer is still absorbing the operational cost — the cleanup, the internal questions from their own boss, the trust they had to rebuild with their team. Asking for a testimonial in that window reads as if you care more about your marketing than their recovery.
Wait for a clear signal that the relationship has moved past the incident:
- They renewed, expanded, or bought an add-on after the outage
- They referred you to someone, or spoke well of you in a QBR
- Enough time has passed that they've brought you a normal, unrelated request — a sign the incident is no longer top of mind
A renewal after an outage is the cleanest possible cue. It's the customer voting with their budget, and it gives you an honest, non-awkward reason to open the conversation.
Step 2: Open with the incident, not around it
When you do ask, name the outage directly. Trying to get an outage-survivor testimonial while pretending the outage never happened is both dishonest and obvious. Customers respect the opposite: a company willing to talk about its worst day out loud.
A message that works:
"You stuck with us through the March outage, which I know cost your team a real morning. The fact that you renewed after that means more to me than a dozen easy references. Would you be open to sharing, in your own words, how we handled it? I think other teams evaluating us are exactly the people who need to hear it."
Notice what this does. It acknowledges the cost to them, it credits their decision to stay, and it frames the testimonial as a service to other buyers rather than a favor to your marketing team. You're not asking them to forgive the outage — you're asking them to describe a decision they already made.
Step 3: Let them keep the honesty in
The instinct, once they agree, is to sand the incident out of the final quote so it reads clean. Resist it. If the customer's draft says "they had a rough outage but earned my trust back," leaving the first half in is what makes the second half land. A quote scrubbed down to "great reliability" from a customer who lived through an outage is not just weaker — it's a lie, and the customer knows it.
Guide them toward the specifics that carry weight:
- How fast you communicated — "I heard from them before I heard from my own team"
- How honest the explanation was — "they told me exactly what broke, no spin"
- What changed afterward — "they shipped the fix they promised in the postmortem"
- Why they stayed — the actual reason, in their words
These are the details a prospect who is scared of downtime will read three times.
Step 4: Get explicit approval on the incident reference
There's a real sensitivity here: a testimonial that names an outage also, by implication, says the customer experienced an outage. Some customers are fine with that; others don't want their own stakeholders reading that they bet on a vendor that went down. So make the approval unambiguous.
Send the exact wording back and ask plainly: "Are you comfortable with this being public, including the reference to the outage? I can soften or remove that part if you'd rather." Let them decide how much of the incident stays visible. A customer who opts to keep it in has given you something far stronger than a vague quote — genuine, on-the-record trust — and you have their explicit sign-off protecting both of you.
Storing that approval matters as much as the quote itself. Keep the request, the customer's exact words, and their yes together, so that if anyone ever questions whether the testimonial was authorized, the trail is right there. This is the same discipline that protects any published testimonial, and it matters double when the quote references a real incident. For more on that, see our guide on how to get a testimonial approved by a customer's legal team.
Step 5: Place it where the fear lives
An outage-survivor testimonial is wasted on a generic homepage carousel. Its power is specific, so put it where prospects are actively worried about reliability:
- On your status page or trust/reliability page, next to your uptime history
- In the part of a sales deck that addresses "what happens when something breaks"
- In renewal and expansion conversations with customers who have had their own rough patch with you
The customer who almost left and then didn't is a close cousin of this story — the emotional arc is the same. If you have those quotes too, they reinforce each other. Our guide on how to get a testimonial from a customer who almost churned then stayed covers that adjacent case, and the two together make a powerful "we don't run from hard moments" section.
The mindset that makes this work
The reason most companies never collect these testimonials is that they want to forget their outages, not memorialize them. That instinct is backwards. Your incidents already happened; the only choice is whether they become buried liabilities or public evidence that you handle failure well.
A customer who stayed with you through your worst day has already forgiven you. Asking them to say so out loud isn't reopening the wound — it's letting them turn a bad memory into something that helps the next buyer trust you faster. Handled with the timing and honesty above, it's one of the few marketing assets that gets more credible the worse the underlying story was.