Partial integration

An AI receptionist for ModMed practices.

MedPhone's ModMed integration covers core scheduling workflows today, with additional capabilities in active development. We will walk through exactly what is live for your practice on a demo.

Last updated:

We will not tell you ModMed works today when it does not. This page updates when it goes live.

An AI receptionist for ModMed practices is a voice AI system that connects to ModMed to handle inbound patient calls: looking the patient up, checking provider availability, and booking or moving appointments. Core scheduling runs in production today. Refill task creation, insurance intake and chart write back are at varying stages of development on ModMed, and all of them run in production on athenahealth.

What a ModMed front desk fields all day.

Specialty practices. Dermatology, ophthalmology, orthopedics, plastic surgery, gastroenterology, urology and ENT make up most of the base.

  • Procedure scheduling, where the slot type and the prep instructions have to match
  • Pre op questions in the days before, and post op checks in the days after
  • Self pay and cosmetic consultation inquiries, which are revenue that never comes back if the phone rings out
  • Pathology and imaging results, where the caller wants a person and a date
  • Seasonal surges, because skin checks and allergy seasons do not spread themselves evenly

Specialty calls carry more clinical context than a primary care booking, and the cost of getting one wrong is higher. That is a real constraint on any phone automation, and it is why this build is not a copy of the primary care one.

Where the ModMed integration stands.

Core scheduling on ModMed runs in production today. Beyond that, capabilities are at different stages, and the honest answer for any given workflow is either that it works now or that it is in development. We will not show you a feature grid that blurs the two.

What is real today is athenahealth, where MedPhone is answering patient calls in daily use. The call handling, the routing, the transfer rules and the writing back to the chart are all built and working. What changes per EHR is the connection underneath.

We have no named ModMed practice to point you at yet. The production deployment behind everything on this site is a family medicine practice on athenahealth, and that is the one we will show you.

What a ModMed AI receptionist would do first.

A specialty build is not a primary care build with the name changed. These are the four we would take first on ModMed, chosen because they are where a wrong answer on the phone costs the most.

  1. Procedure scheduling where the slot type, the length and the prep instructions all have to agree, rather than a generic appointment that a human has to correct later

    In development

  2. The pre operative and post operative windows, which generate a burst of calls on a predictable schedule and almost never get a dedicated person

    In development

  3. Cosmetic and self pay inquiries, which are the callers least likely to leave a message and the ones worth the most when they connect

    In development

  4. Pathology and imaging results, where the caller wants a person and a date and a portal message will not settle it

    In development

Straight answers about ModMed.

Does MedPhone work with ModMed today?

No. ModMed has approved MedPhone to integrate, and the build has not started. Nothing is working yet and we are not going to imply otherwise. MedPhone is live in production on athenahealth.

Why does a specialty build take longer?

Specialty calls carry more clinical context than a routine booking, and the cost of getting one wrong is higher. Slot types, prep instructions and what may safely be answered without a clinician all differ by specialty, so the rules have to be built for the practice rather than assumed.

What moves ModMed up the queue?

Demand from practices that want it, and access to real scheduling rules to build against. The list is how we decide the order. Telling us your specialty and your call volume genuinely changes where it sits.

What MedPhone does in production today.

Running on athenahealth today. This is what comes to ModMed when the integration lands.

The mechanics are on the how AI phone agents work page, and the AI phone agent case study at a family medicine practice sets out what two months of it actually produced.

  • Answers every inbound patient call on the first ring, on hours and after
  • Books, reschedules and cancels appointments against the provider schedule
  • Takes prescription refill requests and routes them to the provider inbox
  • Collects insurance details and flags mismatches for the front desk
  • Transfers complex or urgent calls to your team on rules you set
  • Writes a summary of every call back to the patient chart

See exactly what runs on ModMed today.

Tell us your practice size and call volume. On a twenty minute demo we will go through exactly which workflows are live on ModMed for a practice like yours, and which are still in development.

See a live demo