Review requests and reputation for dental practices, done the right way
We build a workflow that asks every patient for a review after their visit, in the same way, with your Google review link. New reviews are flagged to the team, and reply drafts are written to never confirm someone is a patient or mention their care. Staff approve every reply. A typical build costs $1,000 to $2,500 and takes about three weeks.
The problem
Why dental review requests need rules
Patients choose a dentist partly on reviews, and most happy patients never think to leave one. Asking consistently is the fix, but it is easy to slip into practices that break the rules, such as asking only the patients you expect to be happy.
Replying is the other risk. A dental practice that answered online reviews with patient names, treatment and insurance details paid $23,000 to settle with the US Office for Civil Rights in 2022. A reply workflow has to make that mistake hard to make.
What we build
What our dental review management includes
Ask everyone the same way
One review request after each completed visit, sent to every patient who agreed to be contacted, not filtered by how happy they seem.
Your review link
A direct link to your Google review form, plus other platforms you use.
New review alerts
New reviews posted to Slack or email so the practice manager sees them the same day.
Privacy-safe reply drafts
Draft replies that thank the reviewer and invite them to contact the practice, without confirming they are a patient or mentioning any care.
Feedback route for everyone
Patients can also send private feedback to the practice manager, offered to all patients alongside the review link, never instead of it.
Monthly summary
Requests sent, reviews received and themes worth discussing at the team meeting.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Visit completed
The appointment is marked complete in the practice system.
-
02
Automated
Request sent
The patient gets one review request with your Google review link, if they agreed to be contacted.
-
03
Automated
Review posted
New reviews are detected and posted to the team channel.
-
04
Staff review
Reply approved
A draft reply is prepared; the practice manager edits and approves every one.
-
05
Dentist or owner decides
Complaints
Concerns raised in a review are handled through your complaints process by a person.
How it behaves
How review requests behave
What the patient sees
- One message after their visit asking for a review, with your Google link
- The option to send private feedback too, offered to everyone
- No repeated nagging
What staff see
- New reviews in Slack or email the same day
- A draft reply that never confirms someone is a patient
- A monthly summary of requests, reviews and themes
What the automation does
- Checks contact consent after each completed visit
- Sends the same request to every eligible patient
- Picks up new reviews and prepares drafts for approval
Edge cases and fallbacks
- Patient complained during the visit
- They are still asked like everyone else; the complaint follows your complaints process.
- Review mentions treatment details
- The draft reply still says nothing about care; the manager decides any follow-up offline.
- Fake or abusive review
- Flagged to the manager, who can report it through Google's own tools.
- Patient opted out of messages
- No request is sent.
Architecture
Review requests and replies for a dental practice at a glance.
- Input
- Logic and services
- Output
- AI step
- People
How it flows
- 1 A completed visit in the practice system starts the workflow, which checks the patient agreed to be contacted.
- 2 Every eligible patient gets the same review request with your Google review link.
- 3 New reviews are picked up and a short, privacy-safe reply is drafted.
- 4 The practice manager edits and approves each reply; complaints go through your complaints process.
Project planner
How the project runs, phase by phase.
Review requests & reputation project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Current review profile, contact consent records, complaints process and reply tone.
-
02
Design
2 to 3 days
Request timing and wording, reply rules, alert channel and summary contents.
-
03
Build
About 1 week
n8n workflow, review link, review monitoring, reply drafts and alerts.
-
04
Test
2 to 3 days
Requests sent to staff phones, reply drafts checked against the privacy rules.
-
05
Launch
1 to 2 days
Switch on for completed visits and walk the manager through approvals.
-
06
Support
Ongoing
Optional monthly care for wording and new platforms.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Process mapping, wording, data flows and the written specification.
$200 – $400
-
Build
The n8n workflow, logic, AI step and error handling.
$500 – $1,300
-
Integrations
Practice system, phone or messaging and alert channels.
$150 – $400
-
Testing and shadow run
QA against acceptance criteria and a side-by-side run with your team.
$100 – $250
-
Launch and training
Switch-on, team walkthrough and run book.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Messaging and n8n costs are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing). US A2P 10DLC registration fees also apply.
- n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).
- AI model usage: Billed by the provider per use; for short sorting and drafting steps usually a small monthly amount at practice volumes.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
No review gating
Google's policy does not allow businesses to discourage or prohibit negative reviews, selectively solicit positive reviews, or offer incentives for reviews. We ask every patient the same way.
Source: support.google.comUS: FTC rule on reviews
The FTC's final rule bans incentives for reviews that express a particular sentiment and certain review suppression practices.
Source: www.ftc.govUS: HIPAA and review replies
In 2022 a California dental practice paid $23,000 after replying to Yelp reviews with patient names, treatment and insurance details. Our reply drafts never confirm someone is a patient.
Source: www.hipaajournal.comFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Review requests & reputation questions, answered.
No. Google's policy does not allow selectively soliciting positive reviews or discouraging negative ones, and it bans incentives for reviews. The workflow asks every patient who agreed to be contacted, the same way.
No. Google does not allow incentives for reviews, and the FTC rule bans incentives tied to a particular sentiment. Asking politely and making it easy is what works.
Briefly, politely and without confirming the person is a patient or mentioning any care. Invite them to contact the practice manager directly. The drafts follow that rule and a person approves every reply.
We do not set it up that way. Replies are public and carry legal risk, so a person approves each one.
Yes. Google's review policy applies everywhere, and in the UK and EU patient confidentiality and data protection rules lead to the same rule for replies: never reveal patient information.
Requests sent, reviews received per month, average time to reply and recurring themes. We do not promise a star rating.
Free 20-minute call
Want this for your dental practice?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for dental practices
All servicesDental CRM & new-patient pipeline automation
Capture every enquiry from web, phone, chat and social into one dental CRM pipeline, with follow-ups, reminders and a weekly report on where new patients come from.
From $1,000 · About 4 weeks Details
Missed-call text-back & booking requests
Text every missed caller back within seconds with a booking link, sort the reply and put urgent pain calls in front of staff first.
From $1,000 · About 3 to 4 weeks Details
Hygiene recall, reactivation & treatment-plan follow-up
Build recall lists from your practice system, send reminders by each patient's preferred channel and pass lapsed patients and unbooked treatment plans to a person.
From $1,000 · About 4 weeks Details