How to turn customer praise into testimonials

Sort praise into three piles: thanks, specific comments and quotable lines. Ask the sender for permission before you publish, and use their exact words with light edits only. Keep a praise log in internal notes so a useful quote is still there when you need it.

By · Last updated

Sort praise from testimonial material

Not all praise is quotable. "Great product, thanks!" is kind, but it tells a stranger nothing. "The checklist during setup showed me which step I had skipped, and I stopped guessing" is a testimonial waiting to be used. Read each praise item and sort it into one of three piles.

  • Thanks. Warm, general, short. Reply to it and move on.
  • Specific. Names a feature, a moment or a result in the customer's own words. Worth a follow-up.
  • Quotable. Specific and clear enough to stand alone on a page without context.

Most praise lands in the first pile. The second and third piles are where the testimonial work starts, and they are usually smaller than you expect.

Ask permission before you publish a word

Praise written to you is not a testimonial until the person agrees to share it. Ask first, in a short message from your own email. Name the line you want to use, say where it would appear and offer to show them the final wording.

Hi Ana, your note about the setup checklist made my week, thank you. Would you be comfortable with us quoting the line about skipping a step? We would use it on our pricing page with your first name and the name of your company, and I can send you the final text before it goes live.

Some people prefer to stay anonymous. Respect that. A quote with a role and a company, such as "product manager at a logistics company", can work just as well without a name.

Edit lightly and keep the sender's voice

Light edits are fine: fix a typo, cut a filler word, or shorten a long sentence. Do not change what the person meant. Do not turn "it saved me a morning each week" into "it transformed how our whole company works". The first is a real claim in a real voice. The second is marketing copy the customer did not write.

If you cut a quote, mark the cut with an ellipsis, and make sure the shortened version still says what they said. Send the edited version back for approval when the cut changes the meaning.

Pick the places where praise helps

Testimonials work best near the decision they inform. Common places are:

  1. Near the top of a sign-up or setup page, where a visitor wonders whether the product is worth the time.
  2. In a product update email, next to the change the customer asked for.
  3. On a page about one feature, where the quote describes that feature.
  4. In a sales call, when a prospect asks how the product works in practice.

Do not put a quote on a page where it does not match the claim around it. A quote about support speed next to a claim about pricing confuses people and hurts trust.

Keep a praise log in internal notes

Good praise disappears. The message sits in the inbox until someone archives it, and the next time you need a quote, you cannot find it. Keep a small log. Add an internal note to each quotable item with the exact line, the date and whether permission was given.

Use the note to record the status of the request too: "asked on the first, permission pending" or "approved for the onboarding page". That single note stops two people from asking the same customer twice.

The inbox search finds items by their message text, so a short note with the feature name helps you find the praise later. You can also export the feedback as CSV and keep the quotable rows in a spreadsheet.

Handle praise you cannot use

Some good praise cannot become a testimonial. The customer may be a competitor, may work for a client who forbids quotes, or may simply be unhappy later. Do not force it. Thank them, file the note as thanks, and move on.

Also watch for praise that hides a bug. "Love the product, the export is a bit slow" is praise and a report at once. Handle the report separately, following the steps in how to follow up on a bug report.

Track the permission, not just the quote

Permission can change. A customer who agreed to a quote in March may not want it on a new page in October, and a company may be acquired or change its name. Keep the date of the permission in the note next to the quote. Before you reuse an old quote in a new place, check whether the terms still hold. If you are unsure, ask again. Asking twice costs one short message, while a quote used without consent can cost you the relationship.

Pulling praise together in Escuta Produto

Use the inbox filtered by type set to praise. The type buttons in the widget are bug, idea, praise and other, so the praise filter shows the items customers chose as praise. Read each item, sort it into the three piles, and write a note for each quotable line.

Set nothing public from the inbox. The Escuta Produto dashboard is for the team. Publishing the quote is your decision, made on your own site or in your own materials, after the customer agrees.

For the wording of the request itself, the templates in how to reply to customer feedback cover praise and the follow-up. For how praise fits the weekly review, see how to triage customer feedback. Praise sent from your app through the REST API lands in the same inbox as widget feedback, so the same steps apply.

Frequently asked questions

Can you use customer praise as a testimonial without asking?

No. Ask the person first, from your own email. Name the line you want to use, say where it would appear and offer to show the final wording. Publish only after they agree.

What makes praise usable as a testimonial?

Specific detail in the customer's own words. A comment that names a feature, a moment or a result can stand alone on a page. General thanks is kind, but it works as a reply rather than a quote.

How much can you edit a customer quote?

Edit lightly. Fix typos, trim filler and shorten long sentences without changing the meaning. Send the edited version for approval if a cut changes what they said.

How do you keep track of testimonials you have collected?

Add an internal note to each quotable feedback item with the exact line, the date and the permission status. Export the feedback as CSV if you want the quotable rows in a spreadsheet for the whole team.