Fixed quote after a free call

Dental CRM automation for your new-patient pipeline

New-patient enquiries arrive by phone, web form, chat, Facebook and Instagram, and most practices track them in a spreadsheet or not at all. We connect every source to one pipeline in a dental CRM such as DenGro or a general CRM such as HubSpot, move each enquiry through clear stages from first contact to booked treatment, automate the follow-ups and reminders, and send a weekly report on which sources bring patients who book. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why dental practices lose new-patient enquiries

A new-patient enquiry is the most valuable message a practice receives, and the easiest to lose. It might arrive as a missed call, a web form at midnight, an Instagram message or a chat on the website, and each lands in a different inbox.

Without one pipeline nobody can say how many enquiries came in last month, how many were called back, how many booked a consultation or which advert or listing brought them. Follow-up depends on whoever happens to remember.

What we build

What our dental CRM automation includes

Every source in one place

Web forms, missed calls, website chat, Facebook and Instagram lead forms and email enquiries flow into one CRM pipeline.

Clear pipeline stages

New enquiry, contacted, consultation booked, treatment plan presented, accepted, scheduled and completed, matched to how your team works.

Automatic follow-ups

A first reply within minutes, then reminders for staff and polite follow-ups for patients who have not booked, with stop rules.

Task reminders for staff

Call-back tasks and due dates for the treatment coordinator, so no enquiry sits untouched.

Practice system link

Booked patients matched to the practice system through its API or integration route, so the pipeline knows who actually attended.

Source reporting

A weekly email showing enquiries, bookings and accepted treatment by source and treatment type.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry arrives

    A form, call, chat or social lead creates or updates a contact in the CRM.

  2. 02 Automated

    First reply

    The patient gets an approved acknowledgement and booking link within minutes.

  3. 03 Automated

    Stage moves

    Bookings, plans and payments move the deal through the pipeline automatically where the systems allow.

  4. 04 Staff review

    Coordinator follows up

    The treatment coordinator calls, answers questions and records the outcome.

  5. 05 Dentist or owner decides

    Treatment decisions

    Treatment options and plans are set by the dentist with the patient, never by the CRM.

How it behaves

How the dental CRM pipeline behaves

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

What the patient sees

  • A quick acknowledgement and booking link after they enquire
  • A call from the treatment coordinator if they asked for one
  • A couple of polite follow-ups at most, stopping once they book

What staff see

  • One pipeline board with every enquiry and its stage
  • Call-back tasks with due dates
  • A weekly report by source and treatment type

What the automation does

  • Captures and de-duplicates enquiries from every source
  • Moves stages when bookings or plans change
  • Sends follow-ups and creates tasks with stop rules

Edge cases and fallbacks

Same patient enquires twice
Matched by phone or email and merged into one contact.
Existing patient fills in the new-patient form
Flagged to staff instead of creating a duplicate deal.
Lead form arrives without consent ticked
Gets the acknowledgement only; no marketing follow-up.
CRM API limit or outage
Enquiries are queued and retried, and staff get an alert.

Architecture

A dental CRM pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Web and chat Forms, live chat Calls Missed and answered Social leads Facebook, Instagram n8n Capture and dedupe Dental CRM DenGro or HubSpot Follow-ups Text and email Coordinator Calls and tasks Weekly report By source
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from web forms, chat, calls and Facebook or Instagram lead forms.
  2. 2 n8n captures each one, removes duplicates and creates or updates the contact and deal in the CRM.
  3. 3 Approved follow-ups go to the patient and call-back tasks go to the treatment coordinator.
  4. 4 A weekly report shows enquiries, bookings and accepted treatment by source.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Dental CRM & new-patient pipeline automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Enquiry sources, current tracking, pipeline stages, CRM choice and reporting needs.

  2. 02

    Design

    2 to 3 days

    Stage definitions, follow-up rules, field mapping, consent and duplicate rules.

  3. 03

    Build

    1 to 2 weeks

    Source connections, CRM pipeline, follow-ups, tasks and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Enquiries flow into the CRM while staff keep their old process, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over, train the coordinator and front desk.

  6. 06

    Support

    Ongoing

    New sources, stage changes and reporting tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n DenGro (dental CRM) HubSpot CRM API Facebook and Instagram lead forms Open Dental API, Dentally API or NexHealth Synchronizer Twilio SMS and your email provider

Cost estimate

What it costs, line by line.

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

    Sources, stages, field mapping and reporting.

    $200 – $400

  • Build

    Capture, de-duplication, pipeline automation and follow-ups.

    $500 – $1,300

  • Integrations

    CRM, lead forms, practice system and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with your current tracking.

    $100 – $250

  • Launch and training

    Switch-over and coordinator training.

    $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. CRM subscriptions, messaging and n8n are billed to you directly. Several sources or a two-way practice-system link may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM subscription: Your CRM vendor's own plan (DenGro, HubSpot or the CRM you already use).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: marketing texts need consent

Follow-up texts that promote treatment are marketing and need prior express written consent; appointment-related messages have narrower rules.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

US: HIPAA and CRM vendors

A CRM that stores patient information for a covered practice needs a business associate agreement; if the CRM will not sign one, we keep clinical details out of it.

Source: www.law.cornell.edu

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.

FAQ

Dental CRM & new-patient pipeline automation questions, answered.

A dental CRM tracks enquiries and potential patients from first contact to booked treatment. It sits between your marketing and your practice management system, which still holds appointments and clinical records.

Dental-specific CRMs such as DenGro are built around new-patient enquiries and connect to some UK practice systems. General CRMs such as HubSpot are flexible and have a documented API. We help you pick based on your sources, practice system and budget, and we can work with a CRM you already have.

Usually, through the vendor's API or an integration platform: Open Dental and Dentally have APIs, Dentrix and Ascend connect through Henry Schein One's API Exchange of authorised vendors, and NexHealth Synchronizer covers systems including Dentrix, Eaglesoft, Open Dental and Curve Hero. We confirm the route for your system before quoting.

Partly. The follow-ups and source reporting are marketing automation, but the core is making sure every enquiry gets a fast, consistent reply and a person follows up. Promotional messages only go to patients who agreed to receive them.

No. Each sequence has a few messages at most, stops as soon as the patient books or replies, and respects opt-outs across every workflow.

Enquiries by source, time to first reply, share contacted, consultations booked, treatment accepted and which sources bring patients who book. We set the CRM up to report these from day one.

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.

Book a free 20-minute call