Reference architecture · Illustrative scenario, fictional business
Inbound voice receptionist with booking, triage and human escalation for a dental practice
A voice agent that answers every call, books and reschedules through the practice system, recognizes urgent cases and hands them to a person, with a per-minute cost model and a pilot plan.
Illustrative scenario, fictional business. Quillmere Dental is invented to show how I would design this system; it is not a client. A working prototype of the receptionist exists and is shown live on a call.
Solution architect · Dental practice · Design, not built for a client
Retell
n8n
Practice management API
Design targets
< 800 msVoice response latencyPer conversational turn, measured in the pilot
400 calls / monthSized forA four-chair practice, about 3 minutes per call
≈ $0.11Model cost per minuteRetell published pay-as-you-go example, Nov 2026
100%Urgent calls to a personEvery urgent or unclear call is transferred or queued
Context and problem
Illustrative scenario, fictional business. Quillmere Dental is a four-chair practice where the front desk is also the chairside assistant. Calls that arrive during procedures or after hours go to voicemail, and some of those callers book elsewhere. The practice wants every call answered, routine bookings handled, and anything clinical or urgent in front of a person quickly.
Constraints
Patient data. Names, appointment reasons and symptoms are protected health information in the United States, so every vendor that touches them needs the right agreement.
Small team. No in-house IT. Whatever runs must be supportable by one outside consultant and understandable by the office manager.
The practice system is the source of truth. The agent may read open slots and write bookings, nothing else.
Architecture
How to read it. Follow the call from the left. The voice agent handles the conversation; anything that touches the schedule goes through the n8n workflow, which is the only part allowed to read or write appointments. Dashed lines are the fallbacks: transfer to a person, or a message taken for a callback. The highlighted box is the escalation decision, because a receptionist that does not hand off well is a liability.
Call flow
Happy path
The agent greets the caller with the practice name and asks how it can help.
For a booking, it asks for name and date of birth, spells the name back, and offers two open slots from the practice system.
It confirms the slot, writes the booking through the workflow, and repeats date and time before ending the call.
Edge cases
Interruptions. The caller can cut in at any point; the agent stops speaking and listens.
Missing data. If the caller cannot give a date of birth, the agent takes a message instead of booking.
After hours. Bookings still work; anything clinical becomes a callback for the first hour of the next day.
Handoff. Pain, swelling, bleeding or trauma, or a caller who asks for a person, transfers to staff during hours.
Decisions and trade-offs
Retell for the voice layer, n8n for the tools. The agent only talks; every action on the schedule goes through an n8n workflow that can be logged, tested and switched off without touching the voice agent. Rejected: letting the voice agent call the practice system directly, which spreads credentials and logic across two vendors.
Self-hosted n8n. n8n documents that self-hosted workflow data stays on your own infrastructure, and documents no BAA for its cloud service. Rejected: n8n Cloud for a workflow that carries patient details.
Reference IDs in staff alerts. Slack supports HIPAA use only on Enterprise plans with a signed BAA, which a four-chair practice is unlikely to have. Staff alerts carry a call reference and a callback number; the details stay in the call log. Rejected: posting call summaries to a team chat.
Governance and cost
Compliance posture
Retell: its documentation requires a signed BAA before any protected health information passes through the platform, and states there is no fee to sign it. Confirm at signing which plan and settings it covers, and turn on PII redaction and the shortest recording retention.
Practice system: Open Dental publishes a REST API and expects integrators to have a BAA with the practice. Dentrix integrations go through the Henry Schein One API Exchange and its vendor review, so a Dentrix practice should plan for that approval time.
n8n: self-hosted on infrastructure covered by the practice’s own agreements.
Cost model
Component
Rate (published, Nov 2026)
Retell voice infrastructure
$0.055 per minute
LLM (a small, fast model)
about $0.025 per minute
Text to speech
$0.015 per minute
US telephony
$0.015 per minute
Total
about $0.11 per minute
At 400 calls a month and about 3 minutes per call, that is roughly 1,200 minutes, or about $130 a month in voice costs, before hosting for the workflow. Retell bills the whole call including silence, and prompts above 4,000 tokens increase billed time.
Two levers that reduce it: keep the prompt short and move reference material into the workflow, and transfer early when the call is clearly for a person instead of letting the agent try.
Failure modes
What breaks
How it is detected
Fallback
Practice system API is down
Workflow call fails or times out
Agent takes a message; booking becomes a callback
Voice latency spikes
Turn latency above target in call logs
Shorter responses, then transfer to staff
Name or date misheard
Caller corrects the spell-back
Second attempt, then a message for staff
Agent misses an urgent case
Weekly review of a call sample
Tighten escalation keywords; review threshold
Outcome
Design targets, not results: response under 800 ms per turn, sized for 400 calls a month at about $0.11 per minute, and every urgent or unclear call reaching a person.
What I would measure in a pilot
Calls answered: at least 95% of calls answered by the agent or staff, against the voicemail rate before.
Booking accuracy: every agent booking checked by staff for the first two weeks; zero wrong slots to continue.
Escalation: every call flagged as urgent in the weekly review was transferred or queued; any miss pauses the pilot.
What comes next
Reminders and confirmations on outbound calls, once inbound has run cleanly for a month and the practice is comfortable with the escalation rules.