Use a confirmed job-completion event to queue one neutral request to the correct customer. Check messaging eligibility and sending time, prevent duplicates and log failures for a person to resolve.
Define what completed means
Choose the business event that confirms work is finished: for example, an authorised technician marking the job complete. Do not treat a missed appointment, a paid deposit or an elapsed calendar slot as proof of completion.
Record a stable job identifier, customer contact, completion time and the responsible team member. The precise fields and tool connection depend on your business; do not assume every CRM exposes the same event.
A reusable workflow design
- Receive: accept the completion event from an agreed source.
- Validate: check customer contact, job status and messaging eligibility.
- Deduplicate: look for an existing request against the same job and customer.
- Schedule: respect the appropriate local sending window.
- Send: deliver a neutral invitation with the correct review link.
- Record: save the delivery result and request identifier.
- Resolve: route failures to a responsible person.
This is a recommended design checklist, not a claim that every listed mechanism is included in every KEDO installation. Confirm the agreed connection, fields and failure behaviour during onboarding.
Test the cases that cause duplicate or premature requests
| Test case | Expected design outcome |
|---|---|
| Completion event arrives twice | One customer request, with the duplicate recorded. |
| Work is not actually complete | No review request yet. |
| Contact detail is invalid | Flag for correction; do not silently report success. |
| Customer opted out | Suppress that message channel. |
| Late local completion | Queue for the appropriate sending window. |
Use internal test records with authorised recipients. Replaying a real customer’s job event just to test the workflow can send an unwanted duplicate.
Keep the feedback invitation fair
Use the same neutral invitation for eligible customers, regardless of predicted satisfaction. The automation sends a request; it must not compose or publish the customer’s review. Google prohibits review incentives and selective positive solicitation.
KEDO’s published review workflow starts from the completion action in the job notification. If work is not marked complete, the system follows up after an agreed period; late customer requests wait until the following morning. The exact process is confirmed before go-live.
Start with the request templates and timing guide. Measure delivery consistency and failed requests before attributing changes in revenue or ranking to automation.
Sources and editorial notes
The checklist and test matrix are original recommended controls. The KEDO description is limited to the currently published workflow; additional integrations and controls require confirmation. Sources checked October 8, 2026.
See the workflow
Finish the job. Make the request.
See how KEDO connects job completion to your Google review-request workflow, then review current system pricing before you pay.