You are auditing your lifecycle emails, deciding which ones deserve a testimonial, and you arrive at the dunning email — the message that tells a customer their payment failed and their card needs updating. There is room under the "update your payment method" button, and the same instinct that adds social proof to a landing page whispers that a glowing quote might keep this customer from churning. But the person reading a dunning email is not weighing whether to buy. They are a paying customer who just hit a snag, and they came to the inbox to fix a card, not to be sold. That gap is exactly where a well-meant testimonial goes wrong. Before you drop a quote under the retry button, it is worth asking what this customer actually needs from the email.
Who is reading a failed-payment email
Here is the fact that changes the decision: the person reading a dunning email has already chosen your product and wants to keep it — the failure is almost always mechanical, not a change of heart. Expired cards, hit limits, a bank fraud hold, a billing address that moved: the overwhelming majority of failed payments are logistics, not a customer reconsidering their loyalty. Their question is not "is this product any good," which they settled long ago; it is "what broke and how fast can I fix it." A testimonial answers a question this reader is not asking, and every second it delays the fix works against the one outcome you both want.
That mismatch is the core risk. A quote that reads "This tool transformed our workflow" is aimed at an evaluator with no experience. Your customer with the declined card has the experience, and dropping a marketing quote into a billing failure reframes a helpful "your card needs updating" note as a retention pitch. It signals that you see a payment hiccup as a churn threat to be talked out of, when the customer just needs a working link. The same misfire as the chirpy quote that grates in a renewal reminder: warm, true, and pointed at a decision the reader is not making.
The narrow case where it helps
There is one genuine exception, and it is not persuasion — it is reassurance for a customer on the final retry before cancellation. When a card has failed several times and the account is one step from being suspended, a wavering customer may quietly ask themselves whether reviving the subscription is worth the trouble. Here, a single result-anchored line can tip the effort-versus-value math: not "great software," but "teams that stay past their first year cut reporting time by roughly a third." That is proof aimed at the doubt a lapsing customer actually has — "is keeping this worth two minutes of updating a card" — rather than proof aimed at a stranger.
The pattern that works is result-anchored and reserved for the late dunning stage, not the first friendly retry. On the first email, the assumption is a simple mechanical failure, and proof only clutters the fix. By the third or fourth notice, when suspension is imminent, one short line about what long-term customers gain by staying reframes the update as protecting a result rather than repeating a chore. This is the same restraint as showing a single testimonial on a thank-you page: proof supports the moment without hijacking it.
Why it usually gets in the way
For most dunning emails — especially the first one or two — a testimonial fails in two ways. The first is friction against the only job that matters. A failed-payment email works when it is fast, clear, and single-purpose: your payment did not go through, here is the button to fix it, here is the deadline before service pauses. Every element that is not the fix competes with the button. A customer scanning for "how do I update my card" has to read past a stranger's praise to find the action, and a slower fix means more involuntary churn — the exact outcome the email exists to prevent.
The second is tone collision. A billing failure is a mildly stressful, transactional moment; the customer may already be slightly annoyed that something broke. A cheerful marketing quote in that context reads as tin-eared, as if the company is celebrating while the customer is locked out. It can even raise suspicion — a customer who feels sold-to during a payment problem may wonder whether the failure is being used as a hook. The language patterns that make a testimonial sound staged land worst on a reader who is mid-friction and just wants the problem gone.
What to put in the email instead
If your dunning email has room and you want it working harder, aim at the customer's real state — a loyal customer who hit a mechanical snag and wants it fixed fast. The highest-value elements are practical: a plain statement of what failed and why (card expired, payment declined), a prominent one-click path to update the payment method, the exact date service pauses if nothing changes, and a clear line to reach support if the card is fine and the charge still failed. These serve the person trying to fix a payment instead of the person who has never signed up.
If the account is deep into the retry sequence and genuinely at risk, make any proof their proof or a tightly outcome-anchored line — the same discipline behind a testimonial placed in a cancellation flow, where a single result-focused note can remind a leaving customer what they are giving up. One line, tied to the value of staying, never a full quote from someone the reader has never met, and never ahead of the update button.
The rule of thumb
Ask what the customer came to this email to do. On a failed-payment email the honest answer is "fix my card and keep my service running" — so an early dunning email needs a fast, frictionless update path and nothing that slows it down. Reserve borrowed proof for the one place it changes behavior: a short, result-anchored line on the final retry before suspension, sized so a customer who just wants to update a card barely notices it is there. Save the full stories for the pages where undecided prospects still live.