The short version: A Power Automate flow can watch for a job being marked complete and send the review request a day later, timed to when the customer is happiest rather than whenever you happen to remember. Built on the job list you already use plus Outlook, it costs nothing extra to run.
The trigger is marking the job done
Whatever you already use to track jobs, a SharePoint list, a Dataverse table, even a Tradify or ServiceM8 status pushed into one, has a moment where a job flips from in progress to complete. That flip is the trigger. A Power Automate flow watching for it can wait a day, then send a short message with a link to leave a review, Google, Facebook, wherever you actually want it. Nobody has to remember to send it, because remembering was never the plan, the status change was.
This is standard-connector territory: SharePoint or Dataverse plus Outlook, both already inside the Microsoft 365 licence a small trades business runs. There is nothing extra to buy for the mechanism itself.
Timing beats wording every time
A review request sent the same afternoon, while the mess is still being cleaned up, reads worse than one sent the next morning once the job actually looks finished. A day's delay, built into the flow as a scheduled wait rather than an instant send, is the difference between asking at the right moment and asking at the only moment you thought of it. The same completion trigger can run a second flow on a much longer delay, thirty days out, for a genuine check-in rather than another ask: how's it holding up, not can you leave us five stars.
When it is not worth building
If you finish two or three jobs a week and you already ask for a review on the doorstep before you leave, a flow is chasing something you have already solved with a habit. It earns its place once job volume means asking in person consistently is the thing that actually slips, not the reviews themselves.
Common questions
What's a good way to follow up with customers a month after the job?
A separate scheduled flow, checking for jobs marked complete around thirty days ago, can send a short, genuine check-in, how's it holding up, rather than a sales message. It is the same completion field doing a second job on a longer timer.
How do I make sure something happens after a job is marked complete?
Wire the completion status itself as the trigger, not a date on a calendar you have to remember to check. The moment a job flips to complete in your job list, a flow can fire the review request, the invoice reminder, or both, without anyone deciding to do it that day.
Finishing jobs and moving straight to the next one?
Tell me how you mark a job done today. Book a free 30-minute call and I will scope the flow that picks it up from there.