How fast should you respond to reviews?

Why speed matters

How fast to respond to reviews matters for two readers. The reviewer is most receptive soon after the experience; a reply days later can feel like an afterthought. Prospective customers see the timing of replies, and a negative review that sat unanswered for weeks suggests nobody is listening. Google's guidance for negative reviews includes responding promptly.

Sensible targets

• Negative reviews: within one working day.
• Positive reviews with text: within three days.
• Rating-only reviews: optional, within a week.
• Escalated reviews: acknowledged internally the same day; public reply once approved.
• App reviews about a bug: when there is something useful to say, such as a fix or workaround.

Allow for Google's checks

Google checks replies against its policies before they appear, usually within 10 minutes and occasionally up to 30 days. Measure reply time from review to when you submitted the reply, not when it appeared.

Measuring it

• Median hours from review to reply, by store and by rating.
• Share of negative reviews replied to within the target.
• Oldest unanswered negative review per store.

Why replies are slow

Slow replies rarely mean lazy staff. More often nobody is sure who should reply, store teams wait for approval they do not need, or nobody sees new reviews. Clear ownership and a daily check fix most delays.

An example

A chain finds its median reply time to negative reviews is four days, but 20 stores reply within hours and 30 never reply. The difference is not effort: the fast stores' managers have access and a daily routine; the others' profiles are owned by a former agency. Fixing access and adding a daily check brings the median under a day.

Common mistakes

• Measuring average instead of median; a few very old replies distort the average.
• Rushing sensitive replies to hit a target.
• Ignoring reviews over weekends and holidays.

Common questions

In short

Aim to reply to negative reviews within a day and positive ones within a few days, acknowledge escalations the same day, measure median reply time by store, and fix ownership where replies are slow.

A daily routine that works

Each morning, one named person per store or region opens the new reviews, replies to routine ones, flags anything that needs escalation and assigns the rest. A second short check in the afternoon catches the day's negative reviews. Weekends rotate between managers. This routine, more than any tool, is what keeps reply times under a day.

Report reply time weekly by store for the first month, then monthly once it is stable.

Holidays and festive peaks

Review volume often rises during festive seasons and sales, exactly when teams are busiest. Plan reply cover in advance for those weeks.

Doing this with Falcon

Falcon's CRM is where a team handles replies across stores. For each review it suggests an owner from your taxonomy, drafts a reply from the playbook for the review's theme and sentiment, and checks the draft before it is saved: is it long enough to sound personal, does it contain a phone number or email, does it promise compensation that needs a manager's approval, and does it fit the channel's length. Reviews can be assigned, escalated and tracked to done. The reply itself is posted in Google Business Profile.