Your happiest customers vanish before you ask them to prove it.
Review requests sent at random moments feel like spam. Review requests sent 48 hours after a customer's first successful workflow completion feel like gratitude. The gap between those two moments is where most SaaS founders leave money on the table. You have a 3-day window after a customer deploys their first integration, closes their first deal, or ships their first campaign. After that, the emotional momentum dies. This workflow automates the timing. It doesn't automate the ask itself. Here's the pattern: Customer hits a success milestone (you define it—could be "first invoice sent," "first report generated," "first user invited"). A trigger fires. A human reviewer gets a Slack message with the customer's name, their milestone, and a pre-drafted review request. The human approves, edits, or kills it. If approved, the request goes out via email. If the customer has already opted out of review requests, they never see it. If they've been asked in the last 90 days, they don't get asked again. Why the human gate? Because a generic "please review us" email from an AI feels like a generic "please review us" email. A personalized note from a founder or operator who actually knows the customer's use case converts 3–5x higher. The automation handles the logistics. The human handles the judgment call. The failure mode most founders hit: they set the trigger too early (day 1, before the customer has actually used the product) or too late (day 30, after they've moved on). They also skip the opt-out mechanism and end up in spam folders. And they send the same template to every customer, which trains people to ignore it. This workflow solves all three by making the human the filter. The founder is the filter, and the founder has no time to filter—so you build a system that only asks the founder to filter the moments that matter.
Trigger: Customer completes a success event (first invoice, first report, first campaign launch, first team member invited—you pick the milestone). Workflow fires 48 hours after that event, with a 90-day throttle and opt-out check.
1. Define your success milestone in your product analytics or CRM (e.g., 'invoice_created' or 'report_generated'). 2. Connect your CRM or product database to your automation platform (Zapier, Make, n8n, or custom webhook). 3. Set the trigger: "When [success event] occurs, wait 48 hours, then check: Has this customer opted out of review requests? Have they been asked in the last 90 days?" 4. If both checks pass, send a Slack notification to a designated channel with: customer name, company, the milestone they hit, and a pre-drafted review request. 5. Add a reaction-based approval gate: 👍 = send the email, ❌ = skip, 💬 = edit and send. 6. Log all approvals and skips in a spreadsheet or database for monthly review. 7. Include an unsubscribe link in every email that updates a 'review_request_opted_out' flag in your CRM.