By Industry

View all industries

Have questions? Give us a call. Our team is happy to help: (469) 812-5544

Call our team

Product Categories

Have questions? Give us a call. Our team is happy to help: (469) 812-5544

Call our team

Scenarios

View all use cases

Have questions? Give us a call. Our team is happy to help: (469) 812-5544

Call our team

Library

Have questions? Give us a call. Our team is happy to help: (469) 812-5544

Call our team
Quick Links
Home/
AI Receptionist/features
Pricing/pricing
Contact/contact
Book a Demo/contact
About/about
Partners/partners
Security/security
Developers/developers
↵ to selectTab to navigateEsc to close

By Industry

DentalOptometryMedicalVeterinaryMedical SpaPlastic SurgeryPhysical TherapyMental HealthPrimary CareView all industries

By Role

Practice OwnersOffice ManagersFront Desk StaffView all roles

Enterprise

Dental Service Organizations (DSO)Medical GroupsVision GroupsVeterinary Chains

Call Management

AI ReceptionistCall RecordingCall IntelligenceMissed Call Text BackVoicemailPhone Porting

Scheduling

Smart SchedulingOnline SchedulingAI ChatbotCalendar SyncWaitlistBooking Widget

Patient Engagement

Two-Way TextingRemindersReview RequestsPatient OutreachRecall & Reactivation

Practice Websites

Practice WebsitesBrowse TemplatesDental WebsitesVeterinary WebsitesMed Spa WebsitesTherapist WebsitesHome Care Websites

Practice Management

Multi-LocationTeam ManagementDigital FormsPaymentsPatient CRM

EHR & Billing

EHR OverviewClinical NotesAI Progress NotesSuperbillsBillingClient PortalTelehealthTherapy EHR

Analytics & AI

Call AnalyticsPractice AnalyticsProvider DashboardCustom AI Voice
AI ReceptionistVirtual Receptionist24/7 Answering ServiceAfter-Hours AnsweringHoliday Call AnsweringMissed Call RecoveryOverflow Call AnsweringVoicemail ReplacementAI Call Answering ServiceAppointment Booking ServicePatient Reactivation CallsPatient Recall & Recare CallsAppointment Reminder CallsPost-Visit Follow-Up CallsOnline Appointment SchedulingHIPAA-Compliant AISpanish-Speaking AIReplace Your Answering ServicePricing vs Answering ServiceCost of an Answering ServiceAnswering Service Pricing GuideView all use cases
Templates & ScriptsIndustry GuidesBlogResultsCase StudiesHealthcare GlossaryIntegrationsChangelog
Tools
Get StartedLog InSales: (469) 812-5544

Verify caller identity before sharing records

Turn on Verify identity before sharing records under Receptionist → AI Voice → Voice tab → What it can do, then save. Before the AI discusses a returning patient's own appointments, balance, treatment or records, it asks for their full name and date of birth and checks them against your records, never reading the date on file aloud. Hours, directions, new-patient booking and messages need no check. After a fourth miss the AI offers a message or one more try; after the fifth it stops trying. Unverified, or with no date of birth on file, the caller hears nothing personal and is offered a message. A verified caller stays verified for the call. With athenahealth connected it is always on (Required). With it off, a client's details only go to a caller ringing from the number on that record.

Updated October 24, 20264 min read

Verify identity before sharing records adds a privacy check to your AI receptionist. Before it discusses a returning patient's own appointments, balance, treatment or records, it confirms it's actually speaking with that person. It's off by default and set per location.

Why you'd use it

Caller ID tells you which phone a call came from, not who is holding it. A spouse, a child or a stranger could be on the line. This setting makes the same identity check happen on every call, without your front desk having to think about it.

Turn it on

  1. Open Receptionist → AI Voice and stay on the Voice tab.
  2. Under What it can do, switch on Verify identity before sharing records ("Require the caller's name and date of birth before the AI discusses any treatment, balance, or appointment details.").
  3. Save. The change applies to the next call.

If athenahealth is connected, the row shows a lock and Required instead of a switch. With a connected EHR the AI can reach live chart details, so verification is always on.

What the caller experiences

  • General questions (hours, directions, services, booking as a new patient, leaving a message) work right away. The AI asks whether the caller has been seen before, and new patients skip the check.
  • When a returning patient asks about their own appointment, balance, treatment or records, the AI asks for their full name and date of birth. FrontDesk checks them on the server and tells the AI only whether they matched. The date of birth on file is never read out.
  • If the details don't match, the AI may ask the caller to spell their name, or for the ZIP code or email on their file. When the AI only needs the year of birth, asking for it doesn't count as a try.
  • After the fourth miss, the AI stops and offers a choice: "That still isn't matching what I have on file. I can take a message and have the team call you back, or we can try one more time."
  • After the fifth miss, verification is locked for the rest of the call: "I'm not able to verify that over the phone. I can take a message or have a team member follow up."
  • If the caller can't be verified, or there's no date of birth on file, the AI shares nothing personal and offers to take a message or have a team member follow up.
  • Once verified, the caller stays verified for the rest of the call.

Returning a staff member's call or leaving a message for someone is message-taking, so the AI doesn't ask for verification. Each attempt, and whether it passed, is recorded on the call in Call Logs. A message the AI takes from a caller it tried and failed to verify shows a Couldn't verify chip in Tasks: confirm who they are before sharing anything when you call back.

When identity checks are off

With Verify identity before sharing records off, the AI doesn't ask anyone to prove who they are, so FrontDesk uses the caller's own number instead:

  • Details from a client's record (their visits, balance, phone, email or last visit) are only shared with a caller ringing from the number on that record.
  • Confirming, rescheduling or cancelling a visit, and texting a payment link, also only work for the number they're calling from.
  • Asked about someone else, by name or by another number, the AI shares nothing, not even whether that person is a client. It says it can't share another person's details over the phone and offers to take a message or have the office call back.
  • A caller who says it's their own account but is on a different phone gets the same offer, or a call back on the number on file.
  • Booking a new appointment, the waitlist, messages and general questions work for every caller.

Like verification, this is enforced on the server. See How the AI handles callers.

With athenahealth connected

Verification is always on. Identity is confirmed against athenahealth's records and needs one more matching detail besides name and date of birth: a phone number on the chart (the number they're calling from counts), the email or the ZIP code. Name and date of birth alone are not enough.

Good to know

  • Protection is enforced on the server. The tools that look up appointments, balances and records refuse to answer until the caller is verified, so a slip in the conversation can't reveal them. The tools that change an appointment's details or text a payment link wait for verification too.
  • Conversation memory has its own Only after identity is verified setting, which controls whether past calls, texts and chats are used before the caller verifies.
  • Outbound calls confirm they're speaking with the right person before discussing specifics. By default the AI asks something like "Am I speaking with…?". With this setting on, it also asks for name and date of birth.

Frequently asked questions

What does the AI ask to confirm someone's identity?
Their full name and date of birth. FrontDesk compares them with the record on the server; the date of birth on file is never sent to the AI or read back to the caller. If the first try doesn't match, the AI may ask the caller to spell their name or give the ZIP code or email on their file.
Can a new patient still book if this is turned on?
Yes. The AI first asks whether the caller has been seen before. New patients go straight to booking or intake with no identity check. General help like hours, location, services, booking a new appointment or leaving a message never needs verification.
What happens if the AI can't confirm someone?
It shares no personal or clinical details. After the fourth miss it says "That still isn't matching what I have on file. I can take a message and have the team call you back, or we can try one more time." After the fifth, verification stops for that call and it offers a message or a team member's follow-up. With no date of birth on file to check against, it offers the same. Each attempt is recorded on the call, and a message from a caller who couldn't be verified shows a Couldn't verify chip in Tasks.
A caller asked about their own account from a different phone. Why wouldn't the AI help?
With Verify identity before sharing records off, nobody on the line proves who they are, so the AI only shares a client's details (visits, balance, phone, email, last visit) with a caller ringing from the number on that record, and only confirms, moves or cancels visits or texts a payment link for that number. From another phone it offers to take a message or have the office call back on the number on file. Turn on Verify identity before sharing records if you want callers on other phones to verify with name, date of birth and one detail on file instead.
Does this work with my EHR?
Yes. With athenahealth connected, verification is always on (the switch shows Required) and identity is confirmed against athenahealth's records. It needs the name, date of birth and one more detail that matches the chart: the phone number (the caller ID counts), the email or the ZIP code. Without an EHR, the AI checks the patient records in FrontDesk.
Does the caller have to verify again later in the call?
No. Once verified, the caller stays verified for the rest of the call.
Is identity verification required for HIPAA?
HIPAA requires reasonable safeguards and "minimum necessary" handling of protected health information, but it doesn't mandate one specific method. This setting helps you apply the same identity check on every call. Whether to turn it on is up to you, unless an EHR is connected.

Was this article helpful?

Related articles

Still need help?

Our team replies fast. Or just ask the in-app Setup Assistant.

Contact support