AI Receptionist for ModMed Practices

A dermatology or specialty practice on ModMed lives on a distinction the caller rarely makes cleanly: is this medical or cosmetic. The same phone rings for a changing mole and a pre-wedding filler, and the two go to different providers, different slot lengths, sometimes a deposit, and very different urgency. Get that first read wrong and the booking lands in the wrong half of the practice.

We build the ModMed connection, so this is what happens between a caller's description and a correctly placed visit on their ModMed chart. That first classification, made from a single sentence, is where a ModMed front desk is won or lost, so it is where this starts.

"Integrated with ModMed" hides the detail, so here it is. 2care reaches ModMed through its API, authorised with OAuth2 and scoped to your practice, configured during onboarding. Nothing is installed and no screen is scraped.

Availability is read live from ModMed at the moment the caller asks, filtered by provider, visit type and location, so the slot offered exists in the real schedule. Booking writes the visit against the resolved patient, and ModMed validates it against its own templates and rules, which is why a slot lost during the call fails cleanly instead of being assumed still open. Patients are found by a search on identifier and demographics before any record is made, and the connection manages its own tokens and rate limits, so the load behind it never reaches the caller. Where ModMed's patient portal is in use, a caller and an online booker resolve to the same chart, never two.

Answering every call, cosmetic and clinical alike

Specialty lines spike hard, around a new treatment launch or a results batch, and that is where a desk usually breaks. There is no per-line limit here, so 1000 concurrent calls are handled with no busy signal, each answered on the first ring in about 2 seconds, whether it is one caller or fifty. Because the voice pipeline is native, the ModMed read, the medical-cosmetic sorting and the reply share one timing budget rather than being relayed between separate systems. An urgent clinical call still reaches a human in about 3 seconds under that load, because it never queues behind the cosmetic booking traffic.

Separating a medical concern from a cosmetic request

This is the ModMed-specific problem, and it is the one a generic agent gets wrong. 2care resolves intent, provider and urgency from natural speech and, on a derm or aesthetics line, sorts a clinical concern from a cosmetic one before it books.

A dermatology call	The agent recognises	Where it books or routes
A mole that has changed	A medical concern	A medical derm slot, urgency checked
Filler before an event	A cosmetic request	A cosmetic consult, a deposit if set
An acne script that ran out	A refill	The provider queue, no visit needed
Results from a biopsy	A clinical question	The clinical team, patient resolved
Moving a Mohs procedure	A procedure reschedule	A live slot at the procedure length

The classification is not cosmetic in the other sense: a changing mole described casually still reads as a medical concern and is checked against the escalation triggers, while a routine cosmetic touch-up is not sent down a clinical path it does not need. Anything that crosses a red-flag line leaves the booking flow and reaches a person, configured in triage and routing.

Take a caller who says, "I've got a spot that's been bleeding and it's darker than it was." Described lightly, it is still a medical concern, and the agent treats it as one: it resolves the record, checks the description against the escalation triggers, and books a medical derm slot at the right urgency rather than the next cosmetic consult. A caller asking to "top up my lips before the weekend" is read as cosmetic and sent to a consult, with a deposit if the practice requires one. A menu tree asks both callers to choose a category, and both sometimes choose wrong.

Procedure lengths and treatment intervals, honoured on the call

Specialty care runs on cadence. A procedure has a length ModMed holds, a course of treatment has a minimum interval between sessions, and a provider sees only certain visit types. A system that ignores these books a filler session too soon after the last, or a Mohs slot at the wrong length, and a coordinator unpicks it later.

2care honours what ModMed encodes, on the call. It books the correct length for a procedure, respects the minimum interval before offering the next session in a series, and offers only providers eligible for the visit. A request that does not fit is offered an allowed alternative rather than written and bounced, so the schedule a provider sees in the morning is one they can actually run.

The interval rule is the one most often broken by a booking system that means well. A cosmetic series has a minimum gap between sessions for a reason, and a caller keen to be seen sooner will happily book inside it if the system lets them. The agent does not: it offers the next date that respects the interval ModMed holds, and where the caller pushes, it routes to a person rather than quietly overriding a clinical spacing rule. A schedule full of correctly spaced sessions is worth more than one full of appointments a provider has to move on the day. The interval is a clinical decision, and the agent is built to treat it as one.

The record resolved, and intake written clean

Before anything is written, the caller is matched to the existing ModMed record with a date-of-birth check, so a returning patient keeps one chart. An ambiguous match goes to a person with the candidates gathered, following patient matching, rather than a guess.

Intake is captured at the same moment: the reason, the insurance carrier and member ID for a medical visit, and any consult specifics for a cosmetic one, read back to confirm and written to ModMed as structured fields rather than a free-text note. Clean capture at booking is what keeps the front of house running, and it is the same structured intake that feeds patient intake across every channel a patient uses.

What 2care gives a ModMed specialty desk

A ModMed practice is not short of a specialty EHR; it is short of a phone that keeps up. 2care answers every call and sorts each into the right half of the practice without more front-desk staff. It reads the reason, separates medical from cosmetic, applies ModMed's lengths and intervals, resolves the patient and writes the visit, in one native pipeline rather than a chain of tools passing a patient along.

What a specialty desk feels is not a faster booking on the calls it already handled. It is the cosmetic enquiries that used to go to voicemail after hours now booked, the medical concern that needed a person reaching one in seconds, and the schedule staying clean because nothing was placed in the wrong slot. 2care answers the phone at the standard a ModMed practice already holds itself to on the clinical side.

Write-back on ModMed, and the agreement behind it

A visit booked this way is not a call the words pass through and disappear from. The agent assembles a transcript, ties it to a patient and writes a visit into ModMed.

Under HHS guidance, that is what makes a vendor a business associate rather than a conduit.

So a signed BAA covers the connection before the first live call. Patient information is encrypted end to end, never used to train the models behind the conversation, and every write leaves a reversible record. The specifics sit on the compliance page.

Outreach that fills the aesthetic calendar

Between calls, the same ModMed connection works your list. It confirms procedure appointments a day ahead so a high-value slot is not lost to a no-show, calls cosmetic clients due for the next session in a series before the interval stretches too far, and offers a slot a cancellation frees to the waitlist in priority order. The outcome writes back to ModMed, so a filled slot and a completed follow-up both land where the front desk actually looks, not on a list beside it.

Where this is right for a ModMed practice

The practices that gain most share a few traits.

A mixed medical and cosmetic book. The more a single line has to separate clinical from aesthetic before booking, the more that first read is worth, and derm and plastics feel it most.

Lengths and intervals kept current in ModMed. The agent honours what ModMed holds, so a practice that keeps procedure lengths and treatment intervals accurate gets the full benefit from day one.

A clinical route for urgent calls. Anything that turns clinical goes to a provider or nurse, so a practice with that queue in place can move the line over straight away.

Going live on ModMed

Three steps, over weeks. First, authorise the connection so the agent can read availability and write visits through ModMed's API. Second, map your rules: providers, medical and cosmetic visit types, procedure lengths, treatment intervals and the escalation lanes. Third, test in a test context with your team listening, then move the line over and watch the first days while the medical-cosmetic sorting and the routing settle against the real calls.

Those first days are the tuning window. A term the agent filed as cosmetic that your practice treats as medical gets remapped, and a procedure booked a little short has its length fixed. Each adjustment is driven by the recorded trigger on every escalation, so it is a correction with evidence behind it, and the picture is stable inside a fortnight. Patients keep dialling the same number throughout; the agent answers in front of your existing line, with nothing to port and no hardware to install anywhere on site.

Why it feels like a person answered

The speed is what lets a cosmetic enquiry feel like a person picked up. Replies land in about 480 milliseconds, ninety-fifth percentile under 700, on a native pipeline rather than a third-party wrapper, so reading ModMed live adds little to the call. The platform runs 99.9% uptime and 1000+ concurrent calls, and turn-taking uses both silence and sentence completion, so a caller describing a concern is not cut off mid-thought by a plain timer.

Frequently asked questions

How does it tell a medical concern from a cosmetic one?

From the description, not a menu. It resolves the reason and the urgency from natural speech, routes a clinical concern to a medical slot with the escalation triggers checked, and a cosmetic request to a consult, so the two halves of the practice stay separate.

Does it take deposits for cosmetic appointments?

Where the practice configures it, a cosmetic booking can collect a deposit or set up payment on the call. The rule for which visit types require one is yours, and the agent applies it rather than deciding on its own.

Will it create duplicate charts in ModMed?

No. A returning caller is resolved to their existing chart before anything is written, using a date-of-birth check, and when two records look equally plausible the call goes to a person instead of a guess. That is what keeps a patient's medical and cosmetic history on one chart rather than split across two.

Does it work after hours for cosmetic enquiries?

Yes, every hour, at any volume, with no busy signal. Cosmetic enquiries that used to hit voicemail in the evening are answered and booked, and anything clinical still follows your escalation rules for out of hours.

Is patient data ever used to train models?

No. No model behind the conversation is trained on patient information. It is encrypted throughout, kept only as long as the record requires, and covered by the business associate agreement that governs every ModMed call the agent handles.

Hear it sort a mixed call list

The call mix worth judging on a ModMed line is the real one: a changing mole, a filler enquiry, a refill and a biopsy result, back to back. That is where separating medical from cosmetic and placing each correctly either holds or does not.

See how the same connection runs on other systems across integrations, or hear a mixed derm call list handled live when you book a demo.