Social proof is incredibly important for new businesses, but the process of getting and displaying customer quotes breaks down too easily. And then it ends up on the back burner.
Here’s a workflow that automates the entire system from collection to publishing.
We’ll use a few simple tools for this setup.
You can swap Webflow for Framer if you want. Now, let’s build the first part of the workflow.
Open Jotform:
Keep the form short. Most customers will not spend 15 minutes writing feedback. Short forms get completed more often.
Now, add these fields first:
Next, add the testimonial questions:
That last question is important. Specific results make testimonials stronger.
Finally, add a Checkbox
Then, make the important fields required before publishing the form.
This step is important. If customers have not used the product yet, the feedback is usually too general. It helps to wait until they:
In this example, the request will send after a customer upgrades in Stripe.
Open Zapier:
Zapier should find a recent upgrade event.
This keeps free users out of the workflow.
This gives customers time to use the product.
Keep the email simple. Here’s an example.
Quick question about your experience
Hey {First Name},
I saw you've been using the product for a couple weeks now.
If you have a minute, I’d love to hear how your experience has been so far.
Here's the form: {{Jotform Link}}
Replace the form link with your Jotform URL from Step 1. Before turning the Zap on, send a test email to yourself first. Check:
Then turn the Zap on.
Now, you need one place to keep all the responses. Without organization, testimonials become difficult to reuse later.
You do not need a complicated setup here. Start with these fields:
Now, go back to Zapier.
Example: “What changed after using the product?” → Result After
Submit a fake testimonial through the form. Then open Airtable. You should now see the testimonial appear automatically as a new record.
Most customers are not strong writers. That’s normal. Many testimonials come in:
The goal is not to fake the testimonial. The goal is to make it easier to read while keeping the original meaning.
Now paste this prompt (or similar):
Rewrite this testimonial clearly.
Keep the meaning the same.
Keep any numbers or measurable results.
Remove fluff.
Keep it under 50 words.
Make it sound natural.
Testimonial: {Result After}
Next, map the Airtable field Result After into the prompt.
You should now see a cleaned-up version of the testimonial.
Save the cleaned version back into Airtable.
Then, return to Zapier.
Now, every testimonial has:
Once you collect enough testimonials, finding the right one becomes difficult. You need some structure.
Paste this prompt (or similar):
Read this testimonial.
Return:
Customer type
Use case
Main outcome
Testimonial: {{Clean Testimonial}}
Then: Test Step
Go back to Airtable. Create these fields:
Return to Zapier.
Map the AI responses into the Airtable fields like this:
At this point, each testimonial is stored in fields you can search and filter.. That makes it easier to display relevant testimonials on different pages later.
You can publish testimonials automatically after the AI cleanup step. But you may prefer a quick manual review first, especially once you start collecting a larger number of submissions.
That gives you an opportunity to check:
To do this, inside Airtable, add: Status
Then create options like:
Then, in Zapier:
If you do not need manual review, you can skip this step and publish testimonials to Webflow automatically after the AI cleanup step.
Next, we need a way to publish testimonials automatically. Open Webflow.
Then, create these fields:
Click: Create Collection
Now, go back to Airtable.
Add:
Now, create another Zap.
This prevents drafts from reaching the website.
Map:
Now click: Test Step
Open Webflow CMS. You should now see the testimonial appear automatically.
This helps prevent the same Airtable record from being published again.. At this point, approved testimonials automatically move from Airtable into your website.
Most founders show the same testimonials on every page. That is usually less effective. Different pages need different customer testimonials.
Here are some examples:
Your pricing page needs:
Your onboarding page needs:
In Webflow:
Then:
Each page will now show more relevant testimonials.
Some testimonials sound impressive but do nothing. Others quietly improve conversions. You need data to know the difference.
Then choose the events you already track in PostHog, such as:
Run the test long enough to collect enough data. As a general rule, detailed testimonials often perform better than vague ones.
wouldn't have even thought to do that. great advice as always.