An AI receptionist for dental practices that stays on your facts
We build an AI assistant for your website, text line or phone that answers routine questions from your practice's own approved answers, takes booking requests and captures messages out of hours. It tells people they are talking to an automated assistant, never gives clinical advice and hands anything urgent or clinical to your team. Projects typically cost $2,500 to $7,500 and take five to eight weeks.
The problem
What an AI front desk for a dental office should and should not do
Most calls and chats to a dental practice are the same dozen questions: opening hours, parking, whether you take a particular insurance plan or scheme, new-patient availability, costs and how to reschedule. Each one takes a front-desk member away from the patient in front of them.
An assistant can take that load, but only if it is narrow. It must answer from the practice's own approved wording, never guess at clinical questions, and pass anything about pain, swelling, bleeding or trauma straight to a person or your emergency instructions.
What we build
What our AI receptionist for dentists includes
Approved answer library
Hours, location, fees, accepted plans, new-patient process and policies written and approved by the practice, and the only source the assistant answers from.
Website chat and text line
A small chat widget on your site and, optionally, the same assistant on a text number or WhatsApp.
Booking requests
Collects name, preferred times and reason for visit, then creates a request for staff or offers your online booking link.
Urgent and clinical hand-off
Clinical questions and urgent symptoms trigger your emergency instructions and a staff alert, not an AI answer.
Clear AI disclosure
The assistant says it is automated at the start and offers a person at any time.
Transcript review
A simple admin view of conversations and a weekly review list of questions it could not answer.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Question asked
A visitor asks on your website, text line or phone.
-
02
Automated
Answer from your library
The assistant answers only from your approved answers and links to the source page.
-
03
Automated
Booking request
For appointments it collects details and creates a request or offers your booking link.
-
04
Staff review
Staff confirm
The front desk confirms booking requests and replies to anything the assistant could not answer.
-
05
Dentist or owner decides
Clinical questions
Anything clinical or urgent goes to a dentist or your emergency process. The assistant never decides.
How it behaves
How the AI receptionist behaves
What the patient sees
- A clear note that they are talking to an automated assistant
- Short answers taken from your own approved wording, with a link
- A booking request form or your booking link
- A person or your emergency instructions whenever they ask something clinical
What staff see
- New booking requests to confirm
- Urgent and clinical messages flagged at once
- A weekly list of questions the assistant could not answer
What the automation does
- Matches the question to the approved answer library
- Refuses clinical questions and hands over
- Logs every conversation for review
Edge cases and fallbacks
- Question not in the library
- The assistant says it does not know and offers a person; the question goes on the review list.
- Patient describes symptoms
- No advice; emergency instructions and a staff alert.
- Abuse or spam
- The conversation is closed politely and logged.
- AI provider outage
- The widget falls back to a simple contact form.
- Out of hours
- Booking requests are queued for the morning and the patient is told when to expect a reply.
Architecture
An AI receptionist for a dental practice at a glance.
- Input
- Logic and services
- AI step
- Data
- Output
- People
How it flows
- 1 A patient asks a question on the website, by text or on the phone and is told they are speaking with an automated assistant.
- 2 The assistant service retrieves the matching approved answers and passes them, with fixed rules, to the language model.
- 3 Routine questions are answered with a link to the source; booking requests are collected for staff or sent to your booking page.
- 4 Urgent or clinical messages go straight to staff with your emergency instructions, and every conversation is logged for review.
Project planner
How the project runs, phase by phase.
AI receptionist & website assistant project plan
Typical time to launch: about 6 weeks, then support
-
01
Discovery
About 1 week
Collect real questions from calls, emails and chats, agree what the assistant may and may not answer.
-
02
Answer library
About 1 week
Write and approve the answers with your team, including emergency and out-of-hours wording.
-
03
Build
About 2 weeks
Chat widget or text line, retrieval, booking request, hand-off alerts, logging and admin view.
-
04
Test
1 to 2 weeks
A test set of real questions plus tricky and clinical prompts; staff sign off before launch.
-
05
Launch
2 to 3 days
Soft launch on part of the site or out-of-hours only, then widen.
-
06
Support
Ongoing
Weekly transcript review at first, then monthly updates to the answer library.
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 answer library
Real questions collected, answers written and approved.
$500 – $1,200
-
Build
Assistant service, chat widget or text line, retrieval, hand-off and admin view.
$1,200 – $4,000
-
Integrations
Booking page or practice system, alerts and messaging.
$300 – $1,000
-
Testing and evaluation set
Real, tricky and clinical prompts tested before launch.
$300 – $900
-
Launch and training
Soft launch, transcript review and team walkthrough.
$200 – $400
-
Total project estimate
$2,500 – $7,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A voice line costs more to build and run than website chat. Model usage and telephony are billed to your accounts 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.
- AI model usage: Billed by the provider per use; for short sorting and drafting steps usually a small monthly amount at practice volumes.
- Messaging or voice: Twilio messaging at the published per-message rates if you add a text line; a voice line costs more to run than web chat.
- Hosting: n8n Cloud from about €20 a month, or your own server.
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.
EU: tell people they are talking to AI
Article 50 of the EU AI Act requires AI systems that interact with people to be designed so people are informed they are interacting with an AI system. It applies from 2 August 2026. We add the disclosure everywhere, wherever you are.
Source: artificialintelligenceact.euUS: HIPAA vendor agreements
Any vendor that receives patient information on your behalf needs a written business associate agreement. We only route patient details through providers that will sign one, or keep the assistant free of patient data.
Source: www.law.cornell.eduEU and UK: health data is special category
Questions about symptoms are health data under Article 9 GDPR and UK GDPR, so the assistant collects as little as possible and data stays with contracted processors.
Source: gdpr-info.euFree 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
AI receptionist & website assistant questions, answered.
No, and ours is built not to. It answers practical questions from your approved answers. Anything clinical, and any mention of pain, swelling, bleeding, trauma or breathing problems, goes to a person or your emergency instructions.
Yes. It says so at the start and offers a person at any time. In the EU this disclosure is a legal requirement under the AI Act from 2 August 2026, and we treat it as good practice everywhere.
It can collect a booking request or send patients to your online booking page. Writing appointments directly into the practice system is possible with some systems, but we start with staff confirming requests until the assistant has a track record.
It can say which plans or schemes you accept and explain your process, from wording you approve. Questions about a patient's own coverage or estimate go to the front desk.
Compliance depends on the vendors and how data flows, not on a label. We map every system that would touch patient data, use providers that sign a BAA or processor contract, minimise what is collected and give you a written data-flow summary.
We set up transcript logging and a weekly list of questions it could not answer. Measure how many conversations end without a staff hand-off, how many booking requests it captures and what patients ask that is missing from the answer library.
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