Slack groups, forums and user groups
Collect Testimonials in Your Customer Community
Your customer community is full of people praising the product to each other. That is exactly why it feels wrong to screenshot a thread and put it on your homepage. A community runs on trust between members, and a clumsy ask can make every future post feel like marketing material. Use the checklist to ask in a way members welcome, then collect their words properly.
- Agreed with moderators before anyone posts
- Members opt in through a link, never a screenshot
- Thanks given back in the community
The problem, solved
Asking a community without spoiling it
Members are generous in a community because it is not a sales channel. Each fix keeps it that way.
Situation 1 of 5
The best praise is already in threads
A member wrote three glowing paragraphs to help a newcomer. They were talking to a peer, not agreeing to an advert.
How StoryProof solves it
Reply privately and ask whether they would say it again through your collection link, so the version you publish is one they chose to give.
Situation 2 of 5
Posting the ask feels like spam
A request dropped into the general channel competes with real questions and annoys the people you most want to hear from.
How StoryProof solves it
Share the link by hand in one agreed place, such as an announcements channel or a pinned forum post, and print it as a QR code for in person meetups.
Situation 3 of 5
Members use handles and inside jokes
A testimonial signed “devnull42” with a reference only regulars understand means nothing on a product page.
How StoryProof solves it
Nothing a member sends goes public until you approve it, so you can check the name and context with them first.
Situation 4 of 5
We cannot tell community quotes apart later
When someone asks where a quote came from, or a member leaves the group, nobody can find the ones collected there.
How StoryProof solves it
Tag each response with its source, such as the channel or the meetup city, so community testimonials stay findable.
Situation 5 of 5
Members never see what happened next
People who took part hear nothing, and the next ask lands on a group that feels used.
How StoryProof solves it
Every plan includes a Wall of Love with its own link, so you can share the finished page back with the community that made it.
Checklist
Before, during and after a community ask
Tick what is done. Open lines are the ones most likely to cost you goodwill.
Ticks stay in your browser only.
Prompts
Wording for each kind of space
The same ask reads differently in a chat channel, a forum and a room full of people.
Chat channel announcement
- “If the product has helped your work, we would love two minutes of your words for our site. Totally optional: {link}”
- “Questions about this? Reply here. Answers go through the link, not the thread.”
Leave out
- Tagging named members in the public post
- Reposting the ask every day
Private note to a member whose post stood out
- “Your reply to the onboarding question last week was brilliant. Would you be happy to say something like it for our website? If not, no problem at all.”
Leave out
- Pasting their post back and asking “can we use this?”
User group or meetup
- A slide or table card with the QR code, mentioned once at the end
- “Scan it later if you like; it takes two minutes.”
Leave out
- Filming people in the room without asking each one
In StoryProof
From community goodwill to published testimonials
- 1
Prepare the form and link
Set the form in the community’s language and copy its link and QR code.
- 2
Post once, in the agreed place
Use the checklist wording, and send private notes to authors of standout posts.
- 3
Approve and tag
Confirm names with each member, tag responses with the community source, then approve.
- 4
Give it back
Share the Wall of Love link in the community with a thank you to everyone who took part.
What happens next: Leave a few months before asking the same community again, and ask newer members first next time.
Before you start
What this does not cover
No community integrations
StoryProof does not connect to Slack, Discord or forum software, and it does not read or import posts. Members answer through the link.
No public posting for you
StoryProof does not post the ask in your community. A person does, in the agreed place.
Handles are not attributions
StoryProof records the name the member gives on the form. Confirm a real name or a description they are happy with before approving.
Community rules come first
If the group is run by members or another company, its rules decide whether a request is allowed at all.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can we use a community post as a testimonial?
Not without asking the author. They wrote it for other members. Ask them privately whether they would say it again for your site, through the link.
Should we offer members a reward?
It can make a community feel transactional. If you do, offer it for taking part, not for praise, and say so in the attribution where your rules require it.
What about a community that another company runs?
Ask its moderators first. Many independent groups ban vendor requests, and breaking that rule costs more than the testimonials are worth.
How do we stop the thread filling with answers?
Say in the post that answers go through the link, and reply to anyone who answers in the thread with the link and a thank you.
Still have a question? Ask the StoryProof team or book a demo.
Let your community speak for itself
Create a link members can choose to answer. No credit card needed to start.
Last updated 2026-11-12.