Build a small system that collects testimonials as they come in and reviews them every month. That way, when it’s time to share social proof, it’s already there.
Here's how to build that system.
This system does five simple things:
Then, once a month, you'll choose your best quotes and use them on your website, emails, and social media.
We'll keep things simple. Start with Gmail and a Jotform form. Don't try to connect every tool yet. Get one simple system working first.
Before you save your first testimonial, decide what good proof looks like; otherwise, you'll end up saving messages that aren't very helpful.
Look for testimonials with at least one of these:
Use this scoring guide (or something similar):
You now have a simple way to sort the good testimonials from the weak ones.
Now, it's time to create one place to store all your customer proof.
In Airtable:
Create these fields:
Set Original Message, Clean Quote, and Outcome as long text fields. Set Permission Status as single select with: Not requested, Asked, Approved, and Rejected. And set Best Use Case as single select with: Homepage, Pricing page, Sales email, Launch email, Social post, and Case study. Set Date Added as a Created time field.
Every testimonial now has one place to live, along with its permission status and best use case.
Your inbox is probably full of customer feedback. Start there.
Next, search your inbox for old messages with phrases like:
When you find a message that's worth saving, open the message, click the Label icon, and add the Proof - Review label.
Spend the first week or two labeling messages yourself. This helps you develop a good sense of good testimonials before you automate anything.
It's time to automate the process.
Go to Zapier and create a new Zap. Trigger:
You should find one of the emails you labeled earlier. If not, label one email in Gmail and test again.
Now, add the AI step:
Paste this prompt (or something similar):
Read the customer message below. Use only the information in the message. Don't make up results or add details that the customer never shared.
Return:
Clean Quote
* Under 35 words.
* Stay as close to the customer's original wording as possible
Outcome
* What changed for the customer
* If no outcome is mentioned, write "Outcome not stated."
Product Used
* The product, service, template, course, or feature they mention
Strength Score
* Rate the testimonial from 1 to 5
Permission Status:
* If the customer permits to share their testimonial, write "Permission clear."
* If they don't, then write "Permission not clear."
Best Use Case
* Homepage
* Pricing page
* Sales email
* Launch email
* Social post
* Case study
Follow-Up Question
* If the testimonial is vague or needs more detail, write one short question that would make it stronger
Score the testimonial like this:
* 5 = Specific and convincing
* 4 = Strong with useful details
* 3 = Positive but general
* 2 = Kind words only
* 1 = Not usable
Customer message: Insert the Gmail email body here.
Click: Test step.
The AI will read each email and extract the important details, so every testimonial is organized consistently. If you notice the AI rewriting the customer's words too much, add: “Keep the customer’s plain language.”
Now, it's time to decide what happens to each testimonial.
In Zapier, use Paths if your plan includes them. If not, create separate Zaps with Filters.
Path 1 — Strong and approved
If:
Do this:
Create a new Airtable record and save the testimonial.
Map:
Do not mark the quote as Approved until a person checks the original message and the permission.
Path 2 — Strong, but no permission
If:
Do this:
Add a Gmail action, then create a draft asking if you can use the testimonial.
Then, add Airtable → Create Record.
Only change the status to Asked after the draft has been sent.
Path 3 — Nice, but vague
If:
Do this:
Add a Gmail action, then create a draft asking what changed after using your product.
Then, create an Airtable record.
Path 4 — Weak or not useful
If:
Do this:
Create an Airtable record.
Now, each testimonial has a clear place and a clear next step.
The best time to send a testimonial form is right after a customer says something good. Don't send your testimonial form cold.
Go to Jotform:
Create the form with these fields:
Make the permission questions clear. Give customers enough information to make an informed choice. Tell them where their testimonial may be published and whether you'll edit it.
Now, connect Jotform to Airtable with Zapier:
Create a Zap:
Map each answer to the matching field in your Airtable base.
If the customer clearly agrees to your use of their testimonial, set Permission Status to Needs review. After a person checks the form answers, change the status to Approved. If they select No, set it to No permission.
Form testimonials and inbox testimonials now land in one library.
A library of testimonials only helps if you use it.
Create one final Zap:
Send the reminder to yourself. Have the email remind you to:
That's it. One reminder each month is enough to keep your testimonial library useful.
As you build your testimonial system, always keep these points in mind.
The best systems are usually the simplest. One label, one form, one library, and one monthly review are all you need. That's enough to build a steady flow of customer testimonials without adding more work to your plate.
an untapped treasure trove of validation. thanks again!