Patient reviews strategy: volume, velocity, response
Run hospital online reviews as an operating process built on four numbers: volume, velocity, recency and response. Ask every eligible patient through a consented post-visit message, never offer incentives, gate by sentiment or set staff quotas, reply to every review without disclosing care, and feed recurring themes back to unit heads.
I have argued before that Google reviews are the hospital’s real front desk. This piece is the operating manual behind that idea: how to run hospital online reviews as a steady process, week after week, without breaking platform rules or patient trust.
The model has four parts: volume, velocity, recency and response. Each one needs an owner, a measure and a routine. And all of it sits inside what Google’s policies allow, which is narrower than many hospitals and agencies assume.
This is part of my complete playbook on local SEO for hospitals. For the wider question of what reputation management covers beyond reviews, read what hospital reputation management is.
The four numbers behind hospital online reviews
I track four things per location and, where it applies, per doctor profile. None of them needs a paid tool to start; the platform dashboards and a simple sheet are enough.
- Volume: the total number of reviews on each profile. It signals to patients that the rating is based on real experience, not a handful of opinions.
- Velocity: how many new reviews arrive each month. A steady flow looks and is more genuine than a burst followed by silence.
- Recency: how recent the latest reviews are. Patients read the newest reviews first and treat old ones as history.
- Response: the share of reviews that get a reply, and how quickly. This is the only one of the four you fully control.
I deliberately do not set a target star rating. Chasing a rating pushes teams towards exactly the behaviours Google forbids. Instead, the goal is a steady, honest flow of reviews and a consistent, humane response to every one of them.
What Google’s review policies forbid
Most review problems I have seen in hospitals come from well-meaning shortcuts. Google’s Maps user-generated content policy is explicit, and the lines that matter for hospitals are these:
- No incentives: no payment, discounts, free goods or free services in exchange for posting a review, or for changing or removing a negative one. A free follow-up consultation “for a review” is an incentive.
- No gating: you cannot discourage negative reviews or selectively solicit positive ones. Sending the review link only to patients who rated you well on a survey is selective solicitation.
- No pressure on the premises: you should not require or pressure patients to leave ratings or reviews while they are at the hospital.
- No staff quotas or scripted content: the policy names requesting staff to solicit a certain number of reviews, or reviews with specific content, including content naming a staff member.
- No conflict of interest: reviews from current or former employees, contractors or others with a professional or personal affiliation are not allowed.
What is allowed is simple. Google’s tips on getting more reviews encourage businesses to ask customers to review through a link or QR code, and to reply to reviews. Ask everyone, offer nothing, and let patients say what they want.
In India, the Bureau of Indian Standards has also published IS 19000:2022 on online consumer reviews, a voluntary framework aimed at platforms that publish reviews. It is a useful reference for integrity and transparency. This article is not legal advice; check specific questions with your counsel.
Designing the review request flow
Volume and velocity come from one thing: asking every eligible patient, consistently, at the right moment, through a channel they have agreed to. In practice that means an automated message after the visit rather than a request at the counter.
Consent first
WhatsApp’s business messaging policy allows a business to contact people only if they have shared their number and given opt-in permission to receive messages from it. The Digital Personal Data Protection Act, 2023 and the DPDP Rules notified in November 2025 add obligations on notice and consent for personal data, with phased compliance. Capture the opt-in at registration, and read my notes on DPDP consent for hospital marketing before building the flow. This is not legal advice.
Moments and rules
- Define the moments: after an OPD consultation is completed and billed, after a day-care procedure, and after discharge from an inpatient stay.
- Define exclusions in advance, by circumstance, never by expected sentiment: for example, a bereavement, an ongoing critical-care admission or a patient who has opted out. Write the list down and apply it to everyone.
- Send one message, once: a short WhatsApp or SMS with the review link for the exact location or doctor profile, sent a few hours after the visit or the day after discharge.
- Do not chase: at most one polite reminder, then stop.
- Keep a light on-site option: a QR code at the exit or on the discharge folder is fine, as long as nobody stands over the patient.
- Route problems separately: give every patient the same review link plus a direct line to the patient relations team, so anyone with a complaint can also reach a person.
The mechanics of automating this sit comfortably inside a post-visit journey, which I describe in automating patient follow-up after an OPD visit, using the setup in the WhatsApp Business API for hospitals.
An example message
Example only. “Thank you for visiting Example Hospital, Sector 12 today. If you would like to share your experience, you can post a review here: [review link]. If anything did not go as it should have, please call our patient relations desk on [number]; we would like to hear from you directly too.”
Note what it does not do. It does not ask for five stars, name a doctor, promise anything or suggest wording.
Which profile the request should point to
A hospital unit often has a main profile, department profiles and individual doctor profiles. Sending every patient to the main profile builds one strong listing and leaves the rest looking empty. Sending them to a doctor profile builds that doctor’s visibility but may fragment the unit’s.
My rule is to send the patient to the profile that matches what they experienced. An OPD consultation with a named consultant points to that doctor’s profile where one exists and is managed by the hospital. An inpatient stay, a health check or an emergency visit points to the unit’s profile. Keep the mapping in the request system, not in someone’s head.
Two cautions. Never point a patient at a profile for a different location to prop up a weaker unit, because the review will describe the wrong place. And when a doctor leaves, stop sending requests to their profile the same day.
Language matters too. In many cities a meaningful share of reviews arrive in Hindi or a regional language, often typed in Roman script. Reply in the language of the review where your team can do it well, and keep a small set of approved phrases in each language so tone and privacy rules hold.
Response SLAs and who owns them
Response is where most hospitals fall down, because nobody owns it after office hours or across units. Google’s own guidance asks businesses to reply in a professional, polite and timely way, and to protect customer privacy. I turn that into three internal rules.
- Every review gets a reply: positive, negative and neutral, on every profile including doctor profiles.
- Negative reviews have a faster clock: set your own service levels, with negatives answered within the working day and positives within a few days, and publish them internally.
- Escalations have a named route: anything alleging a clinical error, a safety issue or discrimination goes to the quality or medical administration team the same day, before any public reply.
In a group, the unit’s patient relations lead usually owns replies, with a central digital team monitoring every profile and stepping in when a unit misses its clock. The profile-level mechanics are in managing Google Business Profiles across hospital units.
Response templates by complaint type
Templates save time but only if they are a starting point. Each reply should be personalised, short and free of any detail that confirms someone was a patient or describes their care. These are illustrative outlines for a fictional Example Hospital.
| Review type | What the reply does | Example opening |
|---|---|---|
| Waiting time | Acknowledges the wait, explains nothing clinical, offers a direct contact | “We’re sorry the wait was longer than it should have been…” |
| Billing or TPA delay | Acknowledges the frustration, points to the billing desk by name and number | “Delays in claim approval are stressful, and we want to help…” |
| Staff behaviour | Apologises for the experience described, commits to looking into it privately | “This is not the experience we want anyone to have…” |
| Clinical outcome allegation | Neutral, brief, moves offline after escalation; never debates care in public | “We take concerns like this seriously and would like to speak with you directly…” |
| Positive | Thanks the reviewer without repeating clinical details they mentioned | “Thank you for taking the time to write…” |
| Not a genuine patient review | Polite, factual, invites contact; report separately through the platform | “We’re unable to find a record matching this, and would welcome a call…” |
For the “not genuine” case, be careful even with “we have no record of you”, since that itself says something about who is or is not a patient. A neutral invitation to call is safer. Never reply in anger, never threaten legal action in public, and never ask a reviewer to remove a review in exchange for anything.
Handling fake, abusive and conflicted reviews
Hospitals do receive reviews that break policy: competitors, former employees with a grievance, abusive language, or reviews meant for another hospital. The right route is the platform’s own reporting process, with evidence, not a public argument.
The same rules apply in reverse. Do not ask staff, their families or vendors to post reviews, even genuine ones about their own care, because the conflict-of-interest rule covers employment and professional relationships. And do not buy review management services that post on your behalf. If a vendor’s method involves accounts it controls, you are buying fake engagement.
Reviews as operations data
The most valuable use of hospital online reviews is inside the hospital, not on the profile. Every review is unprompted feedback from a patient or family, tagged by location and often by department.
I ask teams to tag each review by theme (wait time, billing, cleanliness, staff behaviour, communication, food, parking) and send a short monthly theme summary to each unit head. When the same theme repeats, it is an operations problem, and no reply template will fix it. That loop is what turns review work into reputation, and it is why I treat reviews as part of reputation management rather than as a marketing channel.
A weekly and monthly review checklist
This is the routine I would hand to any unit’s patient relations lead on day one.
- Daily: read new reviews on Google and every directory profile; reply or escalate per the service levels.
- Weekly: confirm the request flow is sending, check opt-out handling, and spot-check a few replies for tone and privacy.
- Weekly: report any policy-violating reviews through the platform, with notes.
- Monthly: record volume, velocity, recency and response rate per profile; tag themes; send the unit head a one-page summary.
- Quarterly: audit the request flow against Google’s policies, check that no exclusion is based on expected sentiment, and refresh templates.
Reviews also live on healthcare directories and local search engines, each with its own rules; I compare those in Practo, Justdial and Google: where patients actually search. For doctors setting up their own profiles, the Google Business Profile optimisation template for doctors includes the review settings and reply routine. The setup notes are in Google Business Profile for doctors.
Questions people ask
Hospital online reviews are the ratings and written feedback patients and families post about a hospital, its units or its doctors on platforms such as Google Maps, healthcare directories and local search engines. Managing them well means a steady, policy-compliant flow of genuine reviews, a timely and private-by-default reply to every one, and using the themes they reveal to fix problems inside the hospital.
No. Google’s Maps policy prohibits offering incentives such as payment, discounts, free goods or free services in exchange for posting a review, or for changing or removing a negative one. Reviews posted because of an incentive can be removed. The same applies to lucky draws or gifts tied to reviewing. Ask everyone genuinely, offer nothing, and let the patient decide.
No. That is review gating, and Google’s policy says businesses must not discourage negative reviews or selectively solicit positive ones. If you run a satisfaction survey, the review invitation must go to every eligible patient regardless of their score. Exclusions are acceptable only when they are defined in advance by circumstance, such as a bereavement, never by expected sentiment.
Not in the way many hospitals set them. Google’s policy names requesting that staff solicit a certain number of reviews, or reviews with specific content including a staff member’s name, as prohibited. Staff also should not pressure patients to review while on the premises. Measure the request flow and response quality instead, and let automated post-visit messages do the asking.
Mainly people time and messaging. A patient relations lead or team spends daily time reading and replying, with escalation support from quality and medical administration. Messaging costs depend on your WhatsApp or SMS provider and volumes. There is no cost for reviews themselves, and there must never be, since paid or incentivised reviews breach platform policy.
Set your own service levels and hold teams to them. My preference is that negative reviews get a reply within the same working day and positive ones within a few days, with clinical or safety allegations escalated internally before any public reply. Consistency matters more than speed alone: every review, on every profile, gets a considered, private-by-default response.
Yes, and it helps, but follow the same privacy rules as the hospital. Never confirm that the reviewer was your patient, never discuss diagnosis or treatment in public, and move any concern to a private conversation. If the hospital’s patient relations team manages your profile, agree who replies and how escalations reach you. Keep replies short and courteous.
That no template implies a clinical judgement, admits or denies clinical fault, or discloses anything about a patient’s condition or care. The reviewer should also confirm the escalation route for clinical allegations is clear, so those reviews reach quality or medical administration before a public reply. Marketing owns tone; clinicians and quality own anything touching care.
Report it through the platform’s own process with whatever evidence you have, such as no matching visit or clear signs it refers to another hospital. Reply publicly only with a neutral, brief invitation to call, without saying whether the person was a patient. Do not argue, threaten legal action in public or ask the reviewer to remove it in exchange for anything.
Yes. WhatsApp’s business policy requires that people have shared their number and opted in to receive messages from your business. India’s DPDP Act and Rules add notice and consent obligations for personal data, with phased compliance. Capture a clear opt-in at registration and honour opt-outs. This is not legal advice, so confirm your consent wording with counsel.
Track four numbers per profile each month: total reviews, new reviews per month, the age of the latest reviews, and the share replied to within your service levels. Alongside them, track themes by tag and whether repeated themes are falling after operational fixes. Avoid a star-rating target, which pushes teams towards shortcuts the policies forbid.
They should not. Google’s policy treats content based on a conflict of interest, including current or former employment and contractual or professional relationships, as not allowed. That applies even when a staff member was genuinely treated at the hospital. Tell staff clearly, in onboarding and in writing, that they must not review their employer or colleagues.
Standardise the policy, request flow, exclusions, templates and service levels centrally, then give each unit’s patient relations lead ownership of replies for that unit’s profiles. A central digital team monitors every profile, reports monthly by unit and steps in when a unit misses its clock. Theme summaries go to each unit head so fixes happen locally.
A short monthly view by unit: review volume and velocity, response rate within service levels, the top recurring themes and what has been done about them. The most useful signal for leadership is whether repeated complaint themes decline after operational changes. That turns reviews from a marketing metric into evidence about patient experience across the group.
Read my takes first in Google Search
