Asking is most useful when the customer has received the work and knows what they are being asked to evaluate, and not every job should produce a public review. The design starts with eligibility, consent, and a clear owner. It should never filter customers by predicted rating or imply that a positive response is required.
Define what “completed” means.
A calendar event ending is not always a finished job. The source system needs a dependable status or human confirmation that the work is complete. Decide who sets that status and whether the customer has received any necessary handoff or follow-up first.
Write down exclusions. A disputed job, unresolved support issue, sensitive service, duplicate record, or customer who has opted out may need a different path. Platform rules and applicable messaging requirements should be checked for the channels used.
Choose the right customer review request message and destination.
The invitation can thank the customer for working with the business, identify the completed service accurately, and ask for honest feedback. It should not request a five-star rating, offer an undisclosed incentive, or turn a private complaint into a public test. The destination should be the business’s approved review profile or feedback route, not a link assumed to be current.
Keep the message short and recognizable. A customer should know who sent it and why. Email copywriting or another channel-specific review can make the wording fit the relationship.
Build the handoff with checks.
An illustrative sequence is: job marked complete, eligibility checked, approved contact channel selected, invitation prepared, authorized send occurs, event recorded, and duplicate send prevented. If a person must approve the message or timing, that step belongs in the map.
Do not send private job notes or unnecessary personal information into a messaging tool. The workflow should use only the fields needed to deliver the invitation and recognize a duplicate. Marketing automation is a possible implementation scope after the systems, permissions, and customer communication rules are defined.
Plan for an exception.
If the completion status is uncertain, the contact information is invalid, consent is missing, or the destination link fails, stop the send and send the issue to the owner. If a customer replies with a concern, route it to a person rather than automatically asking again. A review-request system should not make an unresolved problem feel ignored.
Test with sample completed and excluded jobs, plus a duplicate event. Confirm that the message arrives at the approved address or number, that opt-outs work, and that the team can see failures. An on-screen “sent” state is not enough if the provider rejected the message.
Start with the moment work is truly finished.
Show us how your team closes a job and follows up today. We can map where a respectful request belongs and which checks should stop it.