# When to Send a Review Request

> Timing by trade, the right time of day, why same day beats next week, when not to ask at all, and how to automate sending without automating the ask.

Source: https://reviewgenerationtool.com/when-to-send-a-review-request/  
Site: ReviewGenerationTool  
Updated: 12 November 2026

---

Short answerSend the request when the customer is most pleased and least busy, which for most businesses is within a few hours of the work finishing. Same day beats next day, and next day beats a week later by a wide margin. The exceptions are trades where the result takes time to appreciate, such as a garden, a course of treatment or a house move, where a few days or weeks is better. Pick one timing per job type and stick to it, because consistency is what makes the numbers mean anything.

Knowing when to send a review request is the cheapest improvement available in review generation. The same message, sent four hours earlier, converts noticeably better, and it costs nothing to change.

## The principle

Ask when three things are true at once: the customer has the result, they are still thinking about you, and they are not in the middle of something. For most local businesses that window is the same evening.

Ask when the customer has the result and is not busy.

## Timing by trade

Business | When to send | Why |

Restaurant or cafe | Same evening or next morning | The meal is the experience, and it fades quickly. |

Trades and callouts | Within a few hours of finishing | The relief of a fixed problem is at its strongest. |

Salon or barber | Same day, after they have seen it in their own mirror | People judge a haircut at home, not in the chair. |

Garage or MOT | At collection or that evening | While the car still feels different. |

Dentist or clinic | Day after a routine appointment | Not while anybody is numb or uncomfortable. |

Landscaping or building | Two to seven days after completion | Once the site is tidy and they have shown somebody. |

Estate agent or solicitor | After completion, not after exchange | The relief arrives at the end, not in the middle. |

Course of treatment | After the final session | A review mid-course is a review of an unfinished job. |

## Time of day

Early evening works for most consumer businesses, because people are at home with a phone and nothing urgent. Mid-morning works for business customers. The two times to avoid are during the working day for consumers, when the message gets opened and forgotten, and after nine at night, which reads as intrusive from a local business.

For text messages in particular, treat anything before eight in the morning or after eight in the evening as off limits, regardless of what your data says about open rates.

Later reviews are shorter, vaguer and less persuasive.

## Why the same day matters so much

-
### Memory
Detail fades within a day. Reviews written later are shorter and vaguer, and specific reviews are the ones that persuade other customers.

-
### Goodwill
The feeling of being well looked after is strongest at the end of the job.

-
### Context
They still have your name, your number and the paperwork to hand.

-
### Competition for attention
By next week your message is below three other things they also meant to do.

## When not to ask at all

If the job went badly, fix the job. A review request sent to somebody whose complaint is unresolved invites exactly the review you deserve, and it looks like you were not listening. Pause the request, deal with the problem, and ask afterwards only if it was genuinely resolved to their satisfaction.

This is not filtering, which is the deliberate practice of asking only people expected to be positive. It is sequencing: complaints get handled before requests get sent, for everyone.

## Time zones and multi-site businesses

A group sending from head office at six o’clock sends at five in one region and seven in another. It sounds trivial and it moves the numbers. Schedule by the location’s own clock rather than the head office one, which also avoids the worst version of this, where a national send lands at nine in the evening for a third of the customers.

## A worked schedule

A domestic electrician. Jobs finish between nine and four. The office sends review requests in a batch at six in the evening, covering everybody completed that day, with a single reminder three days later at the same time to anybody who has not left one.

Two things make it work. The electrician mentions it at the door, so the text is expected rather than unsolicited. And the batch at six removes the decision from a busy engineer who would otherwise forget.

## Automating it without losing the human part

Automation should send the link, not do the asking. The sequence that works is: person asks at the end of the job, system sends the link that evening, system sends one reminder three days later, system stops. Where businesses go wrong is skipping the first step and relying on a cold message to a customer who was never asked.

## The reminder, and exactly when

Three days is the usual sweet spot. Soon enough that the job is still recent, late enough that it does not feel like chasing. Send it at the same time of day as the original, because somebody who was busy at six on Tuesday is often free at six on Friday.

Word it as a reminder rather than a repeat. One line, acknowledging they are busy, with the link again. Then stop, and make sure the system stops too: the most common complaint about automated review requests is the third and fourth message, which no business ever intended to send.

## Measuring the timing

Change one thing at a time and give it a month. If you move from next-day to same-evening, keep everything else identical, then compare the share of requests that became reviews. Most businesses find a meaningful difference, and once it is settled nobody needs to think about it again.

## Repeat customers

Somebody who uses you four times a year should not be asked four times a year. Once is right, and the best moment is usually the second or third visit, when they know you well enough to say something specific but have not started to feel taken for granted. After that, leave them alone unless something notable happens, such as a job that went particularly well.

## Seasonal and one-off exceptions

Holidays, school runs and busy trading periods all change when people read messages. The exception worth coding into any system is simple: do not send on the day of a known closure or during the first week of a seasonal rush, because the reply you get is about the queue rather than the service.

### Send at the right moment, automatically
Trigger review requests when a job is marked complete, with one reminder and a clean stop.

[Review generation](/tools/review-generation/) [Automations](/tools/smart-tasks/)

## Frequently asked questions

**Q: How soon should I ask for a review?**
For most local businesses, within a few hours of finishing, or the same evening. Trades where the result takes time to appreciate are the exception.

**Q: What time of day works best?**
Early evening for consumers, mid-morning for business customers. Avoid the middle of the working day, and avoid texting before eight or after eight.

**Q: Should I ask a customer who complained?**
Not until the complaint is resolved. Fix the job first, then ask if it was genuinely put right. That is sequencing, not filtering.

**Q: How many reminders should I send?**
One. It recovers people who intended to and forgot. A second reminder annoys the people who have already decided not to.

**Q: Can I automate review requests?**
Send them automatically, yes. The ask itself should still be made by the person who did the work, or the message arrives unexpected and converts badly.

## Sources
The Google documentation behind the guidance on this page. Google changes these pages without notice, so check the date on any figure before you rely on it.

- [Tips to get more reviews](https://support.google.com/business/answer/3474122)
- [Prohibited and restricted content](https://support.google.com/contributionpolicy/answer/7400114)
