Starter · Level 1 of 3
Some links below are affiliate links. If you sign up through them, Automate My Life may earn a commission at no extra cost to you, which helps keep the site free. Only tools worth using get a recommendation here.
The fastest way to automate a client testimonial request is to trigger it from an event you already track — an invoice getting marked paid, a project card moving to "Done," or a final file landing in a shared folder. Connect that event to an email step through an automation platform like Zapier, add a short delay so the client has time to actually use what you built, and send a specific, easy-to-answer ask. Once it is wired up, the testimonial request stops depending on you remembering to send it after you have already moved on to the next project.
Why the Ask Keeps Getting Skipped
Client testimonials are one of the highest-leverage pieces of marketing a small service business has, and they are also one of the easiest things to forget. The project wraps, the invoice goes out, and attention moves to whatever is next on the list. By the time anyone thinks about asking for a testimonial, the client's memory of the specific win has faded, or the moment has simply passed.
The fix is not a reminder on your calendar that you will eventually ignore. It is removing yourself from the loop entirely: let a system watch for the signal that a project is actually finished and let it send the ask without you touching it. The client still gets a personal-sounding note. You just stop being the single point of failure for whether it goes out at all.
What You Need Before You Start
This setup assumes two things are already in place. First, somewhere you mark projects or invoices as complete — a project board like Trello or Asana, or an invoicing tool where you flip a status to "Paid." Second, an automation platform that can watch that status and act on it. This guide uses Zapier for the walkthrough because it has the largest library of app connections, but the pattern works the same in Make or, if you are comfortable self-hosting, n8n.
Zapier's free plan includes 100 tasks a month but limits you to two-step Zaps — a trigger plus one action. The workflow below adds a delay step, which pushes it to three steps, so you will need at least Zapier's Professional plan (from $19.99 a month billed annually, covering 750 tasks). If you would rather stay on a free tier, Make's free plan allows multi-step scenarios (not capped at two steps like Zapier's) with 1,000 operations a month, and n8n's self-hosted Community Edition is free with no execution limits if you are willing to run your own instance on a small VPS.
The Two Triggers Worth Automating
Most freelance and small-service businesses have one of these two signals available already. Pick whichever matches how you actually track work finishing.
| Trigger | Where it lives | Best for |
|---|---|---|
| Invoice marked “Paid” | Your invoicing tool (Wave, QuickBooks, FreshBooks, Stripe) | Project-based work billed per invoice |
| Card or task moved to “Done” | Your project board (Trello, Asana, Notion) | Retainer or ongoing work tracked on a board |
Both work the same way once you get to the automation step: trigger, delay, send. The example below uses the board trigger because it is the more common setup for freelancers who do not invoice per milestone.
Worked Example: Trello Card to Gmail Draft via Zapier
Here is the full setup, start to finish, using a Trello board with a "Done" list and Gmail for the email.
- Create a new Zap. In Zapier, click Create, then Zaps.
- Set the trigger. Choose Trello as the trigger app, and pick the event “Card Moved to a List.” Connect your Trello account, select the board you use for client work, and set the target list to “Done” (or whatever you name your completed-work column).
- Add a Delay step. Search for the built-in “Delay” action, choose “Delay For,” and set it to 3 days. This gives the client time to actually see and use the finished work before you ask them to write about it — an ask that lands the same afternoon a project closes reads as rushed.
- Set the action. Choose Gmail, and pick “Create Draft” rather than “Send Email” for your first few runs. A draft lets you review what the automation produced before anything goes out, which matters the first week you have this running.
- Map the fields. Set the “To” field from the client email stored on the Trello card (a custom field or the card description), the subject line to something specific like “Quick favor — [Project Name],” and the body to the template below.
- Test the Zap by moving a test card into the Done list, confirm the draft appears correctly in Gmail, then turn the Zap on.
Once it is confirmed working over a week or two, you can switch the action from "Create Draft" to "Send Email" so the whole chain runs without you opening Gmail at all. Keep the draft step around longer than feels necessary the first time you build something like this — it is the cheapest way to catch a mismatched field or an awkward subject line before a client ever sees it.
The Testimonial Request Email Template You Can Copy
Specific requests get better answers than open-ended ones. "Would you write a testimonial?" asks the client to do the hard work of remembering the project, choosing what mattered, and writing it well. Naming the outcome you want feedback on does that work for them.
Subject: Quick favor — [Project Name]
Body:
Hi [Client First Name],
Now that [Project Name] has been live for a few days, how has [specific outcome, e.g. "the new booking page"] been working for you?
If it has been useful, would you mind sending two or three sentences about what changed, or what stood out about working together? It would be used on this site, with your approval before it goes anywhere.
No pressure either way, and thanks again for the project.
[Your Name]
Fill in the bracketed fields per client, or map them automatically from the fields already stored on the Trello card or invoice if your trigger app captures that data. The specific-outcome placeholder is the part worth spending the most time on — naming the actual thing that changed (fewer missed calls, faster checkout, a cleaner inbox) gives the client something concrete to react to instead of a blank page.
What If They Do Not Reply
Most people mean to answer and then do not. Rather than treating silence as a no, add a second branch to the same Zap: a Filter or Path step that checks whether a reply has come in after 10 days, and if not, sends one short, low-pressure follow-up. Keep it to a single line — something like a reminder that there is no rush, and the request still stands whenever it is convenient. One follow-up is normal. A second one starts to read as pressure, which works against the honest, no-pressure tone the ask needs to land well.
Where to Send Them If You Want a Public Review, Not Just a Quote
A quote for your own site is one outcome. A public review is another, and it is worth deciding which one you actually want before the automation fires, since the ask reads differently. If the goal is a public review, point the client to your Google Business Profile review link or a LinkedIn recommendation instead of asking them to reply by email — both are free, and both carry more third-party weight with a future prospect than a quote sitting on your own site. If the goal is a quote you control and can edit for length, the email template above works as written. Some businesses run both: the email captures the quote for the site, and a lighter follow-up a week later asks for the public review from clients who responded warmly the first time.
Where the Testimonial Should Actually Go
A reply sitting in your inbox is easy to lose. Add one more step to the Zap — or a second Zap triggered by a Gmail reply matching a label — that appends the response to a Google Sheet with columns for client name, project, date, and the quote itself. That sheet becomes the place to pull from when a testimonial is needed for a proposal, a landing page, or a portfolio update, instead of scrolling back through months of email.
Common Snags
- The ask goes out too soon. If clients seem surprised or the project is not actually finished when the email fires, extend the delay past 3 days, or trigger off a more reliable signal like invoice payment instead of a board move that might happen early.
- Replies feel generic. If most responses read like a single sentence of thanks rather than a usable quote, tighten the subject line and the specific-outcome question in the template. A vague ask produces a vague answer.
- The email never gets sent. Check that the Trello custom field for client email is actually populated on every card before the automation runs — missing data is the most common reason a step silently fails.
- The wording feels automated. If a client mentions the email felt like a form letter, trim the template further and drop in one detail specific to that project by hand before the draft goes out. A draft step exists exactly for this kind of light edit.
A Few Questions Worth Settling First
How soon after a project should you ask for a testimonial? A few days to a week after delivery is typically enough time for a client to have used the work without the request going stale. For retainer clients, tying the ask to a quarterly or project-milestone marker works better than a single post-delivery trigger.
Do you need permission to publish a testimonial publicly? Yes. The template above builds that in with the "used on this site, with your approval" line, but treat a reply to that email as informal consent only — get an explicit yes before anything goes live if the client's name, company, or photo will be attached.
What if a client never replies at all? Let it go after one follow-up. A testimonial that has to be chased twice is rarely worth the relationship cost of chasing it a third time, and the automation will simply catch the next client who wraps a project.
Keep the Rest of the Business Running Itself
Once the trigger-delay-send pattern is working for testimonial requests, the same shape shows up everywhere else client work touches an inbox: renewal reminders, project kickoff checklists, and status updates. For a broader look at what else is worth automating in a small service business, see 15 Workflow Automations That Save Solopreneurs 5 Hours a Week. And for a look at the same trigger-wait-action pattern applied outside of client work, a fully automated morning routine runs on the same basic logic — a trigger, a wait, an action, no manual step in between.
Evidence and verification
Last verified: July 12, 2026. This guide was checked against the official documentation for the form, email, calendar, and automation tools named in the workflow. Interfaces, plan limits, pricing, and feature availability can change. Confirm any feature or cost that determines your setup before relying on it, and test the workflow with a non-critical example first.
Leave a Reply