AI Receptionist for Therapy Clinics

First, the disambiguation, because the search results mix two different products. An AI receptionist for therapy clinics handles the front desk: it answers the phone, takes the booking, asks intake questions, sends the confirmation. It is the receptionist your practice would hire if you had the budget, except it works after 5 PM and on Sundays. It is not the same thing as an AI therapy chatbot like Wysa or Woebot. Those are direct-to-consumer tools that talk to the client. The receptionist talks to the caller on behalf of your practice, then hands the actual clinical work to your licensed therapists.

This is the distinction the top vendor pages do not draw clearly. It matters, because the things an AI receptionist should never do in a therapy context are very different from a dental office or a law firm, and the cost of getting it wrong is also different. A confused booking at a dental practice means a rescheduled cleaning. A confused call at a therapy clinic might be a person in crisis.

This guide covers what an AI receptionist for therapy clinics actually does, the things it should never do, the crisis-call protocol the ranking vendor pages skip, the HIPAA + 42 CFR Part 2 layer specific to mental health, the cross-state licensing question the AI needs to handle at intake, and the PMS integrations therapy practices actually use. Operational, not clinical.

Disclaimer. This article is operational guidance for evaluating and deploying an AI receptionist in a therapy or mental-health practice. It is not clinical, legal, or compliance advice. Work with your compliance officer, your licensed clinical staff, and counsel before any deployment that may touch a crisis call or substance-use-disorder records.

What an AI receptionist for a therapy clinic actually does

Five things, no more:

1. Answers the phone, in seconds. Live transfer if the right person is available; full handle if not. Same warm tone at 9 AM as 9 PM.
2. Books, reschedules, or cancels appointments against your PMS calendar, with the therapist's availability and the room (or telehealth link) attached.
3. Runs the structured intake for new clients: name, contact, insurance, referring source, presenting concern in their own words, state of residence, age, and any practice-specific fields you configure.
4. Sends reminders and confirmations by voice, SMS, or email to cut no-shows.
5. Routes the call when the matter is outside its scope, to the right clinician, the billing line, or, in any matter that suggests crisis, directly to an on-call therapist with a 988 fallback (more on this in the crisis section).

That is the entire job. An AI receptionist for therapy clinics does not run assessments, does not score symptom inventories, does not give clinical advice, does not chat about how the last session went. The boundary matters because every step beyond intake puts the practice in territory it has no license to occupy.

What an AI receptionist for therapy should never do

The boundary matters because the receptionist's failure mode in therapy is not a missed booking. It is a caller who mistakes the AI for someone who can give clinical guidance.

• Never give diagnostic suggestions. Not even soft ones. A caller saying "I think I might have ADHD" should be routed to a clinician for a real assessment, not given a hint about what their symptoms might match.
• Never offer treatment advice. No coping techniques, no breathing exercises, no recommendations. That is clinical work.
• Never ask about session content. Avoid "how was your last session?" or "are you feeling better?" These sound friendly and are not the AI's place to ask. They also create a PHI record where one was not needed.
• Never ask medication questions beyond confirming the client knows to bring a current med list to a psychiatric visit if your intake requires it. Dosage, side effects, refills are all clinical.
• Never attempt to provide therapy. No reflective listening scripts, no "tell me more about that," no validation prompts. Even well-meaning therapeutic-sounding responses cross a line the AI is not authorized to cross.
• Never make claims about insurance coverage beyond what is verified in your billing system. "Yes we take BlueCross" is fine; "yes, that visit will be covered" is not, and an AI that improvises here costs you a chargeback or a complaint.
• Never disclose any client information to a caller unless the caller is authenticated as the client themselves and the disclosure is explicitly permitted. This is sharper for mental health than for general medical (see the 42 CFR Part 2 section).

These are not edge cases. A well-configured AI receptionist hits one of these limits in a normal week. Shortlist only vendors that ship these limits hard-coded into the agent. An open-prompt LLM that "sounds friendly" is not safe in a therapy front desk.

Crisis-call protocol: trigger phrases and escalation

The single most consequential configuration in a therapy AI receptionist is the crisis trigger list and what happens when one fires. None of the top-10 SERP results publishes one. Here is the structure to ask every vendor to implement.

The AI listens for trigger phrases in the caller's words. When a trigger fires, the AI moves out of standard intake into a tightly-scripted crisis flow. It does not loop, does not ask follow-up questions that delay help, does not hang up.

A representative trigger map. Refine with your clinical team for your practice; this is a starting frame, not a finished protocol:

Caller signal (sample phrases)	Tier	AI response
"kill myself", "suicide", "end my life", "want to die", "have a plan"	Acute suicide risk	Calm acknowledgment → offer immediate warm-transfer to on-call clinician → if unavailable, state the 988 Suicide & Crisis Lifeline verbatim and offer to text it → log + page on-call therapist
"going to hurt myself", "self-harm", "cutting"	Active self-harm	Warm-transfer to on-call clinician → 988 fallback → log
"going to hurt someone", "want to hurt", named target	Threat to others	Warm-transfer to on-call clinician → 988 fallback for caller safety → log
"I'm in crisis", "I can't cope", "I'm scared"	Acute distress, no expressed plan	Warm-transfer to clinician → if unavailable, expedited callback within X minutes → log
"hearing voices", "seeing things", "I'm not safe in my own head"	Acute psychiatric symptoms	Warm-transfer to clinician → 988 fallback → log
"I've taken too many [pills/anything]"	Possible overdose	911 first, in clear language → stay on line if caller permits → page on-call → log
"He hit me", "I'm being hurt", "I'm not safe" (domestic)	Active domestic violence	Use caller-safe script (no repeat-back of detail), offer National Domestic Violence Hotline (1-800-799-7233), warm-transfer if requested, 911 if immediate

Three configuration rules that matter more than the table:

1. The AI must not loop. A crisis caller hearing "I'm sorry, I didn't catch that, can you repeat?" is the worst possible outcome. Either the AI handles the trigger immediately or it routes immediately.
2. The 988 Suicide & Crisis Lifeline number must be hard-coded as a fallback for every acute risk tier. 988 replaced the older 10-digit National Suicide Prevention Lifeline number in 2022. The AI should also know how to text it.
3. Every crisis flow must produce a record — a logged transcript or summary, a page to the on-call clinician, and an entry your team reviews the next business morning. Mental-health record-keeping under HIPAA and 42 CFR Part 2 is stricter than general healthcare; the AI's logs are part of your record system.

If a vendor cannot show you a configurable trigger list, a warm-transfer mechanism, and a 988 fallback, they are not ready for a mental-health practice. The question is not "does it sound nice on the phone." The question is "what happens at 11 PM on a Sunday when somebody calls in crisis."

HIPAA and 42 CFR Part 2 for mental-health practices

Mental-health PHI sits in a stricter tier than general medical PHI. Two overlapping frameworks apply:

HIPAA is the floor. A Business Associate Agreement (BAA) is required for every vendor that touches PHI, encryption in transit and at rest, audit logs, breach notification within 60 days, minimum-necessary access, patient right to access and amend their record. If you have a general HIPAA-compliant AI receptionist for medical office, the architecture and BAA chain carries over.

42 CFR Part 2 is the addition for any practice that is a "federally assisted" substance-use-disorder (SUD) program. Most independent therapy practices are not technically Part 2 programs, but a practice that holds out SUD treatment as part of its services, accepts SUD-related federal funding, or is part of a larger system that does, often is. When Part 2 applies it is stricter than HIPAA on disclosures: patient consent is required for most disclosures that HIPAA would permit under treatment, payment, or operations. HHS aligned parts of 42 CFR Part 2 with HIPAA in the 2024 rule revisions, but the core stricter-consent posture remains.

Practical operational implications for an AI receptionist:

• The vendor must sign a BAA. No BAA, no PHI touches the system. This is the same bar as any healthcare vendor.
• Sub-processors must also be BAA'd: the LLM provider, the speech-to-text provider, the storage layer. Ask for the BAA chain in writing. (We cover the BAA chain in detail in our AI receptionist for medical office guide.)
• If your practice is dual MH/SUD or potentially a Part 2 program, do not let the AI disclose any client information without explicit, documented consent, even when HIPAA alone would permit it.
• LLM training opt-out must be on. PHI should never be used to train general-purpose models.
• Logs containing PHI are themselves PHI. Audit-log retention, access, and destruction follow your standard PHI policy.

If your compliance officer is not in the procurement conversation, pause until they are.

Cross-state telehealth licensing: what the AI needs to check at intake

Therapists are licensed by state. A caller booking from a state where the therapist is not authorized to practice cannot ethically or legally be seen, even by telehealth, unless a compact (PSYPACT for psychologists, the Counseling Compact for some LPCs) or a temporary practice rule applies.

The AI receptionist is not licensed to make that determination. But the AI can, and should, capture the client's state of residence at the time of the appointment, then check the booking against a static map of states where the therapist is authorized. If the caller's state is not on the map, the AI routes to a human for a real eligibility check rather than booking and creating a problem.

This is a five-line configuration that none of the ranking vendor pages mentions. Ask whether the vendor supports it. If they do not, you are choosing between turning the feature off (and risking out-of-state booking errors) or building a manual gate at session-confirmation.

PMS integration matrix for therapy practices

The PMS systems mental-health practices use are not the same as the EHRs medical offices use. The major ones:

PMS	Integration reality (ask the vendor)
SimplePractice	Public API exists but limited; many AI receptionists integrate via Zapier or one-way calendar push
TherapyNotes	Limited public API; integrations often via Zapier or screen-scraping; verify what is supported
TheraNest	More open API; richer two-way integrations more common
Jane App	Public API; two-way integration available with stronger vendors
IntakeQ	API-friendly; popular with mid-size practices
Tebra (formerly Kareo)	Broader medical PMS; some MH practices use it
Sessions Health	Newer, cloud-native; integration scope varies by vendor
Headway, Alma	Provider-side aggregators; different integration model (booking flows through them, not directly to your PMS)

The honest framing: do not take a vendor's "integrates with all major PMSs" claim. Ask whether the integration is two-way (writes appointments back, not just pulls calendar) and whether it requires Zapier on your end. A one-way calendar pull with Zapier glue works, but you should know that is what you are buying.

Buyer checklist: 8 questions before signing

Run every shortlisted vendor through these eight:

1. BAA scope. Does the BAA cover all sub-processors (LLM, STT, TTS, storage), and can you see the chain in writing?
2. Crisis trigger configuration. Can you edit the trigger list, per-tier actions, and the 988 fallback? Is there a warm-transfer mechanism?
3. Licensure gate at intake. Can the AI capture client state and gate booking against a per-therapist licensure map?
4. Model training opt-out. Is PHI excluded from model training by default, and is that in the BAA?
5. Audit log retention and access. What is the default retention, who can access logs, and how do you export and destroy them on patient request?
6. US-only data residency. Are all PHI flows kept on US infrastructure?
7. Integration depth with your PMS. Two-way or one-way? Native or Zapier-mediated? Failure mode if the integration breaks?
8. Off-ramp. What is the export format for transcripts, recordings, and structured intake data on contract end? Can you take your data with you?

A vendor who answers all eight with documentation is shortlist-ready. A vendor who answers most with "we'll get back to you" is not.

FAQ

Is an AI receptionist HIPAA-compliant by default? No vendor is "HIPAA-compliant by default." HIPAA compliance is a property of the configuration and the BAA chain, not a checkbox. The vendor must sign a BAA, the sub-processors (LLM, STT, TTS, storage) must each be BAA'd or US-hosted in a way that satisfies HIPAA, and the deployment must be configured to minimize PHI exposure. Always verify the chain in writing.

Can the AI handle a supervisee or pre-licensed clinician's caseload? Yes, if the booking flow respects the supervision rules. Configure the AI to never book a new client directly to an unlicensed supervisee without routing for supervisor review. Trickier in states with restrictive pre-licensure rules; check with your supervisor.

How much does an AI receptionist for a therapy practice cost? Pricing tracks general AI receptionist pricing: typically $200 to $1,200 per month depending on call volume and configuration depth, with custom builds running higher. Our AI receptionist cost article breaks down the ranges, with the therapy-specific note that crisis configuration and PMS integration tend to push toward the higher tier.

What if our group practice covers multiple states? The licensure-gate configuration is built per-therapist, not per-practice. The AI checks the booking caller's state against the specific therapist's authorized states, not a practice-wide list. Group practices benefit from this most.

How is this different from how AI receptionists work in general? Mechanically the call flow is the same (STT, LLM, TTS, telephony, integration), and we cover how AI receptionists work in detail elsewhere. The mental-health-specific layers are the crisis trigger list, the 42 CFR Part 2 overlay, the licensure gate, and the harder "what AI should never do" boundary.

---

If you are evaluating an AI receptionist for a mental-health practice and want help mapping a crisis protocol, a licensure gate, and a BAA chain to your specific setup, book an intro call. We build AI voice agents for healthcare practices end-to-end and keep the configuration honest about what the AI can and cannot do.