Fixed quote after a free call

Missed-call text-back for dental practices

When the front desk is checking a patient in, the phone loses. We build a workflow that texts every missed caller back within seconds, offers your online booking link or a call-back, sorts the reply and puts anyone mentioning pain, swelling or trauma at the top of the staff list. A typical build costs $1,000 to $2,500 and goes live in about three to four weeks.

The problem

Why missed calls cost dental practices new patients

A dental front desk answers the phone while greeting patients, taking payments and fielding questions from the treatment rooms. At the busiest moments, calls ring out, and a new patient who reaches voicemail often simply calls the next practice on the map.

Some of those calls matter more than others. An existing patient asking to move a hygiene visit can wait an hour; a patient with a swollen face cannot. A missed-call workflow has to tell the difference, without ever trying to give clinical advice.

What we build

What our dental missed-call text-back includes

Instant text-back

A short, friendly text from your practice number to any missed caller during or after hours, with your booking link and a reply option.

Reply sorting

Replies are sorted into new patient, reschedule, cost or insurance question, and possible dental pain, using your own wording.

Urgent first

Anything that mentions pain, swelling, bleeding or trauma is flagged to staff straight away and answered with your emergency instructions, never with advice.

Call-back list

A simple list (in your PMS task list, a shared sheet or Slack) of who still needs a call, cleared as staff work through it.

Out-of-hours rules

Different messages for lunch, evenings and weekends, plus a holiday mode the office manager can switch on.

Opt-out handling

STOP and other opt-out replies are recorded and honoured across every workflow that texts the patient.

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

    Call missed

    Your phone system or Twilio reports a missed call from a mobile number.

  2. 02 Automated

    Text sent

    Within seconds the caller gets a text with your booking link and a "reply here" option, using wording you approved.

  3. 03 Automated

    Reply sorted

    The reply is classified. Possible dental pain goes to the top of the list with your emergency instructions.

  4. 04 Staff review

    Staff call back

    Front-desk staff see the queue, call back or book directly in the practice system.

  5. 05 Dentist or owner decides

    Clinical questions

    Anything clinical is answered by a dentist or follows your emergency process. Nothing clinical is answered automatically.

How it behaves

How the missed-call system behaves

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

What the patient sees

  • A text from the practice number within about a minute of the missed call
  • A booking link and the option to reply
  • Your emergency instructions straight away if they mention pain or swelling
  • A call back from the front desk when they asked for one

What staff see

  • One call-back list, newest and most urgent first
  • Who replied, what they asked and whether they booked
  • A holiday switch and quiet-hours rules they control

What the automation does

  • Detects the missed call and checks opening hours and opt-outs
  • Sends the approved text and sorts the reply
  • Flags urgent words, logs everything and clears the list when a booking appears

Edge cases and fallbacks

Caller is on a landline
No text is possible, so the number goes straight onto the call-back list.
Caller has opted out
No text is sent; the call goes on the list for a person to decide.
Same person calls three times
One text only, with the repeat calls noted on the list.
Twilio or the workflow is down
Calls still reach voicemail as before, and an alert tells the practice manager.
Reply is unclear
It goes to staff unsorted rather than being guessed at.

Architecture

Missed-call text-back for a dental practice at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Missed call Practice number n8n workflow Hours and rules Text-back Twilio SMS Reply sorting Urgent or routine Front desk Call-back list Practice system Booked or noted
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 A call to the practice number goes unanswered, and the phone system reports it to the workflow.
  2. 2 n8n checks opening hours and holiday mode, then sends an approved text with the booking link.
  3. 3 When the caller replies, the message is sorted. Mentions of pain, swelling, bleeding or trauma are flagged first.
  4. 4 Front-desk staff work the call-back list and book in the practice system. Clinical questions go to a dentist.

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.

Missed-call text-back & booking requests project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Phone system, practice system, opening hours, emergency process and the wording your team already uses.

  2. 02

    Design

    2 to 3 days

    Message templates, urgent keywords, call-back list location, opt-out handling and consent notes.

  3. 03

    Build

    About 1 week

    Twilio number or phone-system hook, n8n workflow, reply sorting and the call-back list.

  4. 04

    Shadow run

    About 1 week

    Runs alongside your team: texts go to a test phone while staff compare every reply with what they would have done.

  5. 05

    Launch

    1 to 2 days

    Switch on for real callers, walk the team through the list and the holiday switch.

  6. 06

    Support

    Ongoing

    Stabilization window, then optional monthly care for wording changes and monitoring.

What it runs on

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

n8n Twilio Programmable Messaging Your phone system (missed-call webhook) Open Dental API or Dentally API Google Sheets or Slack for the call-back list Claude or OpenAI for reply sorting

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

    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. Twilio (number, messages and US A2P 10DLC registration) and your n8n plan or server are billed to you directly, not marked up.

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
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: TCPA healthcare text rules

The FCC exemption for healthcare texts to mobile numbers is narrow: free to the patient, limited to purposes such as appointment confirmations and reminders, 160 characters or less, at most one message a day and three a week, with "STOP" opt-out honoured immediately. Marketing texts need prior express written consent. We design to the stricter reading and you confirm with your counsel.

Source: www.law.cornell.edu

US: opt-out requests

Since April 11, 2025, opt-outs made by reasonable means (such as replying "stop") must be honoured within a reasonable time, not more than ten business days. Our workflows record them at once.

Source: www.kelleydrye.com

US: A2P 10DLC registration

Anyone sending application texts to US numbers from a 10-digit long code must register for A2P 10DLC, so we include registration in the plan.

Source: www.twilio.com

US: HIPAA business associates

A vendor that handles patient information for you needs a written business associate agreement. Twilio requires a signed BAA and HIPAA-eligible products before any PHI flows.

Source: www.twilio.com

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

Missed-call text-back & booking requests questions, answered.

It goes to mobile numbers that called your practice. In the US we keep it to booking and appointment purposes, within the limits of the FCC healthcare exemption and your own consent records, and we never add promotions. In the UK and EU we treat it as a service message and keep marketing out of it.

The reply is flagged to the top of the staff list and the patient gets your own emergency instructions, such as your emergency line or out-of-hours service. The system never gives clinical advice or decides how urgent a problem is on its own.

Most VoIP phone systems can report missed calls by webhook or email, and Twilio can sit in front of your existing number with call forwarding. We confirm the exact route on the free call before quoting.

It sends your online booking link or offers a call-back. Writing appointments straight into the practice system is possible with some systems (through the Open Dental or Dentally APIs, or NexHealth Synchronizer), but we usually start with staff booking so nothing double-books.

You pay Twilio for the number and messages and your n8n plan or server directly. For a single practice that is usually a small monthly amount, and we show you the expected usage before launch.

We log every missed call, text, reply and booking. Watch the share of missed callers who reply, the share who book and how long urgent replies wait for a call-back. We do not promise a number before we have seen your call volume.

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