Hello Patient
Also known as: HelloPatient, hellopatient.com, Patient Engagement Technologies Inc.
Mia, Hello Patient's AI agent for medical, dental and veterinary practices, answers patient calls, texts and chat around the clock, books and reschedules into the EHR, verifies insurance, handles intake and bill pay, runs recall outreach, and escalates clinical questions to staff. SOC 2 Type 2 and HIPAA with a BAA; $22.5M Series A.
Hello Patient sells Mia, an AI agent for patient conversations across voice, text and web chat, used by medical, dental, behavioral health, optometry and veterinary practices. Mia answers inbound calls and messages around the clock, schedules, reschedules and cancels appointments, verifies insurance and collects intake details, handles bill pay and referrals, and runs outbound recall, no show and intake outreach from lists the practice provides. It reads patient records and calendars and writes appointments, new patient accounts and notes back into the EHR, natively in athenaOne and through FHIR and HL7 for systems such as ModMed, AdvancedMD, NextGen, eClinicalWorks and Zenoti.
The practice decides what the agent handles, and clinical questions are escalated to staff. Calls are logged and an audit log records every conversation, beside an analytics dashboard. Hello Patient states SOC 2 Type 2 certification and HIPAA compliance, signs a BAA with every practice, keeps PHI in its US hosted environment and does not train models on it. Implementation takes about six weeks and needs no engineering team, and pricing is usage based on conversation volume. The company is Patient Engagement Technologies Inc. of Austin, Texas, which also trades as Hello Fido. It raised a $22.5M Series A and has announced the acquisition of Converse Health.
Vendor details
Canonical URL
https://www.hellopatient.com
Category
Voice agent
Funding status
$22.5M Series A (company announcement); Austin, Texas
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Hello Patient integrates natively with athenaOne, reading records and calendars and writing appointments, reschedules, cancellations, new patient accounts and notes. FHIR and HL7 connect ModMed, AdvancedMD, NextGen, eClinicalWorks, Zenoti, Provet Cloud and others. Salesforce, HubSpot, Customer.io and Braze are supported too, with CSV exports where a practice system has no API.
In practice
Your front desk misses patient calls after hours and at lunch. Mia answers calls, texts and web chats around the clock and books, reschedules or cancels appointments straight into the EHR.
Your recall list keeps growing while staff are busy with patients in the office. Hello Patient runs outbound recall, no show and intake outreach from the lists and timelines your practice provides.
Your team wants routine requests handled but clinical questions kept with staff. You decide what Mia handles, and anything needing clinical judgment, such as dosing or prescriptions, is escalated to a person on your team.
Sources & related URLs
Research sources
Agentic Index coverage score
5.0 / 14 capabilities · 36%
| Integrations & Tool Calling | Full |
|---|---|
|
Agents read patient records and calendars and write appointments, reschedules, cancellations, new patient accounts and appointment notes back into the EHR. They do this natively in athenaOne and through FHIR and HL7 for ModMed, AdvancedMD, NextGen, eClinicalWorks, Zenoti and others. Salesforce and HubSpot are supported as well. SourceHello Patient, hellopatient.com FAQ and homepageread 2026-09-28 |
|
| Workflow Orchestration | Partial |
|
The agent runs fixed patient flows (scheduling, reminders, intake, insurance verification, billing, referrals, recall) that Hello Patient maps to the practice's protocols during a six week implementation. Hello Patient names no branching, conditions, workflow builder or multi agent routing that the customer operates. SourceHello Patient, hellopatient.com Product page and FAQread 2026-09-28 |
|
| Knowledge Grounding & RAG | Partial |
|
The agent reads live patient records and calendars from the EHR for each conversation. It answers administrative questions (hours, directions, services) from protocols and content Hello Patient tunes with the practice at onboarding. Hello Patient names no knowledge base or retrieval layer that the practice maintains, and the context is assembled for each conversation. SourceHello Patient, hellopatient.com FAQread 2026-09-28 |
|
| Human Oversight & Guardrails | Partial |
|
The practice draws the line between what the agent handles and what a clinician handles. Anything needing clinical judgment (dosing, side effects, prescriptions) is captured and escalated to a person on the team or routed per the practice's protocols. Hello Patient names no step where staff approve an agent action before it commits. SourceHello Patient, hellopatient.com FAQread 2026-09-28 |
|
| Security, Identity & Governance | Partial |
|
By its own account, Hello Patient is SOC 2 Type 2 certified and HIPAA compliant. It signs a BAA with every practice and does not train models on PHI. It names no SSO, roles or permissions for the practice's own users, and the role based access in its DPA covers Hello Patient's internal controls. SourceHello Patient, hellopatient.com FAQ and DPAread 2026-09-28 |
|
| Observability & Auditability | Partial |
|
Every call is logged for review, and an audit log captures every conversation for compliance, beside an analytics reporting dashboard. Hello Patient names no per conversation view of the actions the agent took in the EHR. SourceHello Patient, hellopatient.com FAQ and Product pageread 2026-09-28 |
|
| Memory & State Persistence | Not documented |
|
Patient history and context come from the practice's EHR, CRM and PMS, which hold the practice's business record. Hello Patient names no memory that the agent keeps on its own. SourceHello Patient, hellopatient.com Product page and FAQread 2026-09-28 |
|
| Deployment & Data Residency | Not documented |
|
The service is hosted, with servers in the United States and PHI kept inside Hello Patient's environment. Customers cannot choose a region, and no dedicated or customer hosted option is offered. SourceHello Patient, hellopatient.com privacy policy and FAQread 2026-09-28 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
One agent, Mia, serves specialties including dentistry, dermatology, ENT, mental health, optometry, primary care, urgent care, veterinary and others, with a list of jobs it covers. Each specialty is a configuration of Mia that Hello Patient tunes for the practice, and there are no separate agents or templates for the customer to adopt. SourceHello Patient, hellopatient.com specialty and Product pagesread 2026-09-28 |
|
| Triggers & Channel Coverage | Full |
|
Inbound patient calls, texts and web chats are answered around the clock with no one at the practice starting the work. Outbound recall, no show and intake outreach runs from lists and timelines the practice provides. SourceHello Patient, hellopatient.com homepage and outbound intake pageread 2026-09-28 |
|
| Model Flexibility & Routing | Not documented |
|
For each practice, Hello Patient tailors the voice's personality, accent and speed. It names no model provider and offers no model choice. SourceHello Patient, hellopatient.com Product page and privacy policyread 2026-09-28 |
|
| APIs, SDKs & MCP Extensibility | Not documented |
|
There is no published API, SDK or MCP server for calling Hello Patient, and the site has no developer pages. Deployment needs no engineering team, with CSV exports or custom work for practice systems that lack an API. SourceHello Patient, hellopatient.com FAQ and sitemapread 2026-09-28 |
|
| Testing, Debugging & Optimization | Not documented |
|
Conversation testing and a pilot with real patients are steps of Hello Patient's six week implementation, run with the practice. Hello Patient names no test harness, scoring or experiments for the practice to run itself. SourceHello Patient, hellopatient.com FAQread 2026-09-28 |
|
| Browser & Computer Use | Not documented |
|
Practice systems are reached through API, FHIR and HL7 integrations or CSV exports. Hello Patient names no browser, desktop or computer control. SourceHello Patient, hellopatient.com FAQread 2026-09-28 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Contact sales
usage (conversation volume across SMS, voice and web chat)
What is public
The billing axis (usage by conversation volume across SMS, voice and web chat) and the sales led motion; no rates, tiers or minimums are published.
Variable cost rationale
The FAQ states usage based pricing on conversation volume, but no rates are published.
Sales call required
Yes, required for paid access
Free / trial
Not published
Related vendors
- AgentVoice — AgentVoice builds and runs inbound and outbound AI voice agents, and…
- aiola — Voice agents for field teams on Salesforce
- Aircall — Aircall's AI Voice Agents answer and place calls on Aircall's own…
- Allo — Allo is a business phone system for small teams with an AI…
- Autocalls — Autocalls is a no code platform for AI voice agents that place and…
- AviaryAI — Outbound AI voice agents for credit unions, banks and insurers,…
Alternatives to Hello Patient
The closest documented capability profiles to Hello Patient among voice agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Zo (Zocdoc)5.0 / 14Matches Hello Patient across all 14 documented capabilities
- Netic5.5 / 14Fuller documented coverage on Observability & Auditability
- Slang.ai5.5 / 14Fuller documented coverage on Security, Identity & Governance
- Sonant5.5 / 14Adds documented Memory & State Persistence
- Trapeze4.0 / 14A lighter documented profile than Hello Patient
- Avoca6.5 / 14Adds documented Testing, Debugging & Optimization
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded