Two practices, one phone number

A dermatology practice is two businesses sharing a phone number. Cosmetic and medical schedule differently, pay differently, wait different lengths of time, and want entirely different things from the person who answers. Every single call begins with working out which one you are dealing with.

Get it wrong and the cost is not evenly distributed. Long lead times mean a cosmetic slot that goes unfilled is not a gap in the diary, it is a significant amount of revenue that will not be recovered, and the waitlist that should have refilled it only gets worked when somebody has an afternoon spare. Meanwhile the volume that actually sustains the practice - annual skin checks, post-op reviews, repeat treatments due on an interval - depends on somebody ringing patients who were never going to ring first. And underneath all of it sits the conversation nobody enjoys: explaining to a patient that they cannot have their next treatment yet.

2 rule sets

Cosmetic and medical availability kept properly separate

Every recall

Held to its clinical interval rather than to a spare hour

0

Cross-booked slots between the two sides of the practice

Answering is the easy half. What decides whether a front desk gets its hours back is where the work lands afterwards, and that is the part most tools skip. A booking request emailed to your team is not an integration; it is a second queue with better marketing. the platform answers the call, resolves what it can, and writes the result into ModMed while the caller is still on the line - the appointment against live availability, the intake as structured fields, the follow-up as a task in the queue your team already works. Nothing waits for a nightly sync and nothing needs rekeying in the morning. The ModMed integration page shows exactly what moves in each direction.

The agent works out which side of the practice a caller needs from how they describe it, then applies that side's booking rules, lead times and payment handling without ever asking them to choose from a menu. Cancelled high-value slots trigger the waitlist within minutes rather than at the end of the day, and recall runs from your own interval instead of waiting for the phone to ring. When someone calls too early for a repeat treatment they are offered the first date that is actually appropriate, with the reason explained - so the awkward conversation happens without a member of staff having to have it.

How it connects

Real time

Written while the patient is still on the line. Every write logged and reversible.

Where it stops

It does not triage, and that boundary is deliberate rather than a limitation. The moment a call stops being administrative - a red-flag description, an urgent caller, a question that needs clinical judgement - it is escalated to a person, in seconds, with the transcript already attached so nobody starts cold. The agent will not guess, and it will not advise. For a practice being asked to put an AI in front of its patients, that refusal is usually the thing that makes the rest acceptable, and it is why the compliance posture behind it - HIPAA, GDPR and DPDP, encrypted in transit and at rest, every write logged and reversible - matters as much as the booking logic.

Seeing it rather than reading about it

Dermatology covers the workflow in more depth, and other practices describe what changed once it was running. But the fastest way to judge a voice agent is to be on the other end of one. The demo will call your phone in under a minute, running whichever scenario you pick, or you can book fifteen minutes and we will point it at your own call flows and let you try to break it.