Ask after the customer has experienced completed work and received the handover, at a reasonable local time. There is no universal best hour or delay established for every service business.
Use completion as the trigger
An appointment ending in the calendar does not prove the work is finished. A contractor may need another part, a return visit or a final inspection. Start with a verified completion event, then choose the sending window.
For a straightforward visit, the experience is available to review after the service handover. For a multi-day project, wait until the agreed work is finished. Do not base the request on whether you expect the customer to leave a positive review.
Choose a practical starting schedule
| Situation | Suggested starting rule |
|---|---|
| Routine daytime visit | After completion and handover, during your permitted sending window. |
| Late evening completion | Queue for the next appropriate daytime window. |
| Project needing another visit | Wait for the final completion event. |
| Customer asks for no messages | Suppress the request through that channel. |
These are operational suggestions, not experimentally proven conversion winners. Account for the customer’s time zone, the message channel and any applicable messaging restrictions.
Test timing without inventing a winner
If you have enough eligible completed jobs, compare two reasonable windows while keeping the message and selection rules the same. Record request deliveries, complaints and opt-outs as well as new reviews. Do not use a small difference from a handful of jobs as proof that one schedule is universally better.
Review submission dates do not always map exactly to individual messages. A customer may use a QR code, return to an older link or have a review published later. Treat a period-level comparison as a signal rather than perfect attribution.
Set a limit on follow-up
A single reminder after a few days can be a starting option if the channel and customer permissions allow it; it is not required. Choose a limit before launch and stop when the customer asks. Do not repeatedly contact somebody to chase a rating.
Google encourages genuine customer reviews; it does not prescribe a universal sending hour. For implementation, read the completion-trigger checklist and use a neutral request template.
KEDO review automation connects the completion action to an agreed request process and handles timing with you during onboarding.
Sources and editorial notes
Timing rules are original editorial starting points, not measured performance claims. Customer messaging permissions and local restrictions must be respected. 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.