01
Confirm completion
Trigger only from a confirmed completed job, invoice, or other approved completion signal.
Review requests
Ask at the right time—after the work is actually complete.
Use confirmed completion status and approved messaging to request feedback without asking too early, duplicating requests, or treating every customer the same.
Workflow
Keep every step attached to a clear next action.
Exact timing, wording, routing, and connected actions are configured from the customer's approved operating rules.
02
Check exclusions
Skip complaints, open callbacks, opt-outs, duplicate requests, or other customer-defined exclusions.
03
Send the request
Use the approved review link, channel, wording, and timing.
04
Capture response signals
Track delivery, engagement, replies, or issues that require a person.
05
Route unhappy customers
Send service-recovery replies or complaints to the right human workflow instead of pushing for a public review.
06
Prevent duplicates
Record the request so the same job or customer is not repeatedly contacted.
Measure
Know whether the workflow is working.
- Eligible completed jobs
- Requests sent
- Delivery / engagement
- Review-link clicks
- Human service-recovery handoffs
- Duplicate requests prevented
Guardrails
Automation stops where the approved rules stop.
- Trigger only after confirmed completion
- Respect opt-outs
- No review gating
- No fabricated incentives
- Service issues route to a human
Want this playbook configured around your trade?
Start with the real system, volume, owner, and exception rules. Then test the workflow before production traffic touches it.