BAA before PHI
Get the vendor’s current Business Associate Agreement and data-handling terms before allowing the system to receive protected health information. Marketing language alone is not enough.
Therapy calls require a stricter buying process than ordinary lead capture. A receptionist may hear sensitive health information, intake details or crisis language. That makes HIPAA/BAA documentation, escalation rules and practice-management integration more important than the cheapest monthly plan.
Get the vendor’s current Business Associate Agreement and data-handling terms before allowing the system to receive protected health information. Marketing language alone is not enough.
Define exactly what the system does with self-harm, danger, abuse, medical emergency or other crisis language. It should not improvise clinical advice.
Verify the exact action in SimplePractice, TherapyNotes or your calendar: booking, rescheduling, cancellation, waitlist, insurance questions and clinician routing are different workflows.
AgentZap currently markets directly to therapy practices, states that a signed BAA is included, and names SimplePractice and TherapyNotes integration workflows. Its therapy page lists plans from $109/month.
Non-affiliate benchmark. Verify the actual BAA and integration scope before purchase.
Upfirst’s main pricing page currently references BAAs for HIPAA-regulated businesses, but at least one current industry page states Upfirst is not HIPAA compliant. Because the vendor’s public documentation is inconsistent, ReceptionistLab does not recommend using it for PHI unless Upfirst resolves the discrepancy for your account in writing.
Smith.ai has strong scheduling, intake and human-escalation capabilities, but its current medical/wellness page explicitly says the AI Receptionist is not HIPAA compliant and cannot handle PHI in regulated healthcare environments. That makes it a poor fit for therapy workflows involving PHI.
Therapy-practice calls can involve sensitive information and crisis language. Treat compliance, practice-management workflow and escalation as gates before comparing convenience or price.
Confirm the exact service and contract support the information your workflow may collect before routing real patient calls.
Verify new-patient booking, rescheduling, cancellations and any practice-management integration with test calls.
Define what the receptionist should do when callers use crisis or emergency language; it should not improvise clinical advice.
For practices, the right evaluation sequence is written data-handling terms, scripted escalation and permitted booking. Price should be considered only after the product qualifies for the actual healthcare workflow.
Request a signed or signable BAA where required, list of subprocessors, transcription retention, recording controls and supported product tier. Do not enter PHI in a trial before these questions are resolved.
Run synthetic scenarios with urgent and ambiguous language. Require a practice-approved response, clear human escalation and no diagnosis, promised appointment or improvised safety advice.
Use dummy client records to test new patient booking, cancellations, clinician assignment, time zones and reminder behavior. Do not infer a practice-system integration from a generic calendar logo.
HIPAA compliance is fact-specific. An advertised BAA alone is not sufficient to establish your practice is compliant; involve your privacy adviser before deploying with PHI.