The practical process
Collect testimonials as a workflow, not a one-off favour.
The easiest system to maintain has a trigger, a clear request, one place to respond and a review step. You do not need to ask every customer. Start with people who have completed enough of the experience to describe it honestly.
Choose the right moment
Ask just after a real success: a completed project, useful support outcome, onboarding milestone, renewal or course completion. The details are still easy to recall.
Ask the right customer
Choose someone who has genuinely used the product or service. A warm comment is a signal to ask—not permission to publish the comment without checking.
Make submission easy
Give one obvious action: reply to the message or open a short collection form. Avoid making the customer create an account or choose among several destinations.
Ask useful questions
Use three to five prompts about their starting point, experience and outcome. Specific prompts produce more helpful detail than “What did you think?”
Get publication consent
Say where the testimonial may appear and ask for explicit permission. Treat a private support message as private until the customer agrees otherwise.
Review before publishing
Check that the quote is accurate, appropriate and supported by what the customer submitted. Do not improve it by adding claims or results they did not give you.
Publish strategically
Match the story to the page: onboarding feedback near signup information, service experience on the related service page, or a broader set on a Wall of Love.
Ask people with a real story, not simply the highest rating.
A useful testimonial helps another buyer understand context. Look for customers who reached a meaningful milestone, used an important feature, completed a project or can describe how your process felt.
Ask while the experience is fresh
- After a successful delivery or handover
- After onboarding or a support win
- After a customer renews voluntarily
- After a programme or course milestone
Do not force the timing
- Before the customer has used the product
- During an unresolved complaint
- When the outcome is still uncertain
- When the relationship makes refusal difficult
For wording by situation, use the guide to asking for a testimonial or adapt one of the request email templates.
Choose one collection channel for each request.
| Channel | Useful when | Watch for |
|---|---|---|
| Email reply | You already have a personal conversation. | Permission and customer details can become unclear. |
| Short form | You want consistent fields, questions and consent. | Keep it short enough to finish on mobile. |
| Direct message | The relationship normally lives in chat. | Move the final response into a consented workflow. |
| Interview | The customer has a detailed story but dislikes writing. | Send the edited wording back for approval. |
Each TestiFollow project has a shareable collection link with a rating, written testimonial field and publication consent. Submissions enter a Pending queue so nothing goes public automatically. See the collection workflow.
Consent and moderation protect both sides.
Tell the customer that their words, name, role, company and optional photo may be displayed publicly. Only request details you plan to use. If you substantially edit a quote for length or clarity, ask the customer to approve the final version.
- Keep the original submission.
- Do not publish private email addresses.
- Reject content that is irrelevant, abusive or cannot be used responsibly.
- Never create a testimonial on a customer’s behalf and present it as their unedited words.
Organise approved stories around buyer questions.
Use a simple Pending, Approved and Rejected workflow. Once approved, decide whether a story belongs in a focused Single widget, a browsable Grid, a compact Carousel or a dedicated Wall of Love. Avoid publishing every quote everywhere.
The goal is not the largest collection. It is a current, permission-based set of stories that helps visitors understand what working with you is like.