A dental practice doubled its review volume without a single gated request

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Two dentists, a hygienist team, and a front desk of three serve a family dental practice that has traded from the same high-street location for decades. Its patient base is loyal and local, its appointment book full, and its online reputation a fossil: the newest public reviews date back years and mostly discuss the car park. The practice manager reads the review profiles occasionally and winces; the front desk knows reputation matters and has ideas about it, but asking patients for reviews is one unplanned task among two hundred on any given morning.

What it was costing

The practice's reviews were years old and mostly about parking. New patients checked profiles and went elsewhere; the front desk knew reviews mattered but had no system, and one staff member's 'only ask the happy ones' idea was a policy violation waiting to happen.

What they could see

• The most recent reviews are years old; a prospective patient searching locally finds a competitor's page refreshed last week.
• The front desk means to ask patients for reviews and forgets by mid-morning, because asking is nobody's job among the queue.
• One staff member's plan to request reviews only from happy patients is one audit away from a platform-policy problem.
• Negative reviews sit unanswered for weeks because drafting a response feels like a task requiring the whole practice.
• Nobody at the practice can say, on any given day, what their public rating actually is.

The constraints we worked inside

• Review gating is a platform-policy violation — the system must request from all patients, period.
• The front desk runs the schedule; anything manual dies within a fortnight.
• Responses to negative reviews needed clinician judgment — automation drafts, humans approve.

What had been tried before

The practice manager asked the front desk to invite patients to leave a review at checkout.

Between the queue at the desk and the next patient in the chair, the ask died within a fortnight — good intention, zero system.

A printed card with a review QR code was placed on the reception counter.

Patients assumed it was marketing material or Wi-Fi instructions; the counter already had a leaflet ecosystem nobody reads.

A review-management tool was trialled after a sales call, with its own login and dashboard.

It asked the front desk for daily attention the schedule could not give; the trial expired with barely a dozen logins.

What we proposed

The reliable part becomes automatic and the human part stays human. Every patient receives the same review request by text after their appointment — uniform, ungated, and unhurried, which is both the policy requirement and the point: honesty at volume. Responses to reviews are drafted from templates but posted only after the practice manager approves, with clinicians consulted on anything sensitive. New reviews reach the manager's phone for one-tap approval, and a dashboard shows the practice its reputation daily instead of quarterly, so the front desk sees the effect of the system they run.

Just as important is what we ruled out, and why:

• Review gating — Filtering requests toward happy patients is a platform-policy violation and, in healthcare, a trust violation too; it was off the table before design began.
• Incentivised reviews — Offering rewards for reviews breaches platform terms and sits badly with clinical ethics; the volume had to come from reliability instead.
• Fully automated response posting — A worried patient's negative review needs clinician judgment; an unapproved automated reply risks making a bad appointment worse in public.

How the work ran

Delivered by the growth pod — strategist + automation specialist over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

GoHighLevel workflows

The request must fire for every patient without anyone remembering to; a workflow is the only mechanism in a front desk's day that never forgets.

Review request automation

Uniform, ungated text requests after each appointment; the honesty is not a compromise but the design that survives an audit.

Response drafts

Templates draft, the practice manager approves, clinicians weigh in on the sensitive ones — automation proposes, people speak in public.

Reputation dashboard

The manager's phone gets new reviews for one-tap handling; daily visibility is what turned the reputation from a wound into a routine.

What went wrong

How we worked together

Cadence

A weekly 20-minute call with the practice manager across the four-week build, plus one joint session with the dentists on response tone.

Client side

The practice manager decided and owned sign-offs; the front desk defined what done looks like for their day.

Decisions

The front desk's definition — one tap, zero typing — killed two features we had planned; everything else followed the policy constraint on gating.

They provided

The appointment-type list, confirmation that patient mobile numbers were consented for service texts, and dentists' time for the response-tone session.

What changed

The headline: new review volume per quarter, sustained across two quarters — +112%, read from Review platform counts. A second check: average rating as recent reviews diluted the parking-era legacy at 4.6 → 4.8.

The front desk stopped experiencing reviews as an accusation and started experiencing them as feedback that arrives on their phone, handled in seconds. New reviews describe actual care — a nervous patient treated kindly, a same-day emergency seen — instead of parking. The practice manager reads the practice's reputation daily in the time it takes to make tea, and the staff member with the gating idea now explains to new colleagues why uniform requests are the honest version.

The result was read from Review platform counts against the pre-engagement baseline over the stated window, with a guardrail check on average rating as recent reviews diluted the parking-era legacy. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The post-appointment workflow with its send timing, owned by the practice manager's login.
• A response template library, including the clinician-review step for negative feedback.
• The reputation dashboard with alerts configured to the manager's phone.
• A one-page staff procedure covering what automation does and what humans approve.