AI Dental Receptionist That Answers Every Call Your Team Can't Pick Up

Yes. Zaha discloses that it’s an AI receptionist at the start of every call — this is built into the default greeting script and cannot be removed by practices. If a caller asks directly whether they’re speaking to a person, Zaha confirms it’s an AI.

Clear disclosure aligns with emerging state AI regulations (including the Colorado AI Act and California SB 942) and with FTC guidance on AI marketing. We view it as a feature, not a legal checkbox — patients respond better when expectations are set up front.

Zaha is designed to recognize common patient intents in a dental practice context. For anything outside that scope — clinical questions, billing disputes, complaints, treatment-plan discussions, or any caller who asks to speak with a person — the call routes to your practice line, voicemail, or on-call team per your handoff rules.

Every handoff is logged to the dashboard with the reason, transcript, and a callback prompt for your team. Zaha isn’t designed to guess its way through calls it shouldn’t be handling.

Yes. SMS confirmations, reminders, and follow-ups sent by Zaha are subject to the Telephone Consumer Protection Act and require patient consent. mConsent provides opt-in and opt-out tooling to support practice compliance, and Zaha captures verbal consent during the call before sending confirmations by text.

Your practice remains responsible for maintaining valid consent records; mConsent provides the infrastructure to capture, store, and honor opt-outs.

mConsent operates as a Business Associate under HIPAA and executes a Business Associate Agreement (BAA) with each customer. Call audio, transcripts, and any patient information captured during a Zaha conversation are protected under the BAA with administrative, physical, and technical safeguards designed to meet HIPAA requirements, including encryption in transit and at rest.

Zaha’s supporting infrastructure runs on US-based servers. Specifics of data retention, access controls, and audit logging are documented and reviewed during onboarding.

For practices on Google Calendar, Zaha books directly with real-time availability. For practices on Dentrix, Eaglesoft, Open Dental, Dolphin, and other major PMS, calendar integration is offered to practices that meet operational readiness criteria — things like a stable provider schedule, configured appointment types, and a predictable booking workflow. Practices that aren’t ready for full calendar sync start on confirmation-mode, where Zaha captures the booking request and your team confirms in the PMS.

Your onboarding specialist will walk through which mode fits your practice during setup.

Yes. Zaha’s response library is configured per practice, so specialty workflows — orthodontic consultations, oral-surgery referrals, endodontic emergencies, pediatric new-patient intake — are handled with scripts and appointment types specific to your practice. Onboarding reviews your specialty’s call mix and tunes the response library accordingly.

Specialty-specific clinical screening (pain levels, urgency triage) still routes to a human — that’s in the “not designed to do” column and isn’t changed by specialty.

Zaha supports per-location configuration. Each site can have its own greeting, hours, insurance list, providers, and handoff rules — all managed from one central dashboard. Call history and booking analytics roll up at the DSO level so regional directors get a portfolio view, while individual office managers see just their location.

Enterprise deployments (8+ locations) go through our enterprise onboarding track with dedicated rollout support. See the DSO program for enterprise pricing and procurement.

Zaha’s response library is limited to what your practice has approved: your hours, insurance list, providers, services, directions, and booking rules. It’s designed to say “I don’t have that information, let me connect you with the team” rather than fabricate answers outside its scope.

Every call is logged with transcript and audio. If a specific call didn’t go the way it should have, you can review it, flag it, and the response library updates so Zaha handles that scenario correctly next time. The review loop is part of how it improves for your practice specifically.

No. Zaha is designed to catch the calls that currently go unanswered — the after-hours calls, the calls during lunch, the overflow during peak times, and the routine bookings that don’t need a human touch. The calls where a human should answer still go to your team.

Most practices keep their receptionist and free that person up to focus on in-office patients, treatment coordination, and relationships. Zaha is overflow capacity, not a replacement.

Onboarding takes about a week from kickoff to after-hours go-live. Pricing depends on practice size, call volume, and which workflows you enable (after-hours only vs. full-day overflow vs. main-line coverage). A 14-day free trial is available, and after that the month-to-month option can be cancelled with 30 days’ notice — no multi-year lock-in required.

Specific pricing and service terms are defined in your Master Services Agreement with mConsent.

An AI dental receptionist is a voice-based software system that automatically answers inbound patient calls for a dental practice, without a human staff member. It handles common requests such as appointment booking, hours inquiries, directions, and insurance questions using conversational AI trained on dental office workflows. When a call requires human judgment, clinical triage, billing disputes, or a caller requesting a person, it routes the call to the practice's on-call team with a full transcript attached. Zaha AI is built specifically for dental practices and integrates with major PMS for real-time appointment booking.

Every caller is told they're speaking with an AI receptionist at the start of the call, before they've said anything. This disclosure is built into Zaha's default greeting and cannot be removed. If a caller directly asks, Zaha confirms it's AI. Aligns with FTC guidelines and state laws including the Colorado AI Act and California SB 942 - and in practice, patients respond better when expectations are set from the start.