GoodRepWhat's a Reasonable Response Time for Online Reviews?
The right SLA isn't a single number. It's two: 24 hours for negative reviews, 48 hours for everything else, measured from when the review posts, not when you see it.
Owners ask this question because the conventional advice ("respond as quickly as possible") isn't actually a target. Quickly compared to what? An hour? A day? The end of the week? Without a real number, the response cadence drifts to whenever someone happens to look, which usually ends up being a week or more.
This post lays out a defensible response time SLA for a local business, what it means in practice, and how to actually measure and hit it without the work taking over your day.
Key takeaways
- Negative reviews: 24 hours from posting. 12 is better. 4 is the gold standard for high-stakes industries.
- Positive reviews: 48 hours from posting. Batch on a fixed weekly slot for efficiency.
- Measure from posted time, not seen time: the customer doesn't care when you noticed.
- Industry context tightens the standard: hospitality, healthcare, and any subscription category benefit from faster response.
- The SLA is what makes the cadence sustainable: without it, response time slowly creeps to weeks.
Why "Respond Quickly" Isn't a Standard
Walking into most local businesses and asking about review response time produces some version of: "We try to respond pretty quickly." Then the actual data, when you look, shows the average response time is 4-9 days, with some negatives sitting for 3+ weeks.
The gap isn't because owners are lazy. It's because there's no defined target, so response work gets fit in around everything else. When the week is calm, reviews get answered same-day. When the week is busy (which is most weeks), reviews get answered when someone notices them, which can be a week later.
A defined SLA is what changes this. It moves response time from "when there's space" to "by this time." That single change is usually what separates a 5-day average response time from a 24-hour one.
The 24/48 Standard
For most local businesses, the right baseline is:
Negatives within 24 hours. A 1, 2, or 3-star review needs a response within one business day. Twelve hours is better. Four is the gold standard for high-stakes verticals (hospitality, medical, anything with a public scoring component).
Positives within 48 hours. A 4 or 5-star review can wait two business days without losing anything. The reason for the longer window is operational: positive responses can be batched on a weekly slot, which is much more efficient than handling them one at a time.
The 24/48 split exists because the cost of delay is asymmetric. A negative review that sits for a week accumulates seven days of views from prospective customers seeing the complaint and no response. A positive review that gets a thank-you on day three instead of day one loses almost nothing.
The cost of an unanswered negative review puts the math on the negative side. The positive side is mostly about the relationship signal to the customer who wrote it and the engagement signal to readers; neither is harmed by a 48-hour window.
Why "From Posted Time" Matters
The most common SLA measurement mistake is starting the clock when you saw the review instead of when it posted. The reasoning sounds reasonable: I can only respond to what I know about. The problem is that the prospective customer reading the profile doesn't know when you noticed. They see the review's timestamp and your response's timestamp. The gap between those two is what they read.
A review posted Monday at 9am that you saw Wednesday at 4pm and responded to Wednesday at 5pm is a 56-hour response time, not a one-hour one. That's the number that should be in your SLA.
The implication is that the SLA depends on monitoring infrastructure. If you're checking apps once a week, you can't hold a 24-hour standard regardless of how fast you respond once you see something. Real-time alerting on negative reviews is the prerequisite for the negative-side SLA. How to monitor reviews across multiple platforms covers the setup.
Industry Adjustments
The 24/48 baseline works for most local SMBs. A few industry contexts justify tightening it.
Hospitality (hotels, restaurants, vacation rentals). OTAs (Booking.com, Expedia, TripAdvisor) score response times publicly. A 24-hour negative response time is the floor; 12 hours is competitive. Reviews for hotels and hospitality covers the platform-specific dynamics.
Healthcare and professional services. The privacy constraints on what you can say in public mean the response itself is generic, but the speed of acknowledgment matters more. A 12-hour SLA on negatives signals engagement even when the response can't address specifics.
Subscription businesses (gyms, salons, software). Cancellation-related negative reviews in particular benefit from faster response, often within the same business day, because the reviewer is sometimes still mid-decision about whether to escalate.
Single-location independents in low-volume categories. A 24-hour SLA can stretch to 36 if the volume is low and you've got a clear weekly cadence. The signal customers read is consistency more than speed once you're in the same-week range.
What the SLA Looks Like as a Process
A 24/48 SLA in practice looks like this for a typical small business:
A new negative review hits on Tuesday at 3pm. An alert pings the owner's phone. The owner takes a 15-minute break around 4pm, drafts and posts a calm response. Logged response time: 1 hour.
A new positive review comes in Wednesday morning. No alert (the system only alerts on negatives). The review sits in the queue until Friday's weekly slot. The owner responds in batch with two other positives from the week. Logged response time: 48 hours.
The same review pattern, run without the SLA, looks like this: the negative gets noticed Friday afternoon when the owner happens to log into Google. The positive gets noticed two weeks later, mixed with eight others, and never gets responded to because it feels late. The negative response goes up at 75 hours. The positive doesn't.
The SLA isn't aspirational. It's the structural choice that produces the first version instead of the second.
How to Actually Measure It
Most local business owners don't know their average response time because they don't measure it. The fix is a single number tracked monthly.
The simple version: at the end of the month, look at every review from the past 30 days, calculate the time difference between posted and responded for each, and average them separately for negatives and positives. The number you want to see: under 24 for negatives, under 48 for positives.
If the negative number is creeping up, the alert system is broken or being ignored. If the positive number is creeping up, the weekly slot is being skipped. Either way, the diagnosis is in the number, not in vague impressions.
Most review management tools track this automatically. The metric is usually called "median response time" or "average response time" and lives in the dashboard. If yours doesn't show it, that's worth fixing.
What Happens When the SLA Slips
Response time SLAs slip predictably during busy periods, vacations, and ownership transitions. The recovery move when this happens isn't to write a long apology to the late-responded reviewers. It's to silently catch up, post short responses, and reset the clock.
The reason: customers reading the profile don't know there was an SLA target or that you missed it. They see whichever responses are up. A clean response posted on day 12 is better than no response, and definitely better than a response that explains why it took 12 days.
The recovery routine: a one-time sweep of the past month's unanswered reviews, short responses on each, then back to the regular cadence. Most slips can be cleaned up in 90 minutes once they're caught.
The Bottom Line
The right response time SLA for a local business is 24 hours for negative reviews and 48 hours for positives, measured from when the review posted, not when you saw it. Real-time alerting on negatives is what makes the negative-side SLA possible. A weekly slot for positives is what makes the positive-side SLA efficient. Industry context can tighten the standard but rarely loosens it.
The SLA isn't a stretch goal. It's the structural choice that keeps response work from quietly drifting into "whenever."
GoodRep tracks the SLA automatically: real-time alerts on negatives, response time dashboards, and the monthly numbers that show whether the standard is holding. $39/month, 14-day free trial. Start free.