How to Get Customer Testimonials: Ask, Approve, Publish

A customer thanks your team in an email. Sales needs that story for a prospect. You still need a quote, their sign-off, and the right to use it on that page.

Here is how to get customer testimonials you can publish: ask about a real task, check the answer, agree on the exact words, and record where you can use them. Keep the request and the final quote in one record.

Start with a short written quote. Offer a call or video if they prefer. Use the emails below for the first ask, a follow-up, a vague answer, and sign-off.

Choose the customer story you need

Write down the buyer's question before choosing who to ask. A prospect asking about setup needs a story about getting started. On a pricing page, they may want to know which work the product replaces.

A CSM can suggest someone after a clear result or a call. Check that the person wants to help and has not been asked too often. Logins and a renewed contract alone do not tell you what changed for them.

You are choosing a quote for your own site. Keep public review requests separate. G2's guidance says not to split your list to ask only for positive reviews. A private survey score must not decide who can write a public review.

For the wider program, see customer advocacy and our G2 review campaigns guide.

Send a small, specific request

Ask while the task is still fresh in their mind. Use something they told you. Leave out results you have not checked with them. See the best time to ask for reviews and testimonials for other moments to consider.

Avoid sending a quote the person has never said. If you draft from their email, keep its meaning and call it a draft. Save the source text beside it.

If they prefer video, ask about the task, what changed, and who the product would suit. Agree on rights to record and edit before using the clip. Our video testimonials guide covers the setup.

If they do not reply, send one reminder

Choose a follow-up date that fits how you work with them. Try one follow-up, then close the request if they do not reply. This is a suggested limit, not a tested best send pattern. Stop if they say no.

Log the follow-up and closed state so a teammate does not ask again. For other channels, use our review and testimonial request email templates.

Turn a vague answer into a useful quote

If the answer is only a compliment, ask about the experience behind it. Keep it easy to answer. Send one question tied to the buyer's concern.

Check any result with the person who gave it. Ask what was measured, when, and what else changed. If they guessed, say so. Do not turn one person's result into a promise for all buyers.

Keep words that limit the claim when you trim the quote. Use our testimonial questions for other buyer concerns. The testimonial template helps you format the final answer.

Six checks from HighAdvocacy's documented workflow

We wanted to see how a request becomes a quote you can use. We also looked for steps your team must track elsewhere.

How we checked this: on October 21, 2026, we read six public HighAdvocacy guides: campaign setup, text testimonials, submission review, the Proof Library, showcase selection and sharing and embeds. We followed the described steps from invitation link to public display. At each handoff, we checked what the product records and what the marketer must confirm.

These are findings from reading the guides. We did not run a campaign, test tool connections, or measure response rates. The screenshots come from those guides. We checked them on October 21; they were not captured on that date. We rechecked the linked testimonial, Inbox and Library instructions on October 26, 2026, and corrected the steps below. The setup and review screenshots show the older interface.

1. A collection link does not send the invitation

The campaign guide shows a hosted page link and a widget you can embed. Put the hosted link in your email request. Choose one route and open it before sending.

The guide does not show a product event sending an email to the right person. Your team owns that choice and the last-ask record. Save the owner, person, source email or call, and planned use beside the link. Sales and success can then see who has asked.

For a first request, send the hosted link yourself. A working link and a clear owner are enough to start. Build links between tools once you can trace each step by hand.

2. The form needs a question the customer can answer

The written testimonial form has Question for customers and Detailed questions fields. Each line in that field becomes a bullet beside one text box. The person writes one answer; the form does not ask them to fill in each bullet.

Use the main question to name the task. Add prompts about the old way and what changed. Match those prompts to the page where you need the quote. A longer text limit can mean more work to fill in the form, without a better answer.

The flow also asks for a rating, name and work email, and confirmation that you can feature the testimonial with their name. Explain those fields if the person expects to send only a quote. Ask separately for company-logo rights and any other use beyond the agreed scope.

Source: HighAdvocacy's text testimonial setup guide. Existing screenshot checked October 21, 2026; shows setup, not a result or a filled-in response.

3. Internal approval and customer permission are different steps

Open Inbox → Need action and review the submission in its drawer. Approve adds it to the Library. Check whether that action also sends a reward. You can change a decision while decision buttons remain; rewarded submissions are final.

Check who sent it, what they wrote, and the facts behind any claims. Your team then decides if the content is ready. That status does not show that the person agreed to your edits or to use in a paid ad.

The screen below shows a G2 review in the review drawer. It is not a consent form for a quote. Its score and reward controls apply to that item. Neither proves that a business result is true. Before using a written answer, save the person's sign-off on the words and channels.

Source: review and act on submissions. Existing screenshot checked October 21, 2026; this G2 example shows team review controls, not consent to publish a quote.

4. A library item still needs a permission record

Use the Library filters to find the item, then open its proof details. Copy text is in More proof actions when available. The card shows the original testimonial date when known, otherwise its submission date. Added in the drawer records when it reached your workspace; check the submission's Inbox history for approval events.

The Library's Consent field shows OK to feature or Internal only. Check it before publishing. Keep additional agreements about exact edited words, allowed channels, logo rights, end dates and requests to stop use in your CRM or shared sheet. Link the quote to that record. Internal approval alone does not grant all rights.

Keep the source text and the agreed version. If your team trims it later, send the new version back. If a different team wants it for a new channel, check the agreed scope first. The right to use a quote on your site may not cover an ad.

5. Showcase rules can add new content without a fresh page edit

The showcase guide shows hand-picked items and auto-add rules. The rules use rating, photo, and source. Once approved, new items that match can enter the page on their own.

For a page with strict limits on use, pick each quote by hand. Keep doing that until your team can check each new item against those limits. A rating filter chooses what to show. It must not decide who gets asked for a public review.

If you remove a quote from one showcase, it stays in the library. Log each place you use it, plus copies outside HighAdvocacy. If the rights change, you need a list of all places that show the quote.

Source: choose what appears. Existing screenshot checked October 21, 2026; the reviews show how the builder works, not praise for HighAdvocacy.

6. Opening Share can make the showcase public

The sharing guide says that opening the Share drawer turns sharing on. Check the words, rights, and planned use first. If you open it while working on a draft, turn sharing back off.

Once live, open the page. Check the quote, name, title, any reward notice, and the claim next to it. A true quote can mislead if the headline above it promises a result the person did not describe.

Save the link and tell the person where the quote appears. If they ask for an edit or for you to stop using it, pause new use. Remove it where needed. Check copied slides, ads, and page quotes too. A change in the library does not prove those copies are gone.

Suggested team process based on the six-guide check above, October 21, 2026. Your team must track rights and check removals; the product does not do all these steps for you.

Approve the wording and the allowed use

Send the exact quote with the name, title, and company. List the channels you want to use. Ask about a headshot, logo, video edits, or paid ads where needed. Check who can grant those rights, and get the company's sign-off if required.

This email starts the sign-off process. The terms depend on the use and what the person or company needs. A reply does not clear all rights.

The FTC's endorsement guidance requires honest, non-misleading endorsements and clear disclosure of relevant material connections. A reward or discount may need disclosure. Approval from the customer does not make an unsupported advertising claim acceptable. See our FTC guidelines for incentivized reviews for more detail.

If the company says no, respect that choice. Hiding the name or sending a G2 invite does not get around it. Ask what, if anything, they can agree to, and follow that scope.

Copy the request and permission tracker

Paste this tab-separated tracker into a spreadsheet. Replace the bracketed row with your own request, then add one row per request. Keep emails and approval records private. The public page needs only the name and details agreed with the customer.

Request ID	Customer / owner	Source / task	Last ask / next action	Status	Original answer	Approved wording	Attribution / assets	Approver / evidence / channels / conditions	Incentive / disclosure	Placements / review owner	Withdrawal / removals
[Request ID]	[Customer identifier and teammate]	[Conversation link and relevant task]	[Request date and next step]	[Requested, no reply, clarifying, awaiting approval, approved, declined, or withdrawn]	[Unedited answer or source link]	[Exact agreed version]	[Allowed name, title, company, headshot, logo, or video]	[Who approved, evidence link, allowed uses, expiry, and conditions]	[Any reward and required disclosure]	[Every live URL or copied asset and who checks it]	[Request date, reuse paused, placements removed, and final check]

HighAdvocacy handles collection, team review, the approved library, and showcases. Use the tracker for rights and request details. For a process you can repeat, read how to collect testimonials on autopilot.

Put the quote beside the buyer's question

Place a story about getting started beside your setup steps. Put a result from one feature on that feature's page. Give sales the source and context with the agreed quote so they can use it as intended.

When the product changes, check that the quote still fits. Follow agreed end dates and requests for edits. A quote's age alone does not tell you whether it is still true.

Start with one customer, one buyer question, and one intended placement. Sign up free to set up the collection page, then use the first email above to make the request.