Configuring review asks safely in general practice: the exclusion playbook

Most guides on getting more Google reviews for a GP practice tell you how to ask. Almost none tell you who not to ask — and in general practice, that's the part that actually matters. Send a cheerful "how was your visit?" text to the wrong patient after the wrong appointment and you've turned a review ask into a wound. Getting the exclusions right isn't a compliance afterthought; it's the difference between a review programme your team is proud of and one they quietly switch off.

Why do exclusions matter more in general practice than anywhere else?

A cafe can ask every customer for a review and the worst case is mild annoyance. A GP practice can't, because the reason a patient walked in might be the last thing they want a text about. General practice sees the full span of human health in a day — a vaccination, a mental-health review, a cancer follow-up, a bereaved partner, a worried parent — and a single undifferentiated review blast treats all of them as identical. They aren't. The patient in for a flu jab is a fine ask. The patient who just had a hard conversation in the same building is not.

This is why the exclusion map is the foundation of the whole programme, not a footnote to it. Get it right and the review ask only ever reaches patients for whom it's genuinely appropriate — which is most of them, and more than enough to build real volume. Get it wrong and you don't just risk one upset patient; you risk your reception team losing faith in the system and turning it off. Look, we get it — this is exactly the caution that stops a lot of practices asking at all. The answer isn't to avoid asking; it's to be precise about who you ask.

Exclusions are about appropriateness, not screening for happy patients

Here's the distinction that keeps a GP review programme both effective and above-board, and it's worth stating plainly: exclusions are about clinical appropriateness, never about guessing who'll say something nice. You're not filtering for sentiment — you're filtering for suitability. Every patient who is clinically appropriate to ask gets asked the same way, whether you expect them to be delighted or not. What you exclude is the visit type or cohort where a review request itself would be insensitive, intrusive, or inappropriate — full stop, regardless of how the appointment went.

That line matters for two reasons. First, it's the honest and compliant way to run reviews in a health setting — you're not gaming which voices reach Google, you're respecting the context of care. Second, it's what keeps the programme durable: a system built to chase only happy patients eventually reads as manufactured, while a system that asks appropriately and offers everyone a private channel to raise concerns builds a profile that looks exactly like what it is — a busy practice most patients are glad to have found.

Which cohorts and visit types should a GP practice exclude?

The exact list is practice-specific, but the shape is consistent across the GP practices we work with. These are the categories that come up almost every time — the working core of that 8-to-15-rule configuration:

• Mental-health consultations — anything under a mental-health treatment plan or presentation. A review text here is intrusive at exactly the wrong moment.
• Bereavement-adjacent and end-of-life visits — a patient or family in grief, palliative-care coordination, a death in the practice's care. Never an ask.
• Sensitive-health presentations — sexual health, terminations, serious or distressing diagnoses, results consultations for major conditions.
• Certain paediatric contexts — the ask, if any, goes to a parent or guardian, and sensitive paediatric presentations are excluded entirely.
• Flagged and vulnerable patients — patients your team has marked as vulnerable, at-risk, or not to be contacted for non-clinical reasons.
• Complaints in progress — a patient in an open complaint or dispute is handled by the practice directly, not sent a review invite.
• Recently contacted — a frequency cap so no patient is asked repeatedly across multiple visits in a short window.

Layer on the practice-specific ones — a particular clinician's patients during a sensitive period, a specific clinic session, telehealth versus in-person distinctions — and you land in that 8-to-15 range. The point isn't the exact count; it's that each rule is a deliberate clinical-appropriateness decision, made once, then applied to every patient without reception having to remember it under pressure.

Where does the private feedback channel fit in?

Excluding a cohort from the public review ask doesn't mean shutting them out of feedback altogether — and this is where the two halves of a good programme meet. Alongside the public ask, every patient can be offered a private channel to reach the practice: a route for raising a concern, a problem, or a comment that goes straight to your team rather than to Google. That's universal service recovery, offered to everyone — not a gate that decides who's allowed to review.

It matters because it separates the two jobs cleanly. Public reviews build the practice's search visibility and new-patient trust. The private channel catches the frustrated patient — the one who waited too long, felt rushed, or hit a billing snag — before that frustration lands as a public one-star that the whole team then sees and stews on. We dig into that reception-morale dividend elsewhere, but the structural point here is simple: exclusions decide who the public ask is appropriate for; the private channel makes sure everyone still has a way to be heard.

Can reception just manage exclusions manually?

In theory. In practice, no — and it's worth being honest about why. Manual exclusion means someone at the front desk deciding, patient by patient, at the end of a full day, who should and shouldn't get a review text — while also booking, triaging calls, and managing a waiting room. It's the kind of task that's fine on a quiet Tuesday and falls apart on a chaotic Friday, and the failure mode is the worst one: the mental-health patient who gets the cheerful text because someone was slammed. One slip like that and the practice — rightly — loses confidence in the whole idea.

That's why the exclusions have to be systematic, not remembered. Set the rules once as clinical policy, and they apply themselves to every patient automatically — the appropriate visits get the timed ask, the excluded cohorts never do, and reception never has to make the call in the moment. This is the same no-extra-steps principle behind how the ask runs off your existing recall and reminder flow, which we cover in the wider approach to new-patient acquisition for GP practices.

How the engine applies exclusions without a workflow change

The mechanics are deliberately boring, which is the point. The engine works off your practice's appointment and recall data — the information your reminder system already sends. Your exclusion rules sit as configuration on top: appointment types, patient flags, cohorts, and frequency caps that decide who's eligible for the ask before any message is ever composed. Eligible patients get a request timed to the appropriate post-visit moment, worded to read as if from your practice, never as an obvious third-party blast. Excluded patients are simply never in the pool.

Because it reads from the reminder-capable software you already run, there's no new screen for your team and no change to how a consult is booked or closed. Any modern GP system with automated reminders can feed it — the same rails that already send recall texts. That's what makes precise exclusions practical rather than aspirational: the clinical judgement is yours, set once; the execution is automatic, every day. You can see how the visibility payoff compounds once the volume is flowing in why a 20-year practice can rank below last year's newcomer and how billing shows up in your profile in bulk-billing and Google reviews. There's a real proof point too — a Melbourne practice's local-pack turnaround — and the full GP playbook library and the Review Engine for GP practices pull it together.