Trigger
BuiltA job or delivery is marked complete in your system. That's the only signal it needs.
When a job is marked done, it asks the customer for a review — once, politely, with a single reminder if nothing arrives.
Built · not live yet
A job or delivery is marked complete in your system. That's the only signal it needs.
Writes the review request in your voice, naming the actual job rather than "your recent purchase".
Nothing sends until a human says go. Every draft, every time.
Goes out from your own address, inside your hours, with a working opt-out.
Watches for the review. If none appears after three days, one reminder — then it stops.
Why this matters
Most happy customers would leave a review if asked on the day the work landed. Almost nobody gets asked then — the job finishes, everyone moves on, and a week later it feels awkward to bring up. So the reviews that do appear are skewed towards the people annoyed enough to write unprompted. Asking every satisfied customer once, at the moment the work is fresh, is the whole difference. The reminder cap matters as much as the ask: chase somebody twice for a review and you've turned goodwill into an irritation.
Built on the same engine that's sent 797 emails for ClipZone since June 2026.1
A draft that breaks one of these cannot be approved. The approve button refuses; it does not ask twice.
Attempts to dodge these by spacing out letters or swapping in lookalike characters are normalised away before the rules run. That gap was found by testing the system adversarially, not by using it.
Start
This one isn't running yet — a call is the place to say whether it's worth building for you first.
Setup from $1,500. $400/month to run it.