A dental concierge that answers at 2am and books by procedure

A voice assistant for dental practices that picks up when the front desk cannot — at lunchtime, after six, on a Sunday. It takes the caller through intake, captures insurance and the reason for the visit, and books against the live calendar. The part that matters most is the least visible: it allocates the slot the procedure needs, so a root canal gets the long block and a cleaning gets the short one, and a fifteen-minute scale-and-polish stops landing in an hour of surgical time. Turn-taking stays under a second and a half, which is the difference between a conversation and a walkie-talkie.

A dental practice group

The client

A dental practice group

Industry
Healthcare & dental
Size
Multi-site practice

Challenge

The phone rang at lunchtime and at nine at night

Dental clinics were losing up to 30% of potential new patients due to busy phone lines during peak hours and unreturned after-hours voicemails. Front-desk staff were overwhelmed by repetitive scheduling calls, leading to double bookings, missing patient intake data, and a fragmented experience where medical information was often absent from initial appointments — costing an average of 15 minutes per patient in re-collection.

A patient looking for a dentist is usually looking at a list of them, and the practice that picks up is the one that gets the appointment — so a missed call at 1pm is rarely a call that comes back. The client needed a voice assistant that felt human and empathetic but operated with digital precision, handling insurance verification, procedure-specific slot allocation, and intake capture that meets the practice's own privacy obligations.

Solution

It knows a root canal needs a longer slot than a cleaning

We deployed a low-latency 'Voice-to-Calendar' pipeline using a medical LLM fine-tuned on dental terminology. The assistant interacts with patients via natural speech, captures intake information (insurance, symptoms, preferences), and connects directly to the clinic's scheduling software via secure webhooks for real-time slot validation and confirmation.

To mirror a premium clinic experience, we implemented 'Contextual Patient Recognition.' Returning patients are greeted by name with appointment history context. New patients follow a structured onboarding flow capturing insurance details, primary concerns, and scheduling preferences before the AI suggests optimal time slots based on procedure duration.

Calls we would still defend

  • Procedure-Aware Scheduling — Engineered dynamic slot filtering that allocates longer blocks for root canals and extractions, shorter for cleanings — preventing the common problem of 15-minute cleanings booked into 60-minute surgical slots.

  • Sub-1.5s Conversational Latency — Used WebSocket-based audio streaming with Groq inference to keep turn-taking under 1.5 seconds, eliminating the robotic 'walkie-talkie' feel of older voice bots.

  • Patient vault, encrypted at rest — a Supabase-backed store that keeps captured intake data, insurance details and notes ready for staff review before the appointment, encrypted with AES-256 and partitioned by row-level security so one practice cannot read another's.

Results

The front desk got its afternoons back

Before

30% of calls missed during lunch breaks and after 6 PM. Manual calendar management causing double bookings. Front-desk staff spending 60% of time on phone scheduling instead of patient care.

After

Calls answered at 2am and through lunch, not only when the desk is free. Double-bookings gone, because availability is read off the calendar rather than remembered. Front-desk time back on the patients who are actually in the building. Practice grew 20% without hiring.

100%

Calls Answered Outside Desk Hours

Every after-hours call answered instead of going to voicemail

35%

After-Hours Booking Increase

More bookings captured outside desk hours than before

98%

Scheduling Accuracy

Bookings written to the calendar with the right slot length

FAQ

The questions this one raises

What was actually built, the constraints it had to meet, and what we would do differently.

  • Yes. The assistant operates 24/7/365, allowing patients to book appointments, reschedule, cancel, or ask questions at any time — including weekends, holidays, and overnight. After-hours bookings increased 45% after deployment.

  • Yes. The system checks the incoming phone number against your patient database to greet returning patients by name and pull up their history. New patients are guided through a structured intake flow capturing insurance, contact details, and clinical concerns before scheduling.

  • It gets a person on the line, quickly. If a caller mentions severe pain, trauma or facial swelling, 'Emergency Priority' logic breaks out of the booking flow, rings the on-call clinician's mobile and holds the earliest emergency slot in the same call. What it does not do is advise. The assistant gives no clinical guidance and is not built to triage — whether swelling is a routine abscess or something involving the airway is a judgement for a dentist, not for a scheduling system. If nobody picks up, the caller is told to seek urgent care rather than left holding a booking.

  • Encrypted in transit with TLS 1.3 and at rest with AES-256, row-level security in the database so one practice cannot read another's records, and no protected health information written into conversation logs. Those are mechanisms and they are ours to state. HIPAA compliance is not one of them: it is not a property a system has, it runs through a Business Associate Agreement between the practice and every vendor that touches PHI, and it covers the arrangement rather than the software. THWorks holds no HIPAA attestation. Any deployment handling real patient data needs that paperwork in place first.

  • Through the APIs the practice management platforms publish — Dentrix and Cal.com are the two this deployment used. We build the connector a practice actually needs rather than shipping a library of them, so a different platform is a piece of integration work whose size depends on what its API exposes. The sync runs both ways, so a slot your staff block out is a slot the assistant will not offer.

Keep reading

Other builds, taken apart the same way

Want to talk about yours?