AI Receptionists and Answering Services for Dental Offices: What to Check Before You Sign

The phones ring through lunch, two calls roll to voicemail before anyone is at the desk, and the front-desk chair that opened in September is still empty. Then a vendor demo books a pretend new patient into a pretend schedule without a single stumble, and the contract is in your inbox by the afternoon. Half the team says "none of the AI stuff, please". The other half just wants the phone answered.

This guide is the check that sits on the IT side of that decision: the phone routing, the software permissions, the patient data and the exit door. It does not rank vendors. It gives you a comparison table, a routing table, an access table, a 15-item before-you-sign checklist, a cost comparison built on federal wage data, and a two-week pilot scorecard. If you want someone to own the phone, network and software layers together, that is the job of dental IT support that coordinates your phone, software and vendors. Facts that change were checked on 30 October 2026.

Answering service, AI receptionist or hybrid: what's the difference?

A live dental answering service is a call center whose agents follow your script, take messages and, on some plans, book appointments. An AI receptionist is voice software that understands the caller, answers common questions and, when connected to your practice software, books or moves appointments itself. A hybrid puts software first and hands harder calls to a person.

The difference that matters to IT is not the voice on the line. It is what each model touches: your phone numbers, your schedule and your patients' information. The table compares the three from that side.

Define two terms before any demo. Overflow means calls the office cannot pick up within a set number of rings. After-hours means calls outside the hours you publish. Starting with one of those two, rather than every call, keeps the first test small.

How do calls get to the service? Routing your phone system must support

Calls reach the service because your phone system forwards them under rules you set: overflow after a number of rings, after-hours on a schedule, or every call. Keep your main number with your own phone provider, forward to the vendor's number, and make sure staff can transfer calls back to the office.

Ask the vendor for a routing diagram before you sign, and ask whoever runs your phones to confirm each line of it. A cloud phone system usually handles this with time-of-day rules and a ring group; an older on-premise system may need a programming change on site.

Forward, don't port your main number

Porting moves a phone number from one carrier to another. If the vendor asks to take over your main number, ask why. Forwarding gives the vendor the calls without giving it the number, so leaving later is a settings change rather than a carrier transfer. Porting in general, and how to choose the phone system itself, belong to our guide on choosing a dental office phone system.

Practices with more than one office

Groups with two or more offices need a decision on whether calls stay local or pool into one queue. Time zones, different hours and shared doctors all change the rules. For a worked case of day-and-time rules on one phone system, see an example of time-of-week call routing, and for larger groups the DSO IT support guide covers how standards across offices are set.

What access to your practice software does it need?

An answering service that only takes messages needs no access to your practice software. An AI receptionist that books appointments needs a connection that can read the schedule and write to it. Ask for a written list of what it reads and writes, how it connects, and how you switch that access off.

This is the question the forum threads keep circling: has anyone "connected their clinic's phone system to Dentrix?" The phone part is covered in how dental phone integrations connect to the practice software. An AI receptionist goes one step further, because it acts in the schedule rather than only showing who is calling.

Read only versus book and cancel

Writing to your schedule is where small rules matter. A hygiene recall slot, a new-patient exam and a limited emergency exam may each have their own length, provider and chair. Give the vendor your real appointment types and test them in the pilot. A demo booked into the vendor's own sample schedule proves nothing about yours.

How it connects to Dentrix, Eaglesoft or Open Dental

Each practice software vendor has its own route for outside programs, and the answer belongs in the contract, not in a sales call.

• • Open Dental. Its API uses two keys, one from the developer and one for your office. The developer requests read, create or update access for each kind of record. According to Open Dental's API setup page, your office can see which permissions a vendor's key holds but cannot edit them, and can turn the key on or off. The API also needs the office's eConnector service running. Ask to see the key's permissions in your own API setup screen before go-live, and note where the off switch is.
• • Dentrix. Henry Schein One runs an API Exchange for outside vendors. Its page for practices tells you to check its authorized vendor list for the vendor you have chosen and says vendors are subject to a security assessment. Check the list yourself on the day you sign.
• • Eaglesoft. Ask the vendor how it connects to Eaglesoft, whether Patterson has authorized that connection, and which Eaglesoft version it needs. Get the answer in writing.

The servers and workstations underneath each system are a separate job from the booking connection; see Dentrix IT support and Open Dental IT support for that side. If a booking goes wrong, the question of who fixes what is the same one covered in when to call the software vendor and when to call IT.

Logs and who can see them

Ask whether the vendor keeps a log of every booking, change and cancellation it makes, and whether your office manager can see it. When a patient says "the robot cancelled me", you want the log entry, not a guess.

Patient data: BAA, sub-processors, recordings and retention

If the service will hear, record, transcribe or store patient information for your practice, ask for a signed business associate agreement on the exact plan you are buying. Then ask which other companies process the calls, whether recordings train any model, how long data is kept, and who can open it.

A business associate agreement (BAA) is the contract in which a vendor that handles patient information for you agrees how it will protect that information. For the basics, and for why a free or consumer-grade AI tool is a different risk, read when AI tools create HIPAA risk in a dental practice. Have your compliance adviser confirm the BAA fits your practice; this guide does not interpret the rule.

Six data questions to put in writing

1. 1. Is the BAA signed for this plan? Ask whether the BAA covers your tier and not only a higher one, and get the signed copy before the first live call.
2. 1. Who are the sub-processors? An AI receptionist usually relies on other companies for speech-to-text, the language model and hosting. Ask for the list and how you are told when it changes.
3. 1. Do recordings or transcripts train a model? Ask for the answer in the contract, including the model providers behind the vendor.
4. 1. How long is data kept, and how is it deleted? Ask for the retention period for recordings, transcripts and messages, and for written confirmation of deletion when you leave. NIST's Guidelines for Media Sanitization (SP 800-88 Rev. 2, September 2025) is a reasonable reference to ask the vendor about.
5. 1. Who in the vendor can listen? Quality reviewers, trainers and support staff may all have access. Ask how access is limited and logged.
6. 1. How is the vendor portal protected? Insist on multifactor authentication for every login in your office. CISA explains why a second factor protects an account better than a username and password alone (CISA on multifactor authentication). Our password and MFA basics for dental offices covers the office side.

AI vendors add their own security questions: prompt injection, data leaking between customers, and access tokens that never expire. The wider list is in AI security risks in healthcare. When the service goes live, add it to your vendor list and your next risk analysis. For the wider picture, see HIPAA Security Rule changes for dental practices.

Recording notice and consent: get counsel's sign-off

Have counsel approve your greeting and recording process before go-live.

What happens when the vendor or your internet is down?

When the vendor has an outage, calls need somewhere to go: voicemail-to-email, an on-call mobile or a second number. When your office internet fails, a cloud phone system can still apply its forwarding rules, but anything that depends on the office network stops. Decide the fallback in writing and test both cases before go-live.

Vendors talk about uptime; few talk about the minutes when the bot does not pick up. An AI receptionist adds links to the chain: your phone provider, the vendor's platform, its speech and language services, and the connection into your practice software. Any one of them can fail.

Test both failures on purpose

Before the first live day, ask the vendor to simulate an outage on its side and watch where a test call lands. Then unplug the office internet for five minutes during a quiet hour and call the main number from a mobile. Write down what the caller heard. Our guide on what to do when the dental office internet is down covers the office side of that test, and the dental backup and disaster recovery checklist covers what happens to the practice software itself.

What the vendor should tell you

Ask how you hear about an outage (status page, email, text), whether the vendor will move calls to a backup path itself, and whether any credit applies. Do not accept a guarantee in place of a fallback: a credit on next month's invoice does not answer a patient with a swollen face late at night.

The before-you-sign checklist

Fifteen items cover what the vendor demos tend to skip. Print the list, go through it with the vendor and whoever runs your phones and software, and keep the answers with the contract.

The exit items matter more than they look. Phone and patient-engagement vendors change owners, prices and terms; a contract you can leave cleanly is worth more than a discount for a longer term. The same habit applies to every technology contract, and our list of questions to ask before signing a dental IT contract uses it for IT providers.

What does it cost compared with a front-desk hire?

Answering services and AI receptionists are priced per minute, per call, per conversation or as a flat monthly plan, so the honest comparison is your own call volume against each unit. For scale, the U.S. median wage for receptionists was $18.27 an hour in May 2025 (BLS), not counting payroll taxes and benefits.

The U.S. Bureau of Labor Statistics Occupational Outlook Handbook for receptionists gives a median of $18.27 an hour and $38,010 a year (May 2025), and $19.00 an hour in healthcare and social assistance (page modified 29 October 2026). The annual figure is about $3,170 a month in wages alone. That is not the full cost of an employee, and a receptionist does far more than answer the phone, so treat it as a yardstick, not a like-for-like price.

One published price, worked through

As one example, one phone vendor's dental answering-service article (published 7 August 2026, updated 22 October 2026) lists its AI product at "$99 per month" for 100 conversations, then $1.50 for each conversation after that (Nextiva's published price, read 30 October 2026). This is not a recommendation; it is the shape most AI pricing takes.

Costs that are not on the price page

• • Set-up and integration. A fee for connecting to your practice software, or a higher tier that includes it.
• • Your phone system changes. New forwarding rules, ring groups or a second number from your phone provider.
• • Staff time in the first month. Reviewing bookings, fixing appointment types and listening to calls.
• • Minimum terms. Annual contracts and auto-renewal can cost more than the monthly difference between two vendors.

Run a two-week pilot before you commit

A two-week pilot on a slice of your calls, usually after-hours or overflow only, shows what a demo cannot. Measure the answered-call rate, correct bookings, transfers to staff, emergency handoffs and patient complaints, and agree with the vendor before you start what result means you keep it.

Run the pilot on your real phone system, with your real appointment types, while your team still answers the main line. Review a sample of calls with the vendor at the end of each week. The scorecard below is the one to fill in.

If the team said "everyone in the office is against" it, include them in the review. They hear the callbacks and fix the bookings, so their notes are the most honest data you will get.

What to ask your IT provider about an answering service or AI receptionist

Your IT provider is not choosing the vendor for you. It should check that the phones, network and practice software can support what the vendor promises, and that the access you grant is the access you meant to grant.

How Legend Networking can help

Legend Networking has 22+ years in dental IT (since 2004) and supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy (see Eaglesoft IT support for the server and workstation side). This guide is written from that vantage point (the network, software and contracts around the phone). The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews.

An answering service or AI receptionist rides on the layers an IT provider already looks after: the office network, the workstations, the practice software server, backups and the accounts your team logs in with. This guide stays on those checks. The helpdesk is staffed 24/7 at 1-800-794-1588.