A.I. Eh?PackagesClient sign inBook a call587-577-8979→DemoNothing here is real — fictional business, fictional numbers — and it resets whenever you like.
The thank-you nobody remembers to send.
A job is marked closed. The engine decides whether this customer gets asked for a review — and the interesting half is the customer it refuses to ask twice. Pick what has happened to Ana before now.
the job is closed and nobody has asked this customer.
The customer — Ana, 403‑555‑0132
Job finished · marked done by the crew
Asking the engine…
What is actually running
- Once, ever
- A customer who has been asked is not asked again. The refusal above is the engine’s, not a setting — a second ask costs goodwill and does not get answered.
- A failure is not an ask
- If the mailer was down, nobody was actually asked, so the retry is allowed. Getting that backwards means one outage silently costs every review it touched.
- Who gets the review link
- Everyone who is asked. Asking only the customers who said they were happy is review gating: Google’s review policy prohibits it, and the FTC’s 2024 Rule on Consumer Reviews (16 CFR 465) treats suppressing negative reviews as an unfair practice.
- What is not built
- There is no scheduler in this stack and no timed nudge. The ask goes when the job is marked closed, because the API runs on more than one instance and an in-process timer would ask the same customer once per instance. A private route for an unhappy customer is part of the build we would scope with you; it is not running here, so this page does not act it out.
When did you last ask?
Most businesses ask when they remember, which is after the good ones have already forgotten. This asks once, when the job closes, and never asks the same person twice.
Book a free call →In the real product, everything you just watched lands in the client portal.