Substance first
Replies open with the answer, never with a receipt. No "got it", no "sure", no restating the caller's question back at them.
AI receptionist for healthcare
A receptionist who knows your practice.
MediVoice answers your line in a voice patients recognise as a person, and writes what it hears straight back to your schedule. It greets a returning patient by name, knows which room Dr. Alvarez uses on Thursdays, and gets a real human on the line the moment a call needs one.
Live in a few practices today. General availability follows the roadmap below.
The voice
Most phone systems
are embarrassing.
Patients judge a practice in the first four seconds of a phone call. Ours is trained to pass as staff: short, warm, specific, and never robotic — including when it does not know something.
Interruptible
Callers talk over MediVoice the way they talk to a person. It stops mid-word and listens, without apologising for the interruption.
Honest under pressure
It never invents an answer. If a record is missing or a question is out of scope, it says so and routes the call onward.
Remembers the thread
Names are spelled back letter by letter to confirm. A caller correcting one letter gets the whole name confirmed again.
Reads the room
Accents, crosstalk, a bad line, a cough across the desk — it asks again plainly instead of guessing at what it half-heard.
Yours to configure
Set the greeting, the tone, the words your clinicians actually use, and when to transfer. Each practice gets its own voice.
Phrases we removed from the model
Banned outright, in every configuration. This is the vocabulary that makes a phone system sound like a phone system.
- "Certainly."
- "I'd be happy to help."
- "How may I assist you today?"
- "Is there anything else I can help you with?"
- "Thank you for calling, I hope this helps."
- "I've noted that."
- "Let me check that for you."
- "Just a moment."
- "Absolutely."
- "Sure thing!"
Example calls
What it says,
in practice.
Three calls through the system. The second is a caller cutting in mid-sentence; the third is the one every practice asks about — what happens when it does not know.
Example transcript
Under 400ms, caller to first word
Integrations
It reads the chart,
and writes to it.
MediVoice works against your existing record, not a parallel one. Every call is booked, moved, and documented in the system your clinicians already open every morning.
Scheduling, end to end
Real-time availability across providers, rooms, and equipment. Books, reschedules, cancels, and handles waitlist backfill without a human in the loop.
Two-way, not read-only
Writes go back to the same record it read from, tagged with the call. No duplicate entries, no reconciliation, no second inbox to check.
Insurance and intake
Eligibility checks during the call, referral capture, copay and balance questions answered from the record, and digital intake started while the caller is still on the line.
Clinical context, on request
Asked the right way, it can read back a visit summary or a care instruction. It does not diagnose, and it does not offer a clinical opinion.
Certified connections
- Epic
- Oracle Health
- athenahealth
- eClinicalWorks
- NextGen
- Office Ally
Anything else, we read its API. MediVoice speaks FHIR R4, HL7v2, and plain old REST — including systems nobody has ever heard of.
Never a dead end
A human is
always one step away.
The failure mode of every phone bot is a caller trapped in a loop with nobody to escalate to. MediVoice is built the other way around: the human path is the default, and the automation is what saves your staff the calls they can skip.
- Transfers to the front desk with the caller's context already attached
- Routes to on-call or a specific extension by line or by schedule
- Hands off on request, or on any topic flagged as clinical or urgent
- Takes a message and delivers it as a task, not a voicemail full of noise
- Fails open — if the record is unreachable, it says so and transfers
Trust
Built for regulated work.
Handling protected health information is the whole job, so it is engineered in rather than reviewed in. MediVoice operates under a business associate agreement with every vendor in the path — including the model provider.
BAAs, all the way down
Executed agreements with our sub-processors and the foundation model provider, so no part of the call sits outside a covered relationship.
PHI never trains a model
Zero-retention inference. Your conversations are not used for training, by us or by anyone downstream, under any setting.
Encrypted throughout
TLS 1.3 in transit, AES-256 at rest, per-tenant keys, with rotation on a schedule you control.
Every access, logged
An immutable audit trail of who read which record, which call wrote what, and which action was taken.
Least privilege
Role-based access down to the field, SAML SSO and SCIM provisioning, and time-boxed clinician access to their own panel.
Retention you set
Per-practice rules for call audio, transcripts, and metadata — down to keeping nothing at all.
Compliance posture
HIPAA-aligned by design, with BAAs in place across the full vendor chain. Risk analysis, policies, and workforce training maintained as part of the security program. Independent penetration testing annually; SOC 2 Type II underway. Full documentation is available to practices under NDA during evaluation.
Outcomes
What we hold
ourselves to.
Design targets for a full practice, measured monthly and shared with you in the dashboard. If a practice misses them, we tell you before you ask.
<5sto answer, at any hour
~70%of calls closed without a human
3.2xmore calls handled per FTE
0caller-hung-up calls in the preview cohort
Roadmap
Where we are
and what is next.
Published rather than promised quietly. Dates move when the work says they should, and this page moves with them.
NowPrivate preview
Live in a small cohort of founding practices: natural voice, scheduling, human handoff, and the analytics to prove it.
NextGeneral availability
Full Epic and Oracle Health connections, insurance eligibility and referral capture, multi-location, and the compliance package released to all customers.
LaterAutonomous front desk
Prescription refill routing, care navigation, claims questions, and outbound calling for recall and follow-up — all under the same controls.
Request access
Bring us your
hardest call.
We onboard a limited number of practices each month. Tell us what your front desk would not want to answer, and we will put it in front of MediVoice.