A neighborhood restaurant in the DFW area came to us with 50 Google reviews and a 4.2 average. Ninety days later they were at 155 reviews and a 4.7 average. This is the exact sequence we ran for them — not a hypothetical playbook, the actual operational steps. Name withheld at the client’s request, results pulled from their Google Business Profile.
The starting point
The kitchen was strong. The dining room stayed busy. The owners knew their reviews did not reflect what was actually happening in the restaurant — the few reviews that did come in were disproportionately from upset customers, because happy guests had no system nudging them to leave one. Two direct competitors had 200+ reviews and were eating the top of the map pack.
Before we started
- 50 total Google reviews
- 4.2 average rating
- 1–2 new reviews per month
- Ranked #8 in the local pack for their category
What we built for them
The plan ran in three overlapping phases. The first month did most of the heavy lifting on volume; the second and third months locked in a steady weekly drip.
Phase 1 — past-customer reactivation (weeks 1–4)
The restaurant gave us their reservation export — roughly 800 past customers with email addresses. We dripped review requests out at about 30 per day over four weeks, so the new reviews looked natural to Google rather than landing in a suspicious one-day spike. This single phase generated 85 new reviews.
Phase 2 — automated requests on every new guest (week 2 onward)
We wired up an SMS request to fire two hours after each reservation ended, with a follow-up reminder three days later for non-responders. We ran every outgoing message through a thumbs-up / thumbs-down sentiment check first — happy guests went straight to the Google review link, unhappy guests went to a private form that pinged the owner. The response rate from new guests settled at about 32%.
Phase 3 — in-store touchpoints (week 3 onward)
We shipped them a branded QR code for receipt holders and table tents (“Loved your meal? Scan to let us know”) and an NFC tap card for the host stand. Those physical touchpoints added another 15–20 reviews per month, mostly from guests who did not open the SMS until the next day.
After 90 days
- 155 total Google reviews (+210%)
- 4.7 average rating, up from 4.2
- 35–40 new reviews per month, sustained
- Moved from #8 to #2 in their local pack
- Roughly 22% lift in reservations attributed to Google
Specific results vary by category, customer volume, and competitive density. Most of our restaurant clients see similar directional improvement in 60–90 days.
The piece that mattered most
If we had to point to a single change that did the most work, it would be the sentiment check on the way to the public review. By catching the small number of unhappy guests before they reached Google and routing them to the owner directly, we kept the public average climbing steadily instead of getting yanked down by occasional 1-star reviews. The owner could actually call the unhappy guest, make it right, and often turn a complaint into a return visit.
What this took from the owner
Roughly 30 minutes total during onboarding to hand over the reservation list and approve the message wording, then a few minutes a week to read the dashboard summary. That was the whole ongoing commitment. The system ran without their input from that point on.
What it would look like for your business
The exact sequence above is the kind of plan we build during onboarding for restaurant and hospitality clients. The numbers will not be identical — a quieter restaurant will not have 800 past customers to reactivate, a busier one might add reviews faster — but the structure transfers. If you want to see what this would look like for your situation, that is what the Review Plan Call is for.