A patient calls your practice.
- They go to voicemail.
- They do not leave a message.
- They call the next practice on their list.
You don’t know this happened. Your phone log shows one missed call.
Most practice owners have a strong internal narrative about what their patient experience looks like. The clinical care is excellent. The staff is warm. The facility is well-maintained. These things are true. And they are almost entirely irrelevant to the question a new patient is answering when they decide whether to book.
The question is not: ‘Is this a good practice?’
The question is: ‘Does this practice respond?’
- 78% of patients report that response time is the #1 factor in choosing between two comparable practices.
- 47% of patients who go to voicemail on their first call do not call back.
- 1 hour the window within which a patient inquiry, if unanswered, significantly increases the probability of churn.
- 3× patients are 3x more likely to leave a negative review about administrative experience than clinical quality.
These numbers describe a gap between what practice owners believe their patient experience is and what patients are actually encountering. The clinical quality is real. The response time problem is also real. And for the patient deciding whether to return, the second one often outweighs the first.
| Scenario 1: The New Patient Who Called Once |
What the patient thinks: “I tried calling. Nobody picked up. I don’t know if they got my voicemail. I’ll try somewhere else.” What the patient does next: Calls the next practice on their list. Books there. Your practice never knew they were considering you. |
| Scenario 2: The Existing Patient With an Urgent Question |
What the patient thinks: “I’ve been calling for two days. I’m not sure this practice takes my situation seriously.” What the patient does next: Starts thinking about switching. May not mention it to anyone. Your retention number drops by one — silently. |
| Scenario 3: The Returning Patient Who Needed a Callback |
What the patient thinks: “They said someone would call me back. It’s been four days. I guess I’ll just go to urgent care.” What the patient does next: Goes to urgent care. Solves their immediate problem. Begins thinking of your practice as unreliable. Does not book their next annual visit. |
| Scenario 4: The Patient Who Got a Fast Response |
What the patient thinks: “They picked up right away. I had my question answered in three minutes. I’m definitely going back.” What the patient does next: Books their next appointment. Mentions the experience to a friend. Leaves a five-star review about how easy it was to reach someone. |
The difference between scenarios one through three and scenario four is not clinical quality. It is response infrastructure.
What Patients Expect vs. What Most Practices Deliver
Patient expectations around response time have shifted significantly in the past five years. The Amazon effect — the normalization of same-hour response across consumer industries — has changed what patients consider acceptable from every service they interact with, including their medical practice. The bar has moved. Most practices’ response infrastructure has not moved with it.
| Channel | Patient Expects | Industry Average | What Happens When the Gap Isn’t Closed |
| Phone call (business hours) | Answered live | 60%+ go to voicemail | New patients choose the next practice that answers. Existing patients question the practice’s accessibility. |
| After-hours inquiry | Response by 9am next day | Often 24–48 hrs, if at all | Patient assumes the practice is unresponsive and either self-resolves (urgent care) or switches. |
| Callback request | 2–4 hours | Often end of day or next day | Patient feels deprioritized. Urgency has passed. Relationship erodes by one notch. |
| Appointment confirmation | Proactive outreach 24–48 hrs before | When staff remember to call | No-show rate increases. Revenue gap opens. Staff scrambles same-day. |
| Billing question response | Same business day | 1–3 days, sometimes longer | Patient frustration escalates. Reviews get written. Finance team absorbs more time. |
| Referral status follow-up | Proactive update within a week | Patient usually has to call and ask | Patient feels like the practice lost the referral. Trust decreases. |
Every row in this table represents a gap between what the patient expects and what they actually receive. Each gap is a small withdrawal from the trust account. And trust accounts in medical practice work exactly like real ones: a series of small withdrawals, each unremarkable on its own, eventually produces a balance the practice did not see coming.
Why Response Time Fails: It’s Not a People Problem
The instinct when response time is slow is to address the people. More training. Clearer expectations. A meeting about picking up the phone. This instinct is wrong — not because the people are not capable, but because the problem is structural, not personal.
Here is the structural reality of response time in most medical practices.
Your front desk is managing too many functions simultaneously to respond fast to any of them.
The same person who is answering the phone is checking in the patient who just walked in, processing an insurance question, and fielding a question from a clinical staff member. They cannot give the phone call the attention it deserves because the phone call is competing with everything else that is happening in real time. Speed of response requires dedicated bandwidth. Most practices do not have dedicated bandwidth. They have one person doing five things.
There is no defined response time standard, so there is no way to measure or improve it.
If a practice has not defined what ‘same-day callback’ means in operational terms — which hours, by whom, tracked how — then ‘same-day callback’ is a hope, not a standard. And hopes are not measurable, not accountable, and not improvable. The response time problem persists not because nobody cares but because nobody has built the infrastructure to care systematically.
After-hours response does not exist as a function.
Most practices’ response capability ends when the last staff member leaves. Inquiries that arrive after 5pm are answered the next morning at the earliest — if they are caught before the morning rush buries them. For a patient who reached out with an urgent question at 6pm, a response at 10am the next day is not a response. It is confirmation that this practice is not accessible when they actually need it.
Follow-up is tracked by memory, not by system.
The callback that was supposed to happen by end of day gets bumped by a higher-urgency task and lands on the next morning’s mental list. The next morning’s list is already full. The callback happens on Day 2. Or it does not happen, and the patient calls back on Day 3 to ask what happened. In either case, the experience has already formed. The patient has already made a mental note about this practice’s reliability.
Slow response time is not a character flaw in your team. It is the predictable output of a staffing model that asks one person to answer every call, manage every inquiry, and track every follow-up — while also doing everything else.
What Fast Response Actually Requires
Response time is not a metric you improve by telling people to be faster. It is a metric you improve by building the infrastructure that makes fast response the default.
A Follow-Up System That Does Not Depend on Memory
What a Well-Deployed VMA Does to Your Response Time
The VMA’s job is not to be faster than your front desk. It is to be singularly focused on the one function your front desk cannot be singularly focused on while also managing a full waiting room.
