Somewhere in your community forum, a customer is answering another customer's question right now. Someone posted "has anyone gotten the reporting export to work reliably?" and a user you've never spoken to replied: "yeah, we've run it every Monday for eight months, zero issues — the trick is to filter before you export." That reply is one of the most valuable testimonials you will ever receive, and almost every company lets it scroll off the page unnoticed.
It's valuable for a reason marketing can't manufacture: the customer is talking to a peer, not to you. There is no sales relationship in the thread, no ask hanging over the exchange, no reason to be polite. One user asked a real question and another user, on their own time, chose to defend your product with a specific detail from eight months of real use. That's the exact dynamic a prospect trusts — and it happened without you in the room.
Why a forum answer beats a solicited quote
Most testimonials are solicited. You ask, the customer obliges, and both the prospect and the customer know it. That doesn't make solicited testimonials worthless, but it does mean a reader discounts them a little — the customer was asked, so of course they said something nice.
A forum answer carries none of that discount. The customer wasn't asked by you; they were asked by a peer who wanted the truth, because that peer was about to make the same decision. Praise offered in that context reads as evidence, not marketing. It's the difference between a reference a company hands you and a reference you find on your own by asking around. The second one is worth more precisely because the company didn't arrange it.
Forum answers are also unusually concrete. People answering a peer's question don't speak in adjectives — they speak in specifics, because specifics are what actually help. "We've run it every Monday for eight months, zero issues" is worth ten instances of "great product." The specificity is the credibility.
Watch the threads where customers help each other
The raw material lives in the parts of your community where users answer users: the questions channel, the "show and tell" threads, the replies under a feature announcement, the answer a power user leaves on someone else's support post. Set up a way to notice them. That can be as simple as a saved search for your product name in the forum, a Slack notification on the community's answers channel, or a weekly ten-minute skim by whoever owns community.
You're looking for a particular shape: a customer, unprompted, telling another person that your product works — with a detail attached. Not "+1" and not a bug complaint, but a genuine vouch. When you find one, capture the permalink and the exact wording immediately. Forum posts get edited and threads get archived; a testimonial you remember but can't link back to is one you can't actually use.
Ask the person who spoke up — separately and later
Here's the part teams get wrong: they see the forum answer and either paste it straight onto the website, or reply in the public thread with "love this, can we use it as a testimonial?" Both are mistakes.
Pasting it without asking takes a message the customer wrote for one peer and republishes it as marketing — a context they never agreed to. Even accurate quotes feel like a violation when they show up somewhere the author didn't expect. And replying in the public thread turns their generous, unguarded answer into an obvious marketing moment in front of the very peer they were helping, which sours the whole exchange.
So reach out privately, and let a little time pass. A short direct message: "I saw your answer to Priya in the forum about the Monday exports — that was genuinely helpful, thank you. Would you be comfortable if we used a version of it as a customer quote on our site? Happy to attribute it however you like, or keep it anonymous." Now the customer decides in private, feels appreciated rather than harvested, and the yes you get is one they'll stand behind.
Confirm the wording and the attribution before it goes live
A forum answer is written for a specific thread, so it often needs light editing to stand on its own — trimming the "@Priya" at the front, cutting the follow-up back-and-forth, tightening a run-on. That's fine, but the customer has to approve the edited version. Send them the exact quote as it will appear and get an explicit yes on both the words and how they're named: full name and company, role only, or anonymous.
Pay special attention to any number or specific claim they made. "Eight months, zero issues" is a strong line, but it's their claim, not yours — confirm they're comfortable seeing it in public and that it's still true when you publish. A detail that was accurate in a March forum post can quietly go stale by the time it's live on your homepage, and a testimonial the customer no longer stands behind is worse than no testimonial at all.
Close the loop with the customer who helped
One habit turns this from extraction into relationship: thank the customer for the answer itself, not just for the permission to quote it. The person who took time to help a stranger in your forum is exactly the advocate you want to keep. A genuine "that reply saved someone a real headache — thank you for jumping in" costs nothing and makes the next unprompted answer more likely.
Do this consistently and your community stops being a place you monitor and becomes a place your best proof is generated. Customers vouch for you to peers every week, in the concrete, unguarded language that converts. Your only job is to notice it, ask well, and publish the version they approved — turning peer-to-peer advocacy into evidence the next prospect can see.