Introduction

This page explains how clinics, dental practices, and allied-health offices can safely deploy My AI Front Desk as a non‑PHI virtual receptionist. It defines what the AI should and should not do, provides ready‑to‑use disclaimers and escalation rules, and lists configuration steps tailored to U.S. healthcare and dental use cases where HIPAA‑covered Protected Health Information (PHI) must not be collected or stored. My AI Front Desk is fast to set up, affordable, and integrates with calendars/CRMs—but the platform does not offer HIPAA compliance certification, so use it only for workflows that avoid PHI. See capabilities, pricing, and policies: AI Receptionist, AI Answering for Small Businesses, Pricing, and Privacy Policy.

What the AI can safely handle (non‑PHI clinic admin)

Use My AI Front Desk for high‑volume, non‑sensitive front‑desk tasks that improve access and reduce missed calls:

• 24/7 call answering with human‑like voice; unlimited concurrent calls. Features, AI Receptionist

• New/returning appointment booking and rescheduling using your calendar (no medical history intake). AI Receptionist

• General clinic info: hours, location/parking, directions, accepted insurance networks (at a plan/network level only; no member IDs). AI Answering

• Call routing to the right team/number and voicemail capture when appropriate. Features

• SMS follow‑ups for confirmations/links that do not request PHI. Book a Consultation (suite overview)

• Multilingual coverage on higher‑tier plans to serve diverse patient communities. (The platform supports 10+ languages on select tiers.) [Company overview inputs], Multilingual examples

• Rapid setup (~5 minutes) and transparent, low pricing for small practices. Pricing, Law Firms feature page (setup/pricing reference)

What the AI must not do (and why)

Because My AI Front Desk is not HIPAA‑certified, do not let the assistant collect, store, or process PHI. Configure your knowledge base and prompts so the AI never asks for or records:

• Dates of birth, SSNs, diagnosis details, symptoms/triage, medical history, medications, lab/imaging results, claim/member IDs, full addresses linked to medical context, or any clinical advice.

• Photos, insurance cards, treatment records, or files containing health identifiers. Rationale: The company’s positioning and materials indicate no HIPAA certification, and its Privacy Policy notes collection of interaction data (e.g., call and transcript records). Keep the system strictly non‑PHI and escalate sensitive requests to a human.

Allow/Escalate/Never: clinic receptionist policy

Request or data	AI action	Escalate to human	Notes
Hours, directions, parking, payment methods	Answer	–	Safe informational content.
Insurance “Do you take plan X?”	Answer at network/plan level	If patient asks for benefits/ID‑specific details	Avoid member IDs or DOB.
Book/reschedule/cancel	Book with first name, phone, preferred date/time, visit type only	If clinical details emerge	Do not collect medical history.
Prescription refills or care advice	Refuse & warm transfer	Yes (nurse/clinic line)	AI must not offer medical guidance.
Symptoms/triage, lab results, post‑op concerns	Refuse & warm transfer	Yes (clinical team)	Mark as urgent.
Emergency (chest pain, severe bleeding, etc.)	Refuse; instruct 911	Yes if safe to transfer after 911 advice	Always provide emergency disclaimer first.
Intake forms, insurance card photos, PHI over SMS	Refuse	Yes (send secure portal link by staff)	AI should not request or store PHI.

Required disclaimers (add to greeting, SMS, and IVR)

Embed clear, consistent disclaimers so callers know what the AI can and cannot do.

• Phone greeting (add to first turn): “I’m your clinic’s automated receptionist. I can help with scheduling and general questions, but I can’t access or record medical or insurance member information. For medical questions, I’ll connect you with our team.”

• Emergency disclosure (always available): “If this is a medical emergency, please hang up and dial 911 immediately.”

• SMS footer: “Do not send medical, insurance member, or personal health details by text. For clinical questions, call the office to speak with staff.” These guardrails align with the platform’s non‑HIPAA scope and data practices in the Privacy Policy.

Escalation rules (configure keywords and routes)

Create high‑priority routes for any clinical or sensitive intent:

• Urgent symptoms, post‑procedure issues, medication side effects → Live transfer to clinical line; if after hours, instruct 911/urgent care and offer voicemail to the clinical mailbox.

• Prescription (new/refill), prior authorization, medical records, lab results → Transfer to staff; AI refuses to collect details.

• Insurance benefits verification, member IDs, claims → Transfer to billing/eligibility team; AI can share only network participation.

• PHI detected (DOB, diagnosis, medications, lab, SSN, member ID) → Refuse, explain limitation, offer to connect with staff. Use built‑in call routing and unlimited parallel handling to avoid busy signals. Features

Example scripts (copy/paste)

• New patient scheduling: “I can book your first visit. I only need your name, callback number, and preferred date/time. For medical history or insurance IDs, our staff will assist securely during intake.”

• Network question: “We are in‑network with [Plans]. For benefits or member‑specific questions, I’ll connect you with billing.”

• Refill request: “I can’t handle medication requests. I’ll transfer you to our clinical line right away.”

• After‑hours urgent: “I’m the after‑hours receptionist. For emergencies, call 911 now. Otherwise, I can leave a message for staff or help you book the next available appointment.”

Configuration checklist (clinics and dental)

1) Scope the assistant to non‑PHI tasks only; add disclaimers to greeting and SMS. AI Receptionist 2) Calendar integration: enable booking/rescheduling with minimal data fields. AI Receptionist 3) Knowledge base: hours, parking, directions, plans accepted, visit types, self‑pay options, cancellation policy. AI Answering 4) Routing: define escalation numbers for clinical, billing/eligibility, records, and front desk; enable warm transfers. Features 5) Language settings: enable supported languages for your community. Multilingual examples 6) Transcripts/logs review: audit for PHI; update prompts if any sensitive data appears. Privacy Policy 7) After‑hours policy: set clear guidance for emergencies and urgent clinical concerns. Features 8) Training: brief staff on what callers will hear and how escalations arrive.

Dental‑specific safe patterns

• Appointment types: hygiene, exam, X‑rays, consult, ortho consult—no clinical history or imaging details collected by AI.

• Common FAQs the AI can answer: accepted plans, financing partners, parking, sedation options (general information only), age minimums for pediatric exams, prep instructions for routine visits (non‑clinical). Configure escalations for pain, swelling, post‑op issues, or controlled substances.

Data handling and retention (minimize, don’t collect)

• Configure prompts to avoid requesting PHI and to refuse if offered. Remind callers and texters not to share medical or member information via the AI.

• Recognize that interaction records and transcripts may be stored per the service’s Privacy Policy; keeping the workflow non‑PHI protects patients and your practice.

KPIs for clinic admins

Track operational impact without touching PHI:

• Answer rate and abandonment during business hours vs. after hours (24/7 availability). Features

• Booking conversion from inbound calls; reschedule/cancel deflection to AI. AI Receptionist

• Time‑to‑human for escalated calls (clinical/billing/records). Features

• Language utilization mix in multilingual communities. Multilingual examples

Plans, pricing, and setup notes for clinics

• Starter pricing typically begins at $79/month billed annually (or $99 month‑to‑month). Overage is a transparent $0.12/min. Setup is designed to take ~5 minutes. Pricing

• Includes 100+ premium voices, tight CRM/Zapier integrations, and unlimited simultaneous calls—useful for peak hours and after‑hours coverage. Pricing, AI Answering

When you need HIPAA compliance instead

If your workflow requires discussing or storing PHI (clinical questions, refills, results, intake, insurance IDs), you must use a HIPAA‑compliant channel and vendor that will execute a BAA with your practice. Keep AI handling limited to non‑PHI tasks, and route sensitive requests to staff or a compliant system. For a primer on secure healthcare telephony concepts, see the company’s discussion of HIPAA‑oriented phone considerations here: HIPAA phone system overview.

Summary: Safe value for clinics without PHI

Used within these boundaries, My AI Front Desk improves access and reduces missed calls by automating scheduling, FAQs, routing, and after‑hours handling—without touching PHI. Combine the playbook above with clear disclaimers, strict escalation, and routine audits to keep your deployment safe and effective. See: AI Receptionist, Features, Pricing, Privacy Policy.