Compare
An AI receptionist answers your phone. We run your front door.
Several of these companies are well funded and genuinely good at the phone. Naming them and still winning the row is the point.
| Capability | DocAssistants | Prosper AI | Hello Patient | Hyro |
|---|---|---|---|---|
| Owns the website | Yes — we build and run it | No — voice and workflow, not the public site | No — phone and scheduling | No — conversational layer on existing properties |
| Writes to long-tail EMRs | Practice Fusion and eClinicalWorks live; certified FHIR R4 as a path | Broad EHR coverage, including large-system vendors | Scheduling integrations; coverage varies by practice | Enterprise integrations; strongest in health systems |
| Human release before publish | Yes — digest-bound gate. Nothing patient-facing leaves without a named person | Call review and exception routing when confidence is low — not a publish gate | Staff can take over a live call; not a pre-publish release | Handoff to live agents; not a content-digest gate |
| Full audit log | Hash-chained record of every tool call and state change | Call reports, transcripts, and QA flags | Call logs and scheduling history | Conversation analytics and QA |
A distinction that gets blurred
Escalation is not a release gate.
Escalating a call when a model’s confidence is low is exception routing. It is not a human approval gate. A gate means nothing goes out at all until a person releases it, bound to the exact content approved. If the bytes change after that release, the publish is refused.