A customer cancelled, some time has passed, and you are sending the email that tries to win them back with a discount. You want them to reconsider, and the instinct that puts a glowing quote on every landing page whispers that it might help here too: remind them how much other people love the product, and maybe they will remember why they signed up. But a win-back email is aimed at the hardest audience you have — someone who used the product, formed a judgment, and decided to leave — and a stranger's applause is a strange thing to wave at a person who already made up their mind. Before you pair the discount with a five-star quote, it is worth asking whether that quote answers the reason they left or just talks over it.
Who is reading a win-back email
Here is the fact that shapes the decision: the reader already tried the product and chose to leave. They are not a prospect who has never seen it — they have an opinion, and that opinion was "not worth it for me right now." Something specific drove them out: it was too expensive, they did not get enough value, a competitor won, or their need went away. What is live for them is not "is this product any good in general" — they have a firsthand answer to that — it is "has anything changed that addresses why I left, and is this discount enough to make me look again." A win-back email that ignores that lived experience is talking past the only person in the room.
That framing changes what a testimonial can do. Social proof answers the question "should I trust a product I have never used," and your reader has used it. A quote from a happy stranger cannot overrule the reader's own memory of why the product did not work for them — and worse, it can feel dismissive, as if you are telling a departed customer they were simply wrong to leave. It is the same mismatch as dropping a warm testimonial into a re-engagement email to a dormant user, only sharper: this reader did not just go quiet, they actively quit, so generic praise lands as noise against a firsthand verdict.
The narrow case where it helps
There is a genuine exception, and it is specific: proof from someone who left for the reader's reason and came back because the thing that drove them out got fixed. If a customer churned over a missing feature or a rough workflow, and a short line shows another customer who left for the same reason, saw it addressed, and returned to a real result, that quote does serious work — because it speaks to the reader's actual objection, not to the product in the abstract. "I cancelled because the reporting was too limited; when they rebuilt it I came back, and now it saves my team a day a month" answers a departed customer in a way no generic praise can.
The pattern that works is objection-matched and change-anchored, not a general endorsement. It has to name the reason people like the reader left and show that reason is now different. This is the same discipline behind how a win-back conversation turns a returning customer's own story into proof: the evidence is powerful precisely because it comes from someone who walked the reader's exact path — out and then back — rather than from someone who never left.
Why it usually gets in the way
For most win-back emails, a generic testimonial backfires in two ways. The first is it ignores the reason they left. A departed customer left because of something concrete; answering that with "look how much everyone else loves us" is a non-response, and it reads as one. The discount is the only part of the email doing real work, and burying it next to praise the reader has already privately overruled just weakens the offer. Lead with what changed and what the discount is, not with a chorus the reader has reason to distrust.
The second is it can feel tone-deaf, even insulting. Telling someone who quit how wonderful the product is implies their decision to leave was a mistake — and the language patterns that make a testimonial sound staged make it land worse, because a skeptical ex-customer reads polish as spin. A win-back email needs to feel like an honest "we heard you, here is what is different," not like the same marketing that did not keep them the first time.
What to lead with instead
If your win-back email has room and you want it doing more, aim at the reader's real state — a former customer deciding whether anything has changed since they left. The highest-value elements are direct: a brief acknowledgment that they left, the specific thing that is now different (a new feature, a fixed workflow, a lower price), the discount stated plainly, and a frictionless path back in with their data intact. These serve the person asking "is it worth another look" far better than any amount of applause.
If you do use proof, make it the objection-matched, came-back kind described above — one short line from someone who left for the reader's reason and returned because it got fixed — placed alongside the change you are highlighting, never as a standalone brag. This is the same restraint as reserving one well-aimed testimonial for the onboarding moment where it actually helps: a single, precisely targeted piece of evidence supports the message instead of papering over it. One sentence from someone who walked back through the door beats a paragraph from someone who never doubted.
The rule of thumb
Ask what the reader is deciding. In a win-back email it is never "is this product any good" — they used it and left — it is "has the reason I left changed, and is this offer enough to make me try again." So the email needs an honest acknowledgment, a concrete statement of what is different, a clear discount, and an easy way back, not a stranger's endorsement of a product the reader already judged. Reserve proof for the one form that answers a departed customer: a short line from someone who left for the same reason and came back because it got fixed. Save the general praise for the audiences who have not yet formed a verdict of their own.