An AI receptionist for specialty practices handles the calls that look like primary care calls, such as rescheduling, cancelling, booking a follow up or asking for directions, without much change. The calls that do not look like primary care, meaning referral intake, procedure scheduling and anything involving prep, need far more configuration, and that second group is where specialty phone automation succeeds or fails.
Where we stand, so you can read the rest in that light: MedPhone is in production today at a family medicine practice on athenahealth. Specialty workflows are configured per practice, and we have not yet run a cardiology or orthopedic phone line in production. Treat this post as a map of what changes, what to configure and what to test with any vendor, us included.
How specialty call patterns differ from primary care
A family practice line is high volume and mostly routine. A specialty line usually carries fewer calls per provider, but each call comes with more rules. The differences cluster in five places.
- New patients often arrive by referral, and some insurance plans require one before the first visit
- Appointment types multiply. A new consult, a follow up, a procedure, a post op check and a test visit may each need a different length, provider, room or piece of equipment
- Procedures need things lined up before they can be booked, sometimes including a prior authorization that sits entirely outside the phone call
- Prep instructions matter, and some of them are clinical rather than logistical
- Results and post procedure calls carry more clinical weight, so a larger share must reach a person
| Call type | Primary care | Specialty | What an AI receptionist should do |
|---|---|---|---|
| Reschedule or cancel | Very common | Very common | Complete it, with a reason, inside the EHR |
| Follow up visit | Common | Very common | Book against the right appointment type and interval |
| New patient | Often self referred | Often referred | Follow the practice referral rule, transfer when it cannot be met |
| Procedure booking | Rare | Common | Book only where the practice allows it, otherwise route to the coordinator |
| Prep questions | Rare | Common | Answer written logistics, transfer anything clinical |
| Results and post op | Common | Common | Transfer to clinical staff |
At most specialty practices the top two rows carry most of the volume, and they work the same way as in primary care. That is the honest case: not that an AI receptionist handles everything, but that it takes the large routine share off the desk while the complicated share goes to the people who were always going to handle it.
How specialty practices use an AI receptionist, by specialty
Short notes on five specialties, written from the call patterns these practices describe rather than from our production data.
Orthopedics
New injury calls, post op follow ups, imaging questions and physical therapy coordination. Follow ups on a set interval after surgery are routine and suit an agent well. New injury calls need care: whether the patient needs imaging first, whether it is a workers compensation or auto claim, and whether the injury is acute enough to need a person. Those become rules, and anything outside them transfers.
Dermatology
Skin checks, cosmetic consultations, biopsy results and seasonal surges. Annual skin check booking is routine. Cosmetic and self pay inquiries are revenue that rarely comes back if the phone rings out, which makes evening and weekend answering worth more here than in most specialties. Biopsy and pathology results always go to a person.
OB GYN
Annual well woman visits, prenatal visits on a defined cadence, and a high share of clinical calls. Annual visits and rescheduling automate well. Anything about pregnancy symptoms, bleeding or possible labor goes to clinical staff immediately, and a caller describing an emergency is told to dial 911. Expect fewer calls resolved without a person than at a family practice, and distrust any vendor who promises otherwise.
Cardiology
Interval follow ups, test scheduling such as echocardiograms or stress tests, and device clinic visits. Follow up booking is routine. Test scheduling often depends on an order being in place, so the practice rule may be that staff book tests. Any mention of chest pain, shortness of breath or fainting is an emergency path, not a booking.
ENT
Allergy visits, hearing tests, children with a parent calling, and post procedure checks. Booking against the right resource matters, because an audiology slot and a physician slot sit on different schedules. Parent and guardian calls need the same identity handling as in a pediatric practice.
Referral intake and appointment type rules
For a specialty practice this is the most important configuration question, and the one most demos skip because it is unglamorous.
MedPhone books new and existing patient appointments against real provider availability, following appointment types and the rules the practice sets, and transfers what falls outside them. In a specialty practice, the rules are the product. Four questions I would put to any vendor:
- Can a referral requirement be written as a rule the agent follows, or does every referred new patient become a transfer? Either can be acceptable, as long as you know which before you sign
- Can it tell appointment types apart from what a caller says? "I need to come back in" might be a post op check, a routine follow up or a new problem
- Does it follow provider specific rules, such as a surgeon who sees new patients only on Tuesdays, or a nurse practitioner who does post op checks but not consults?
- What happens when nothing fits? The right answer is a clean transfer with context, not an agent offering whatever slot happens to be open
One limitation, stated plainly: MedPhone does not do insurance eligibility verification or prior authorization. It captures insurance information at intake. If a procedure cannot be booked until an authorization is approved, that approval belongs to someone in the practice using other systems, and the phone call should not pretend otherwise.
Procedure scheduling and prep instructions
Procedure scheduling is where many specialty practices sensibly keep a person in the loop. A slot may depend on the facility, a specific piece of equipment, anesthesia, a prior authorization and pre op testing all lining up. Many practices already run this through a surgical or procedure coordinator. The usual right answer is to keep doing that and have the agent route procedure calls straight to that person with the details already taken.
Prep comes in two kinds, and the split matters. Logistical prep the practice has written down, such as which entrance to use for the procedure suite or how early to arrive, can be answered from practice configuration, the same way as hours, location and parking. Clinical prep, such as whether a particular patient should stop a blood thinner, is clinical advice. MedPhone does not give clinical advice, so those calls go to staff.
Ask the agent on a demo whether you should stop taking your aspirin before a procedure. The correct behavior is a transfer to a person. An agent that tries to answer was configured badly or built badly.
What is live today, and on which EHR
Specialty practices often run different EHRs from primary care, so this matters more than usual. MedPhone is live in production on athenahealth as a verified athenahealth Marketplace Partner. ModMed is widely used in dermatology, orthopedics, ophthalmology and other specialties; on ModMed, as on eClinicalWorks, NextGen and Dentrix, core scheduling is covered or in active development and capabilities vary. Ask on a demo what is live for your system rather than assuming.
Our production reference is Synergy Medical, a family medicine practice in Michigan on athenahealth, live since June 2026, where 65 to 75 percent of calls are resolved without reaching a person. A specialty practice should not expect that range on day one. More of your calls are clinical, so more will transfer. What should carry over is the shape: routine calls finished, everything else routed with context.
How should a specialty practice evaluate an AI receptionist?
Bring your own scripts to the demo, drawn from your phone line rather than the vendor's list.
- A referred new patient whose referral you cannot confirm
- A post op patient asking to move their two week check
- A patient who says "I need to come back in" without saying why
- A caller asking whether to stop a medication before a procedure
- A self pay cosmetic or elective inquiry at 9pm on a Saturday
- A caller describing a symptom your practice treats as urgent
- A parent calling for a child, if you see children
Listen to how each call ends: booked, transferred with context, or stuck. The vendor who tells you which of the seven it will transfer before you ask is usually the one worth a second meeting.
How MedPhone handles a call from ring to chart
Sources
Questions people ask
Does an AI receptionist work for specialty practices?
Yes, for the routine share of calls, which at most specialty practices means rescheduling, cancellations, follow up booking and practice questions. Referral intake, procedure scheduling and prep questions need more configuration, and a larger share of calls will transfer to staff than in primary care.
Is MedPhone live at specialty practices?
MedPhone is live in production at a family medicine practice on athenahealth. Specialty workflows are configured per practice, and on a demo we will go through exactly what has been configured and what is live for your specialty and EHR.
Can an AI receptionist handle referral intake?
It can if your referral rule can be expressed as something the agent follows, booking when the rule is met and transferring when it is not. Ask any vendor to run your actual referral rule on a demo call, and find out whether referred new patients are booked or always transferred.
Can an AI receptionist schedule procedures?
Where the practice allows it and the rules are clear, procedure booking can follow appointment type rules like any other visit. Many specialty practices prefer to route procedures to a coordinator, because a slot can depend on equipment, the facility and a prior authorization that sits outside the call.
Will it give patients procedure prep instructions?
It can answer logistical prep the practice has written down, such as where to go and when to arrive. Clinical prep, such as whether to stop a medication, is clinical advice, and MedPhone transfers those calls to staff instead.
Does MedPhone work with ModMed?
Capabilities on ModMed vary, with core scheduling covered or in active development, while athenahealth is the integration live in production. Ask on a demo exactly what is live on ModMed for a practice like yours before planning around it.
Written by
Agni Patel is the founder and CEO of MedPhone. His production deployment is in family medicine, which is exactly why this post spends so long on what is different.