When to Send a Google Review Request: Right After the Job vs Next Morning

Send the Google review request after the job is finished and you have left, not while you are still in the driveway and not next week. Same-day beats a delayed ask. Same-hour, while the customer is still watching you pack, can feel pushy. For home services, the text goes out after the tech is gone and the work is done. If the job ended late, next morning is the better send. This page is that operational delay. It is not a clock-time article about Tuesday at 10 a.m. versus Thursday at 2 p.m. That calendar question already lives on the best time to ask for Google reviews. Do not treat the two as the same decision.

The trigger is a completed job. The delay is long enough for you to leave, short enough that the job is still today’s event. Google does not publish a required wait. What follows is how operators should set the send so the ask matches the work, without fake urgency and without a promise about how many reviews will come back.

The trigger is job complete, not invoice day and not booking day

A review request timed to the booking is too early. The customer has not lived the job. A request timed to whenever bookkeeping sends the invoice can be days late, and it arrives next to a bill instead of next to the finished work. Mark the job complete in your own system when the work is actually done: the leak is dry, the door opens, the patient has left, the last box is inside. That status is the trigger. The text follows that status, with a short delay you choose on purpose.

Do not send from the driveway while you wait for a signature. The customer still has you in the room. A review ask then feels like a tip jar. Finish, confirm the work is done, leave, then send. If you need a sentence on site, it is only a heads-up that a link is coming, not a request to type a review while you watch.

Do not use “right after” as an excuse to text before the customer has seen the result. A painter who texts at lunch on day one of a three-day job is early. A locksmith who texts two days after a 20-minute lockout is late. The completed moment is the rule. The clock on the wall is secondary.

Same-day after you leave is the default delay

For a normal service call that ends in daylight, send the SMS after you have left the property and had time to mark the job done. Many shops use a delay of about 30 to 90 minutes after that close. You are no longer in their driveway. They have tried the repair or walked the room. The job is still the thing that happened today. That is the window this page is about.

If your team closes jobs in a batch at the shop that night, do not let “after close” mean the office manager sends a pile of texts at 9:30 p.m. Close the job when the tech finishes, or hold the send until next morning. A review request is not an emergency. It should not buzz a household that is trying to sleep. Holding overnight is a courtesy tied to the job clock, not a marketing “best hour” claim.

When next morning is the right send

Use next morning when the job ended late, when the customer is exhausted (an overnight emergency, a move-in that ran past dark), or when you cannot honestly say the work is finished until they test it in the morning. A furnace call at 8 p.m. can wait until morning so they have heat overnight and then get the link with coffee. A lockout at noon should not wait until the next day. The customer already went to work. The moment was this afternoon.

Next morning means a normal start to their day, not a 6 a.m. alarm. If you are setting this by hand, pick a time you would not mind receiving a short text from a contractor. If you are comparing that to “what hour of the week converts,” you have drifted into the other article. Come back here and ask only: is the job done, and are they likely awake?

What not to confuse with this delay

Do not copy a blog schedule that says always send at a famous hour. A job that closes at 11 a.m. does not need to sit until a preferred afternoon slot two days later. The other post covers time-of-day habits in general. This one covers the gap between “tech left” and “link sent.” Keep that gap same-day unless late finish, quiet hours, or an unfinished test says otherwise. A Google review request SMS template still has to sit on top of the right trigger. Pretty wording on the wrong day is still a late ask.

Set the delay by the kind of completed job

The same shop can have two honest delays. Write them down so the dispatcher is not improvising.

• Short repair or service call: after the tech leaves, same day. Not in the kitchen. Not three days later when the invoice is mailed.
• Emergency that ends late: next morning, after the customer has had a night with the problem actually fixed.
• Install the customer needs to live with: same day only if they have used it. If first use is tomorrow, send after that first use, still close to the finish, not at the sales visit.
• Multi-day project: at punch-list close or final walkthrough, then the link. Not at the deposit, not at the first day of demolition.
• Recurring route: after a completed visit you would be willing to have described in public, not at the start of the season and not after every single mow if you have already asked this month. One ask after a real visit is enough until the next reasonable interval. Do not text after every weekly stop.
  If a complaint is still open, finish the fix or the call first. Then, if the job is complete, the same request can go out. Do not build a rule that only “happy” jobs get a link. That is gating. An open leak is not a mood. It is unfinished work. Once it is finished, the ask is the same one you send everyone else.

A QR on the invoice can sit next to this timing, not replace it. Someone who wants to review on a laptop at night can scan later. The send time of the text is still the completed-job delay. How to place that code is covered in Google review QR code for business. The QR does not decide when the text fires.

One reminder, then stop, on the same job

The first send is the one that matches the completed job. A single reminder a few days later is for people who did not tap and did not opt out. Do not send the reminder the same evening as the first text. Do not send it as “last chance” or “we only need two more reviews this week.” That is fake urgency. The reminder is the same plain ask: honest review, direct link, stop if you want out.

If they reply with a problem, the timer stops and a person calls. Do not keep an automated sequence running over a complaint. If they already reviewed, do not remind them. If the number is wrong, fix the number. Do not try the spouse’s phone because you found it in an old job file.

Write the delay where the tech can see it. “Close the job. Leave. Link goes out after we are gone, same day, or next morning if we finished after quiet hours.” That sentence is the policy. The free playbook is the longer checklist if you want this written next to the link setup. If the profile itself is not ready to receive the reviews this timing will produce, check your Reputation Score before you argue about 30 minutes versus 90.

Put the delay in minutes next to the job type, not in a slogan. “Service call: 45 minutes after closed and off site. Late finish after 8 p.m.: next morning. Multi-day: day of walkthrough, after we leave.” If the number is not written, each tech will pick a number that matches their own comfort. Comfort is how driveway texts and Friday batches both survive a staff meeting where everyone agreed on same-day.

Check a week of closed jobs against the texts that actually went out. You are looking for the gap between complete and sent, not for a perfect minute. If most asks leave the next afternoon because that is when someone sits down, the policy is already “next day,” no matter what the whiteboard says. Move the send closer to the completed job or admit the batch and shorten it. A next-morning batch for late jobs is a rule. A three-day pile is a backlog.

The companion article on clock time will not save a late trigger. A polite hour on Wednesday does not fix a request about Monday’s repair. Finish the work, leave, send. Use the other page only when you are choosing among awake hours, not when you are deciding whether the job is even over.

Let ReviewNix handle the follow-up after you set the rule

You can send these by hand if you are the only tech and you actually do it after every close. The moment you have two trucks, hand timing slips. One tech texts from the driveway because they are proud of the repair. Another forgets until Sunday. The customer feels both versions, and neither matches the rule you wrote.

ReviewNix connects to your Google Business Profile and sends a neutral review request by SMS, email, or WhatsApp after a completed job. You set the delay so it fires after the job is done, not while the tech is still on site, and not a week later when someone remembers. Reminders can follow once. Stop and opt-out end the thread. The dashboard shows the sends against the jobs, so “we usually ask” becomes a record. AI reply drafts help when the review comes back, including the quiet 5-star you would otherwise leave unanswered. The software does not decide that a job is complete. You do, when the work is finished. After that, the follow-up does not depend on who remembered the phone.

Set it up once. Let ReviewNix handle the follow-up. Use the trial form when you want the delay on the completed job instead of on someone’s memory. Keep the best time to ask for Google reviews post for clock-time habits. This send is the job trigger, and the form is how you stop doing it from the truck.

Frequently asked questions

Should I text the review link while I am still at the house?

No. You can say a link is coming. Send it after you have left and the job is done. A text in the driveway feels like a tip request, and the customer has not had a minute alone with the finished work.

Is next morning too late?

Next morning is right when the job ended late or they need to test the result overnight. It is late when a midday job sits until the next day because the office batch-sends. Same-day after you leave is the default. Next morning is the exception for quiet hours and unfinished tests, not a weekly habit.

How is this different from the best time of day to ask?

That other page is about calendar timing, the hour and day you might choose in general. This page is about when the request goes out relative to a completed job. Finish the work, leave, then send. Do not hold a finished morning job until a favorite afternoon slot next week.

Can I wait until the invoice is paid?

Do not wait on payment if the work is already complete and the customer is not in an open dispute about the job. Invoice timing drifts. The review is about the work, not about your collections schedule. If a payment fight is still open, resolve that conversation first, then use the same ask you use for every other completed job. Do not send a review link as a condition of payment.