For communities
The praise is already in the channel
Somebody said the thing you needed, in #general, on a Tuesday. It is a private message in somebody's workspace, and it becomes a testimonial the moment you ask them.
No password. You get a private dashboard link right after this — bookmark it, that's your login.
Why it is hard here specifically
Community operators either never ask, or quietly screenshot a member's message and publish it. The second one is the reason members stop speaking freely.
What Kudobox does about it
Ask in the thread, publish after they answer
One line in the channel. The source is set to Slack or Discord, and the note stored beside it says the owner copied it with permission — never that consent was collected here.
Bubbles, because that is what it was
The layout that draws testimonials as a conversation, with faces beside them, is the honest shape for words that were said in a chat.
The faces, if they allow it
A row of members' photographs with a count, under the join button.
The questions worth asking
Copy these into your form and change them to sound like you. Each one is written to produce a sentence you could actually publish — which is the whole difference between a testimonial and a compliment.
- What made you join?
- What has this community given you that you did not expect?
- Who have you met here?
- What would you tell somebody deciding whether to join?
- What is it not?
Where to put them
The layouts that suit this trade. All twenty-three are on every plan, on as many pages as you like.
And what you already have
You are probably not starting empty. These are the places this trade usually finds its first ones.
The limit, said plainly
A message in a server is private by default. Every page here says the same thing: ask first, and keep the reply.
Other trades
Your customers already wrote the words
Send one link and their words arrive here instead — with the date, with the permission, and read for risk before you publish.
Everything it does