She picks up when you can’t.
Zaha is designed to answer your practice’s calls when your team is with patients in the chair — after hours, on weekends, during lunch, and during peak times. Trained on dental workflows. Discloses it’s AI. Hands off to a human when it should.
What Zaha is designed to do — and what it isn’t.
We’ve watched AI voice-agent marketing overpromise and crater trust. Zaha’s pitch is the opposite: a narrow, dental-trained scope with explicit handoff rules. Here’s what that means.
Handle the routine calls that shouldn’t interrupt your team.
- Greet callers and identify itself as an AI receptionist, every call, always.
- Answer common FAQs: hours, address, accepted insurance, directions.
- Book, reschedule, and cancel appointments for practices with calendar sync enabled.
- Follow up on cancellations with rebooking options, so the slot doesn’t stay empty.
- Configure per location for multi-location practices and DSOs, with per-site greetings and routing rules.
- Send SMS or email confirmation after the call — subject to TCPA consent on record.
- Log every call with transcript and recording to your dashboard.
Everything a dental receptionist decides, not looks up.
- Diagnose dental pain, assess urgency, or give clinical guidance — these route to a human immediately.
- Quote prices, confirm insurance coverage, or discuss treatment plans.
- Handle complaints, billing disputes, or anything the caller asks to speak with a human about.
- Pretend to be human. If asked, Zaha confirms it’s an AI — always.
- Replace your team. Zaha is designed to catch calls that would go to voicemail, not the ones where a human should pick up.
Illustrative transcript — not an actual customer call. The handoff is the design: when a caller is in pain, asks for a person, or the call drifts outside Zaha's trained scope, the call routes to the practice's on-call queue with the transcript attached.
When Zaha can’t help — or when a caller asks for a person — the call routes to your practice line or voicemail with full context logged. The handoff is the product, not a fallback.
The AI discloses itself every call, always — and hands off the moment a caller asks for a person, or the call drifts outside what the AI was trained to handle.
Twenty to thirty calls go unanswered every week. Most never leave voicemail.
Some try the practice down the street. Some are new patients who were ready to book but wanted to talk to a human first. A few were after-hours emergencies. Zero of them are on your books.
The predictable part is that most of these missed calls happen in windows your team already knows about. Evenings and weekends, when an emergency search sends a patient to whoever picks up. Lunch, when the front desk is covering for whoever's at the chair. The 3 PM pickup surge, when a stacked appointment schedule is colliding with every caller at once.
A voicemail greeting doesn't fix this. Seventy-to-eighty percent of callers won't leave one, and the ones who do are the ones who already knew they wanted to call back — not the ones deciding between you and another practice in the next five minutes. The missed call is the cheapest new-patient acquisition failure a practice can have, because the patient is already halfway through the door.
Zaha is a voice agent for those specific windows. Not a receptionist replacement. Not a 24/7 omniscient AI. A narrow, dental-trained AI that answers the calls your team can't pick up, discloses it's AI on every call, books into the practices that want it to book, and hands off to a human when the call is something only a human should handle. ~80% of the phone-line workload that's currently going to voicemail is routine enough to be handled this way. The rest stays with your team.
24 hours to go live on basic call answering.2 About a week for the full workflow.
Zaha plugs into your existing phone number through a forwarding rule. No new hardware. No ripping out your PMS. Most practices have Zaha answering after-hours calls by day two — full calendar sync and peak-time coverage layer in over the first week.
Quick onboarding form
You provide practice credentials, phone-routing rules, hours, and accepted insurance. Zaha is typically configured with a basic greeting and FAQ responses within 24 hours.
Day 1 · Basic go-liveTune the call flow
Your onboarding specialist reviews your call volume, tunes Zaha’s response library to your providers and services, and configures your human-handoff rules.
Day 2–4Connect calendar & PMS
Zaha syncs with Google Calendar or with Dentrix, Eaglesoft, Open Dental, or other supported PMS for direct booking. Eligible practices go deeper; others stay on confirmation-mode.
Day 4–5Expand coverage
Most practices start with after-hours only, review a week of transcripts, then expand to lunch and peak-time overflow. Coverage scope is in your control throughout.
Day 5–7Every call, logged. Every transcript, searchable. Every handoff, documented.
Open the dashboard and see what happened while your team was with patients. Calls answered, appointments booked, calls handed off to humans, calls where the caller hung up before engaging — all logged with transcript and recording.
…and other major dental practice management systems. Calendar integration is offered to practices that meet operational readiness criteria during onboarding. Multi-location practices and DSOs supported with per-site configuration.
If Zaha doesn’t find missed calls in your practice, we buy lunch.3
We’re confident your practice has a missed-call problem — most do. If during your trial Zaha detects no significant call leakage, we’ll buy lunch for your entire team, up to $150 via Uber Eats or DoorDash. That’s how sure we are this pays off.
Three practice owners describe what Zaha actually does on their phone lines.
What changed once Zaha was live on the overflow — in the words of the teams using it.
“I wanted the AI disclosure. Patients appreciate knowing they’re talking to a bot that can actually book them an appointment at 9 PM, versus a human who’s going to call them back at 10 AM tomorrow. The disclosure is the feature.”
Individual result — not a guarantee of similar outcomes for other practices.
“We went live with after-hours only and looked at the transcripts for a month. Once I saw the handoff was working — Zaha was actually routing the hard calls to us, not faking its way through — I opened it up to lunch and peak times.”
Individual result — not a guarantee of similar outcomes for other practices.
“Our after-hours voicemails used to be a graveyard. Now they’re booked appointments on my Monday morning schedule. The dashboard tells me who called, what they wanted, and whether Zaha closed the loop or kicked it back to us.”
Individual result — not a guarantee of similar outcomes for other practices.
The questions practice owners ask before they let AI touch their phone line.
The questions practices actually ask before putting a voice agent on their main line.
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.
Zaha runs on the same rails as the rest of the front desk.
One patient contact record. One consent history. One dashboard. Explore the modules Zaha integrates with — or see the full mConsent platform.
Call Zaha. Ask it something. See what it does.
The fastest way to know whether Zaha is right for your practice is to call the demo line and have a conversation. Two minutes. No form. No sales pitch.
mConsent operates as a Business Associate under HIPAA and executes a BAA with each customer. SMS confirmations, reminders, and follow-ups are subject to TCPA and require patient consent. AI voice agents can fail, misinterpret speech, or route imperfectly — Zaha is designed to route to your configured human handoff when it cannot help. Individual practice results vary; product displays are illustrative. Dentrix, Dentrix Ascend, Eaglesoft, Open Dental, Dolphin, and Google Calendar are trademarks of their respective owners, used with attribution, no affiliation implied. Specific integration capabilities, pricing, and service terms are defined in your Master Services Agreement.
