Reviews are the single most undervalued growth lever in service businesses. Most operators are running 1-3 reviews per 100 services delivered — well below what a deliberate review-generation flow produces. The math is unambiguous: a 10-percentage-point lift in review velocity moves local-search rankings meaningfully within 60-90 days. The infrastructure to do this is mostly already in your platform; what's missing is the framework.
This playbook is that framework.
The 24-hour routing flow
The core mechanism is a post-service SMS that arrives 24 hours after the appointment ends, asks for a 1-5 rating, and routes the customer's reply based on what they say.
Step 1 — The 24-hour rating SMS
A single-sentence SMS sent automatically 24 hours after the service is marked complete. "Hey [first name] — how did your [service] go yesterday? Reply 1-5 (5 = loved it)." The simplicity is what makes it work. Long-form asks get ignored; a 2-second reply commitment gets responses.
Step 2 — Reply routing
A reply of 4 or 5 triggers a follow-up SMS with your Google review link and a one-sentence ask: "Glad it landed! Would you share that with a quick Google review? It helps other [neighborhood] folks find us. [link]" A reply of 1, 2, or 3 triggers a different SMS: "Thanks for the honest feedback. The owner would love to hear what we could have done better — can we call you?" The routing happens based on the customer's self-report, not on our pre-judgment about who is likely to be happy.
Step 3 — Owner response to the negative-feedback flow
When a 1-3 reply lands in the owner's inbox, the response cadence matters. Personal call within 24 hours, not an email. Listen first; acknowledge what went wrong; offer a specific path forward (free correction, partial refund, complimentary upgrade — whatever fits the situation). The customer who feels heard often becomes a 5-star reviewer down the road. The customer who gets a defensive response goes public with the complaint instead.
The legal nuance — and why it matters
Google's terms of service prohibit "review gating" — selectively requesting reviews from customers you expect to leave positive ones. What this framework does is different:
- The framework asks EVERY customer for feedback (no selection)
- The customer self-reports their experience (no business judgment)
- The routing happens based on the customer's stated experience, not the business's expectation
This is materially different from review gating and complies with Google's terms. The distinction is real, but it matters: if your flow asks "are you happy?" and only sends the Google link to people who say yes, that's the legal line. If your flow asks "rate your experience" and routes based on the rating, that's compliant.
When in doubt: every customer gets asked. The routing happens AFTER the customer reports.
The response cadence for public reviews
Every public review — positive or negative — should get a response. Within 48 hours. Two sentences. The response isn't for the reviewer; it's for the next customer reading the reviews.
For 5-star reviews:
"Thanks for the kind words, Sara! It was a pleasure working with you on your balayage. Looking forward to your next visit."
For 1-3 star reviews:
"We're sorry your experience didn't meet expectations. We've documented your feedback to review with our team and we've reached out directly — looking forward to making it right."
Three rules for negative-review responses:
- Never argue facts in public
- Never name specifics about what happened (especially anything that could identify the customer)
- Never make commitments you can't back up
The calm, professional response in public is what the next 50 potential customers see when they're researching your business. That audience is your real reader.
What "review velocity" actually means
Google's local-pack ranking algorithm weights two review metrics differently:
- **Total review count** matters but plateaus — moving from 50 to 100 reviews matters more than 500 to 600
- **Review velocity** (reviews per month) matters continuously — a business adding 15 reviews per month is signaling "active and trusted" more than a business with 200 reviews and 1 per month
The 24-hour routing flow optimizes for velocity, not just count. A business generating 15+ reviews per month consistently for a year typically moves into local-pack contention even in dense urban markets.
Cross-industry application
The flow works across every service industry, with minor copy adjustments:
- **Barber shops, hair salons, nail salons**: standard 24-hour cadence
- **Med spas, esthetics**: extend the SMS delay to 3-5 days post-service (clients evaluate aesthetic results over days, not hours)
- **Tattoo studios**: wait 14 days post-service before the ask (initial healing has to settle before the customer accurately evaluates the work)
- **Pet groomers**: same-day cadence (the pet owner sees the result immediately when they pick up the pet)
- **PT clinics**: at discharge from the plan of care, not after individual visits (the review reflects the relationship, not the session)
The principle is the same; the timing adapts to when the customer is most able to fairly evaluate the work.
The metrics that prove the flow is working
- **Review velocity per month** (target: 8-15 reviews per 100 services delivered)
- **Public review average rating** (target: 4.7+ stars)
- **Negative-feedback resolution rate** (target: 80%+ of 1-3 responses converted to satisfied resolution)
- **Local-pack ranking position** for primary keyword (track monthly; expect movement in 60-120 days)
What this looks like at six months
A service business that runs the review flow cleanly typically sees:
- Total Google reviews growing by 90-180 per year versus 12-36 without the flow
- Average rating holding at 4.7+ stars because problems get caught in private before they go public
- Visible local-pack ranking improvements for the primary local search terms
- A defense against the occasional 1-star review (it lands in a sea of recent positive reviews instead of being prominent)
That's the operating discipline that compounds. Reviews aren't an afterthought to operations; they're a deliberate output of operations done well, captured by a flow that asks the right question at the right time.
Every happy customer is a potential review. The flow is what turns the potential into the asset.