Your customers already wrote your testimonials, in tickets
A companion sweeps thirty days of support threads, review sites, community channels and reply emails for praise specific enough to quote, files each with its source and context, and drafts the permission request for the five strongest.
On the first Monday of the month, a sheet fills: the exact quote, who said it, where and when, a link to the source, what they were talking about, and permission status. Roughly eight real candidates from a month of sweeping.
The best sentence a customer ever wrote about you was typed to a support agent at 4pm inside a ticket about something else. A companion reads all of those threads and finds it. Slack, Gmail and Google Sheets are native integrations; review sites are read in the session you are already signed into.
What is the exact prompt?
First Monday of the month:
- "Sweep the last 30 days for quotable customer praise in: (1) support threads in [tool, in my session], looking inside tickets about other things, not just CSAT comments; (2) our G2 and app-store reviews; (3) the [#customers] and community Slack channels; (4) replies in the [success@] inbox. A candidate quote must be specific: it names a feature, an outcome, a number, or a before/after. 'Great product!' is not a candidate."
- "For each candidate, add a row to the [Social proof pipeline] sheet: the exact quote, who said it (name, role, company), where and when, a link to the source, what they were talking about, and permission status = NOT ASKED. Skip anything from a customer whose account is in a support escalation or renewal dispute right now. Check with the CRM before filing."
- "Then draft (do not send) a short permission-request email for the five strongest: quote their own words back, say exactly where we would use it, and make declining one sentence easy. Nothing goes near the website until its row says GRANTED: collection is your job, permission is mine."
The specificity bar is the whole game
"Great product, highly recommend" persuades nobody because it could be about anything. "We cut invoice processing from two days to twenty minutes" persuades because it is checkable, the same reason answer-page quality is measured in verifiable claims.
The bar keeps the sheet short, because its reader is a human choosing what to ask permission for. The context column matters at deployment: a quote about onboarding belongs on the onboarding page.
Why is permission status a column?
Because the sources carry different rights.
A G2 review is public, and quoting it in an ad is a separate act. A community Slack message is visible to members rather than licensed to marketing. A support ticket is private.
NOT ASKED to ASKED to GRANTED or DECLINED keeps those distinctions where the person shipping the landing page can see them, and the escalation check keeps you from asking a favor of a customer whose ticket is on fire.
Deploying a pipeline of granted quotes
Match each to the objection it answers: the pricing quote near the pricing table, the migration-fear quote on the switching guide, the outcome-with-numbers quote in the sales deck. A quarterly pass through the GRANTED rows against your page list is a marketing afternoon with a high payoff.
It shares sources with customer feedback summaries and review-mining reports. Log which pages each quote appears on, so you can retire one in minutes when someone leaves.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents