Is It Risky to Let AI Call Your Patients? Inside AI Patient Calling: Reality, Risks and Safeguards

Every patient services leader who has been pitched an AI patient calling solution has had the same first reaction: what happens when it says the wrong thing to a vulnerable patient? It is the right question to ask, and at Hub West 2026, leaders from 100ms explored the reality, the risks, and the safeguards that determine whether AI-powered patient calling is ready for production.

The Risk Gradient for AI Patient Calling

Not every patient calling use case carries the same level of risk. The session mapped use cases along a gradient of complexity, clinical sensitivity, and impact on time to therapy.

At the lower-risk end are administrative tasks: appointment reminders, refill notifications, shipment confirmations, and survey outreach. These interactions follow predictable scripts, involve minimal clinical judgment, and present limited opportunities for the AI to cause harm. They also represent a significant volume of hub team time that could be redirected to higher-value activities.

In the middle of the gradient are access-related calls: benefits verification follow-ups, copay program enrollment, PA status updates, and specialty pharmacy coordination. These interactions require more contextual understanding and the ability to handle unexpected patient responses, but the clinical stakes are moderate.

At the higher-risk end are clinical and adherence-related conversations: managing side effect concerns, addressing medication fears, navigating therapy discontinuation discussions, and handling emotional distress. These interactions require empathy, clinical judgment, and the ability to recognize when a conversation has moved beyond what an AI agent can safely handle.

Where Humans Must Stay in the Loop

The consensus at Hub West was clear: AI patient calling is not a replacement for human interaction. It is a tool for expanding the capacity and consistency of patient outreach while maintaining human oversight for complex situations.

The critical safeguard is escalation design. AI agents must be engineered with clear, reliable triggers for transferring to a human, including patient expressions of emotional distress, adverse event reports, clinical questions that exceed the AI’s trained scope, and any situation where the patient explicitly requests human assistance.

The failure mode that keeps patient services leaders up at night is an AI agent that does not recognize when it is out of its depth. This means the escalation logic must be conservative: better to transfer to a human unnecessarily than to continue a conversation the AI cannot handle safely.

Privacy, Compliance, and Consent

AI patient calling introduces specific compliance considerations. HIPAA compliance requires that AI voice agents handle protected health information with the same rigor as human agents, including appropriate authentication, encryption, and access controls. State privacy laws may impose additional requirements, including specific consent obligations for AI-mediated conversations.

Regulatory scrutiny of AI in patient communications is increasing, and manufacturers must be prepared to demonstrate that their AI calling programs are compliant with all applicable regulations, that patients are informed they are speaking with an AI agent, and that human oversight mechanisms are documented and functional.

The Physician’s Voice: A Different Approach to Patient Outreach

At Hoot, we have taken a fundamentally different approach to the patient outreach challenge. Rather than using AI to simulate a human conversation, we use the physician’s actual voice, recorded in a 15-minute session, to deliver clinical education at the moments when patients need it most.

This is not a phone call. It is a short, physician-recorded video delivered via SMS or email, designed to address the specific questions and concerns patients have at each stage of their therapy journey. There is no risk of the AI saying the wrong thing, because the content is created by the treating physician. There is no escalation logic to design, because the patient is receiving a one-way clinical education message, not engaging in a dynamic conversation.

For patient services leaders evaluating AI calling solutions, Hoot represents a complementary approach: the physician’s voice handles the clinical education and confidence-building, while human agents (augmented by AI where appropriate) handle the administrative and access-related interactions where dynamic conversation is necessary.