Retention and proof
Ask happy customers to vouch.
Does two jobs, apart or together. It drafts a short, personal request to a customer whose result is on record, asking for one thing: a quote, a star review on a named review site, or a short reference call. And it files the praise customers send in their exact words, with who said it, where it came from, and a consent flag that stays pending until a person confirms it. Nothing goes out until a person sends it.
- Their words, never edited
- Consent marked pending
- A person sends the ask
At a glance
- Group
- Retention and proof
- Command
- /testimonial
- Uses
- Your numbers log, their words
- Writes
- A request draft, quote entries
- Sends
- Nothing. Drafts only.
01When to use it
Use it after a win or a kind word.
- Your numbers log shows a real result for one customer, such as a metric that moved, a baseline beaten or a target hit, and you want to ask them for a testimonial or a review.
- A customer sent praise, a quote, a review or a reference, and you want it filed where you can use it again.
- You are building a case study, a landing page, a proposal or a sales piece, and want a bank of checked quotes to draw from, each showing its consent state.
- A renewal, a milestone or a successful handoff makes this a natural moment to ask.
Not for
- Writing the full story of a result as a case study. Use /case-study
- Drafting replies to the latest unanswered reviews on your local listings. Use /local-visibility
02What it needs
The customer, the record, their words.
- The customer, and the short name their files are kept under.
- Your numbers log, for the result behind the ask: the baseline, where it stands now, the source and how sure the record is. On an agency setup, the client goals file.
- Your voice files. On an agency setup it writes in the client's voice, from the client brand file.
- To file praise: the text as it arrived (pasted, an email export, a transcript of a review screenshot, or an item in your inbox), who said it, their role and company, and where it came from.
- Your rules file, read before anything is drafted. A banned claim is refused by name, with the reason. With no rules file, it says so and asks before drafting any public claim.
- Optional: your permissions file, which says what outside uses are already cleared.
03What it writes
A request draft and a quote entry.
- Operations/testimonial-requests/{slug}-{date}.md
- The request, marked draft, and on a solo or team setup a line added to your task list. It thanks the customer, names their result, makes one ask, offers to draft a starter quote they can edit, and gives them an easy way to say no. When the only record of the result is inferred or stale, the claim is softened or the customer is asked to confirm it. On an agency setup it sits in the client folder, marked confidential.
- Library/swipe/testimonials.md
- A new entry in your running quote bank: the quote exactly as written, who said it, when and where it arrived, any result they cite with its source, and consent marked pending. On an agency setup, each client keeps its own file, marked confidential.
- Ledger row
- Only when a testimonial confirms or sets a number not yet logged. The testimonial is the source, the confidence is honest, and earlier rows stay as they were.
04Limits
What it never does.
- Send, email or post the request, or submit a review for the customer.
- Make up a quote, a name, an attribution or a figure.
- Edit, polish or merge the words a customer sent.
- Round a number up, or pass off a customer's figure as verified. One the log does not hold stays in the quote, labeled as theirs.
- Mark consent as cleared. That flag changes only when a person confirms the customer agreed.
What stays with you.
- Sending each request. The skill stops at the draft.
- Confirming the customer agreed before a quote reaches a landing page, an ad, a proposal or a case study.
- Checking any figure a customer quotes that your records do not show.
- Picking the approver when your rules file and another file name different people.
05Sample output
Two entries in a quote bank.
From the quote bank of a made-up IT support firm. Each quote is kept exactly as the customer wrote it, with a note on what a person must do before any outside use.
| Said by | Quote | Permission so far | Consent |
|---|---|---|---|
| Pat Example, office manager, Example Dental | "They answer the same day and explain the fix in plain words." | Not yet asked | Pending |
| Sam Sample, owner, Example Cafe | "Every call ends with a plain answer, not a ticket number." | Approved in email, 2026-09-18 | Pending |
- Pat Example, office manager, Example Dental Pending
- Quote"They answer the same day and explain the fix in plain words."
- Permission so farNot yet asked
- Sam Sample, owner, Example Cafe Pending
- Quote"Every call ends with a plain answer, not a ticket number."
- Permission so farApproved in email, 2026-09-18
Next steps noted for a person
- Pat Example: ask for approval before the quote is used outside the business.
- Sam Sample: confirm the approval email, then clear consent.
06Related skills
Often run beside it.
07Questions
Before you run it.
Will it send the request for me?
No. It saves the request as a draft for a person to send, and it never posts or submits a review in the customer's name.
What if a customer quotes a number?
It checks the number against your numbers log. When the two match, the entry cites the log row. When they do not, the quote stays exactly as written and the figure is labeled as reported by the customer, not verified.
When can I put a quote on my site?
Once a person confirms the customer agreed to outside use and has checked any figure in the quote that your numbers log does not hold. Every entry is filed with consent pending and a note on the permission so far, such as an approval email or not yet asked, and the skill never clears that flag itself.
Have us build it
We can build it for you.
Start with the free plan. A person names the first fix.



