Case Study: Podiatry Practice

Case Study: An AI Phone Agent for a Medical Practice That Books Into Its Real Schedule

How I connected a phone agent, a text agent and website booking to a podiatry practice's ModMed calendar.

By Jude Horak | Updated November 15, 2026

Short answer

Yes. For a podiatry practice with several offices in the Chicago suburbs, I built an AI phone agent, a text agent and website booking that all book visits into the practice's ModMed schedule. They offer only times ModMed shows as open, match or register the patient, book the slot, and read it back. Anything unclear goes to the front desk.

3 ways in

Phone calls, text messages and the website all book through the same path.

Weeks ahead

How far ahead each availability lookup searches for open times.

2 systems

Booked into Tebra first, then switched to ModMed without changing how patients book.

Read back

Every booking is checked as open, created without an override, then read back.

What Happens When a Patient Books

The same five steps run for a call, a text or a web form.

Step 1

Patient reaches out

By phone, by text, or through a booking form on the practice website.

Step 2

Agent checks open times

It asks the reason and the office first, then pulls real openings from ModMed.

Step 3

Collects the details

Name, phone, date of birth and email, each read back so mistakes get caught.

Step 4

Finds the chart

Matches an existing patient or registers a new one. Unclear matches go to staff.

Step 5

Books and confirms

Checks the slot is still open, books it, reads it back, and texts the staff.

Does the AI phone agent book straight into the scheduling system?

It does now, and getting there took two steps. At first, bookings from the phone agent, the text agent and the website were saved in my own system and then had to be typed into Tebra by hand. Hand re-typing is exactly where bookings get lost.

So in August 2026 I built a bridge. From then on, every booking found or created the patient in Tebra and added the appointment there automatically, with no re-typing.

Then the practice moved from Tebra to ModMed in November 2026. I switched the one booking path that all three channels share, so new visits go into ModMed. Patients did not see any change. The phone agent, the text agent, the main site and the ad landing pages kept working the same way, now asking for date of birth because ModMed needs it to register a new patient.

How does it know which appointment times are really open?

The first version guessed. It offered times from office hours written into its instructions, which meant a closed or full day could have been offered. I replaced that with a lookup tool the agent must call before it offers or confirms any time, for a new visit or a reschedule.

Today that lookup asks ModMed's appointment finder for open slots on the real calendar. ModMed already knows things my office hour rules did not, like a lunch hour and offices that open late or close early on certain days. The result is narrowed by office hours and by bookings already made online, and any time the doctor is booked at another office is dropped. Each lookup searches weeks ahead, so a stretch of blocked days never makes the agent say the practice is full.

Right before booking, the system asks ModMed one more time whether that exact slot is available. Only a yes creates the appointment, with no override, and the appointment is read back to confirm it saved. Some slots at this practice hold more than one patient, so ModMed decides capacity, not my code.

How does it avoid duplicate patient charts?

It never guesses. A caller counts as an existing patient when the last name and phone match, or the full name and date of birth match. Anything less certain, like a shared family phone, goes to the front desk with nothing written.

What happens when the agent cannot help a caller?

It takes a message, and the message does not disappear. Each request becomes a numbered callback ticket. The staff get a text and an email with a link, and the ticket stays on a callbacks list until someone records what happened.

I also wrote firm rules into the agent after reviewing its real calls. It may not say a request is logged until the tool confirms it. It may not promise a person or a time. Hospitals and physician offices are routed to the doctors' team as a professional message. A caller who speaks Spanish gets answered in Spanish.

Does this work with ModMed, Epic or athenahealth?

This build books into ModMed, and into Tebra before the switch. Those are the only two scheduling systems this case study shows. I have not built Epic or athenahealth booking for this practice, so I will not claim results there.

What carries over is the method. For any system, I check what its access allows: can I read open slots, create and cancel appointments, and search patients? That answer decides how the agent connects. For the systems a practice can choose from, see Voice AI for medical practices.

How was it tested before it went live?

Prompt changes run first on a separate copy of the agent, replayed against scenarios built from real call types: a price question, a hospital calling, a sales call, a Spanish speaker. The ModMed connection was tested end to end on a dedicated test chart, booking and cancelling, before any real patient used it. The first real booking made through the new path was linked into ModMed as expected.

What does it not do?

It never forces a booking into a time ModMed says is taken, and it never overrides the schedule.
When two patients could be the same person, it writes nothing and sends the case to the front desk.
A new patient who will not give a date of birth is not registered automatically. Staff finish that one.
It does not give medical advice. A caller worried about something urgent is pointed to urgent care or the emergency room.
It does not promise who will call back or when. It logs the request and the team follows up.

Frequently Asked Questions

Does the AI phone agent book straight into the scheduling system?

Yes. Since the practice went live on ModMed in November 2026, visits booked by phone, text or the website land in ModMed as real appointments. Before that, the same bookings went into Tebra through a bridge I built in August 2026.

How does it know which appointment times are really open?

It asks ModMed for open slots on the doctor's real calendar, then removes anything outside office hours and anything already booked through the agent. Lunch breaks and short office days set in ModMed are respected automatically.

What happens when the agent cannot help a caller?

It takes a message. The request becomes a callback ticket, the staff get a text and an email, and the ticket sits on a callbacks list until someone marks it done. Calls from hospitals and physician offices go straight to the doctors' team.

Does this work with ModMed, Epic or athenahealth?

This build books into ModMed, and before that into Tebra. I have not built an Epic or athenahealth booking for this practice. For any other system, the first question is what its API or staff access allows for reading open times and creating appointments.

Can patients reschedule or cancel through it?

Yes. A change follows the link to the original ModMed appointment, cancels the old time, and books the new one. The staff text says exactly what was done.

What does a build like this cost?

It is priced per project. The things that move it are which scheduling system you run, what access that system gives, how many offices and appointment types you have, and whether texting and web booking are part of it.

Want Calls Booked Into Your Schedule?

Tell me which scheduling system your practice runs, and I will tell you what it would take to connect.

We use optional analytics and marketing cookies to understand visits and enquiries. Your demo works with either choice. Privacy policy