Case Study

Case Study: Dental Practice CRM & Patient Automation

We built a connected set of automations for a general and family dental practice: a new-patient pipeline in a CRM, missed-call text-back, hygiene recall and reactivation, online intake with insurance prep, and review requests. The front desk now works from one set of lists instead of four inboxes, and the dentists only see what needs a clinical decision.

Practice type
General and family dentistry
Team involved
Practice manager, front desk, treatment coordinator, dentists
Systems connected
Practice management system, phone system, CRM, Google Business Profile, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

The front desk was answering the phone while checking patients in and out. At the busiest times calls rang out, and nobody could say how many of those callers were new patients.

New-patient enquiries arrived by phone, web form, email and social messages and were tracked in a spreadsheet when someone had time. Follow-up depended on memory.

Recall reminders went out once from the practice system. Patients who did not respond were only noticed when someone ran an overdue report, which was rarely.

Medical history forms were filled in on paper in the waiting room and insurance was checked on the day, so the first appointment of a session often started late. Reviews were asked for occasionally, and replies had no written rule about what could be said.

Goals

What the project had to change

  • Every missed caller gets a response within minutes, and urgent replies reach a person first.
  • Every new-patient enquiry lands in one pipeline with a clear next step and an owner.
  • Patients who miss a recall reminder are followed up and, if needed, called by a person.
  • Medical histories and insurance details are ready before the patient arrives.
  • Every patient is asked for a review the same way, and every reply follows a privacy-safe rule.

What we built

What we built, as one connected system.

01

New-patient CRM pipeline

We connected web forms, website chat, missed calls and social lead forms to one CRM pipeline with stages from new enquiry to completed treatment, automatic acknowledgements, coordinator tasks and a weekly source report.

Service details
02

Missed-call text-back

Missed calls from mobiles now get an approved text with the booking link. Replies are sorted, and anything mentioning pain or swelling goes to the top of the staff list with the practice's emergency instructions.

Service details
03

Recall and reactivation

A nightly list of patients due or overdue, reminders in each patient's preferred channel, up to two follow-ups, then a personal call list for the front desk. Unbooked treatment plans get a gentle check-in.

Service details
04

Online intake and insurance prep

Forms go out three days before each appointment, reminders chase missing ones, the dentist sees a short summary of what changed, and staff get a day-before list of missing forms and unverified insurance.

Service details
05

Review requests

One request after each completed visit to every patient who agreed to be contacted, new-review alerts, and privacy-safe reply drafts the practice manager approves.

Service details

Architecture

How the practice's workflows connect

Phone system Missed calls Web and social Enquiries Practice system Appts and recalls n8n Five workflows AI sorting Replies, summaries CRM pipeline Stages and tasks Texts and emails Twilio, email Front desk Lists, approvals Dentist Clinical review Log and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Missed calls, web and social enquiries, and appointments and recalls from the practice system feed one n8n instance.
  2. 2 Five workflows update the CRM pipeline, send texts and emails, and use an AI step to sort replies and summarise form changes.
  3. 3 The front desk works one set of lists and approves review replies; the dentist reviews medical history changes.
  4. 4 Every step is logged, and a weekly summary shows the measures the practice agreed to track.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What patients see

  • A text back within about a minute when their call is missed
  • A quick acknowledgement and booking link after an online enquiry
  • Recall reminders in their preferred channel, then a personal call instead of endless messages
  • Forms to complete at home before the visit
  • One polite review request after their appointment

What staff see

  • One call-back list, one pipeline board and one day-before list
  • Urgent replies flagged first
  • Draft review replies to approve
  • A weekly report on enquiries and bookings by source

What the automation does

  • Sends, sorts, reminds and chases on schedule
  • Applies opt-outs, quiet hours and consent across every workflow
  • Logs every step and alerts the practice manager if anything fails

Edge cases and fallbacks

A caller is in pain
The reply triggers the practice's emergency instructions and a staff alert; nothing clinical is answered automatically.
A patient opts out in one workflow
One shared opt-out list stops texts from every workflow.
The practice system is unreachable overnight
The recall run is skipped and retried rather than sent from stale data.
A form write-back fails
Staff get a clean PDF and the failure is logged and retried.
Twilio or n8n has an outage
Calls still reach voicemail, forms can still be completed at the desk, and the practice manager gets an alert.

Integrations

What we connected

All integrations

Open Dental

Practice management

Appointments, patients and recalls for reminders, intake write-back and reporting.

Open Dental's REST API, under a BAA with the practice.

NexHealth Synchronizer

Integration platform

One API to read and write patients, appointments, insurance and forms across supported systems, with webhooks.

Synchronizer API and webhooks.

DenGro

Dental CRM

New-patient enquiries, pipeline stages and nurture messages for UK and Irish practices.

DenGro's integrations, including its Dentally and EXACT links, confirmed per project.

HubSpot

CRM

Contacts, deals, pipeline stages and follow-up tasks.

HubSpot's CRM REST API.

Google Business Profile

Reviews and local search

Booking link, review requests and new-review alerts.

Google Business Profile settings and APIs.

Twilio

SMS and voice

Missed-call text-back, reminders and opt-out handling.

Twilio Programmable Messaging and Voice APIs, under Twilio's BAA for PHI.

Slack and Microsoft Teams

Staff alerts

Urgent replies, new reviews and failure alerts.

Incoming webhooks and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We shadowed the front desk, mapped phone, enquiry, recall, intake and review steps, agreed emergency wording and data flows, and the practice signed vendor agreements.

  2. 02

    Design and access

    Week 2

    Message templates approved by the practice, pipeline stages, consent and opt-out rules, read access to the practice system, Twilio number and A2P 10DLC registration.

  3. 03

    Sprint 1: missed calls

    Week 3

    Built and shadow-ran the missed-call workflow with texts going to a test phone; demo and sign-off.

  4. 04

    Sprint 2: CRM pipeline

    Week 4

    Missed calls went live. Connected enquiry sources to the CRM pipeline and set up coordinator tasks.

  5. 05

    Sprint 3: recalls

    Week 5

    The pipeline went live. Built the recall workflow; staff checked the daily list before any reminder was sent.

  6. 06

    Sprint 4: intake

    Week 6

    Recalls went live for one recall type. Built intake forms, change summary and the day-before list.

  7. 07

    Sprint 5: reviews

    Week 7

    Intake went live for new patients. Built review requests, alerts and reply drafts.

  8. 08

    UAT and handover

    Week 8

    The team ran user acceptance testing on every workflow, then we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Texts missed callers and sorts their replies
  • Captures every enquiry into the CRM and creates follow-up tasks
  • Builds recall and lapsed-patient lists every night
  • Sends reminders and forms, and chases the ones not returned
  • Summarises what changed in a medical history
  • Detects new reviews and drafts privacy-safe replies

The team does

  • Call back missed callers and book appointments
  • Work the pipeline and answer treatment questions
  • Call lapsed patients
  • Verify insurance eligibility and fix missing details
  • Approve every review reply before it is posted

Dentist or owner decides

  • Answers anything clinical, including urgent replies
  • Sets and changes recall intervals
  • Reviews medical history changes and decides what they mean
  • Approves clinical wording in templates

Compliance handled

Privacy, consent and safety, built in.

No clinical advice by text or chat

Nothing clinical is answered automatically. Urgent words trigger the practice's emergency instructions and a staff alert.

Texting rules in the US

Reminders stay within the FCC healthcare exemption limits; anything promotional needs prior express written consent and lives in a separate flow.

Source: www.law.cornell.edu

Opt-outs across every workflow

One shared opt-out list is checked before any text is sent, well inside the ten-business-day limit.

Source: www.kelleydrye.com

Vendor agreements before any patient data

Every vendor that touches patient data signed a BAA or processor contract before go-live; Twilio requires a signed BAA and HIPAA-eligible products.

Source: www.twilio.com

Review replies that reveal nothing

Drafts never confirm someone is a patient, and a person approves every reply.

Source: www.hipaajournal.com

No review gating

Every eligible patient is asked the same way, with no incentives.

Source: support.google.com

Security rule changes

The proposed HIPAA Security Rule update is not final (HHS expects final action no earlier than July 2027), so we built to the current rule and kept MFA and encryption on regardless.

Source: www.paubox.com

Outcomes

What changed for the practice

  • Missed calls from mobiles now get a text back within about a minute, day or night.
  • Every new-patient enquiry lands in one pipeline with an owner and a next step.
  • Recall reminders and follow-ups go out automatically, and lapsed patients reach a person instead of falling through.
  • Most medical histories and insurance details are ready before the patient walks in.
  • Every patient is asked for a review the same way, and replies follow one privacy-safe rule.
  • The front desk works from one set of lists instead of four inboxes and a spreadsheet.

What we track

The measures the practice watches.

Missed-call response

Share of missed callers who reply to the text and the share who book.

Pipeline conversion

Enquiries by source, consultations booked and treatment accepted.

Urgent call-back time

How long replies flagged as possible pain wait before a person calls back.

Recall bookings

Recalls due, reminders sent and bookings made from reminders each month.

Forms ready before the visit

Share of appointments with completed forms and verified insurance the day before.

Reviews

Requests sent, reviews received and average time to an approved reply.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • Missed-call module

    Text-back, reply sorting and the call-back list.

    $700 – $1,700

  • Recall and reactivation module

    Nightly lists, reminders, follow-ups and plan check-ins.

    $800 – $2,000

  • Intake module

    Forms, chasing, change summary and the day-before list.

    $800 – $2,000

  • Reviews module

    Requests, alerts and reply drafts.

    $500 – $1,300

  • CRM pipeline module

    Source capture, stages, tasks and the weekly report.

    $700 – $1,600

  • Integrations

    Practice system, CRM, Twilio and Google Business Profile connections.

    $200 – $400

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every practice gets its own fixed quote after a free call.

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), plus A2P 10DLC registration fees.
  • n8n: Free self-hosted Community edition on the practice's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM: The CRM vendor's own plan.
  • Form tool and AI usage: The form provider's plan and pay-per-use AI model fees, usually small 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
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built 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.

Book a free 20-minute call