Key takeaways
- A callback is only closed when the patient has been told the outcome, not when a staff member reads the note.
- Give every message one owner, one due time and one status; shared inboxes without owners are where calls get lost.
- Use one intake form for all message types so nothing depends on who answered the phone.
- Review open and overdue messages twice a day and track reopen rates to find weak handoffs.
Why unreturned messages pile up
Most practices do not lose callbacks because staff are careless. They lose them because a message moves through three or four hands, sits in a shared queue with no named owner, and nobody is sure whether the patient was ever told the answer. The phone still carries much of that traffic. The Medical Group Management Association notes that the phone often remains the real front door for a large share of patients, even in practices that have portals and automated reminders, and that it still takes a disproportionate share of staff time[1].
The written channel is growing too. In an MGMA poll, 70% of medical groups said patient portal message volume rose in 2024 and only 1% saw a fall[2]. Physicians already spend a large part of the day on inbox work: one time-and-motion study of primary care physicians found inbox management took 85 minutes a day, close to a quarter of their EHR time[3]. A callback system has to fit that reality. It should move simple requests away from clinicians and make clinical requests easy to answer in one pass.
70%
of medical groups reported higher patient portal message volume in 2024[2]
What a closed loop actually means
A closed loop has four parts. If any one is missing, the message is still open, whatever the status field says.
- An owner: one named person or one role queue with a named lead for the day. Never a shared inbox with no owner.
- A due time: set at intake from the message type, written as a clock time, not as soon as possible.
- A status that changes: new, in progress, waiting on clinician, waiting on patient, closed.
- A patient update: the patient hears the answer, or hears exactly when they will hear it. The closing note records who spoke to whom, when and what was said.
The fourth part is the one most systems skip. A nurse can review a refill request, approve it and mark it done, while the patient still calls back two days later because nobody told them it went to the pharmacy. Counting that second call as new work hides the real problem.
Set up the system in six steps
List your message types
Pull two weeks of phone messages and sort them. Most practices end up with eight to twelve types: appointment change, refill, test result question, referral status, records request, billing question, form or letter, clinical symptom question, and other. Keep the list short enough that staff pick the right type without thinking.
Agree one intake form
Every message, whether taken live, from voicemail or from the portal, goes onto the same form in the same place, ideally the EHR task or messaging module so it stays with the chart. Paper notes and sticky pads are retired.
Map each type to an owner queue
Refills go to the medication queue, test questions to the clinical team for that provider, billing to the billing queue. Each queue has a named lead each day who watches the clock and reassigns when someone is out.
Set a due time per type
Clinical symptom questions get the shortest window, routine administrative requests the longest. Write the due time onto the task at intake so it is visible in the queue.
Define closure
A task closes only when the patient update is documented: spoke to patient, left an approved message, or sent a portal reply that the patient can read. Two failed attempts plus a letter or portal message is the usual floor for unreachable patients.
Audit twice a day
At mid-morning and mid-afternoon the queue leads review anything due within two hours and anything overdue. Overdue items are escalated, not silently pushed to tomorrow.
The intake fields that prevent a second call
Most repeat calls trace back to an incomplete first message. A callback that starts with a wrong number, a missing pharmacy or an unclear question turns one task into three. Build the form so the person taking the message cannot skip the fields that matter.
| Field | Why it matters | Example entry |
|---|---|---|
| Patient name and date of birth | Two identifiers before anything else | Example: Dana Ruiz, 04/11/1979 |
| Best callback number and times | Avoids missed return calls during work hours | Example: mobile, after 3 pm |
| Permission to leave a detailed message | Controls what can be said on voicemail | Example: yes, mobile only |
| Message type | Drives the owner queue and the due time | Example: refill |
| The question in the caller's words | Lets the clinician answer without calling to ask | Example: needs blood pressure refill, 2 pills left |
| Pharmacy or destination | Refills and records go to the right place first time | Example: Main St pharmacy |
| What the patient was told | Sets the expectation you must meet | Example: told answer by 4 pm tomorrow |
Records requests deserve their own type because they carry a legal clock. Under the HIPAA Privacy Rule, a covered entity must act on a patient's request for access to their records no later than 30 days after receipt, with one extension of no more than 30 days[4]. Logging the received date on the task makes that deadline visible instead of relying on memory.
Where the phone time goes
When MGMA asked practice leaders which phone tasks take the most staff time, eligibility and prior authorization came first, followed by scheduling, with intake and refills far behind[1]. That is a useful guide for where to set up dedicated queues first: the categories that eat the most time are also the ones most likely to generate a follow-up call if the first contact ends without a clear next step.
Use the chart as a starting point, then compare it with your own two-week sample. If your sample shows that a type such as referral status makes up a large share of messages, give it a queue and a named lead even if it is not on the national list.
Scripts for each stage of the loop
Staff should say the same few things every time so patients know what to expect and so expectations match the due time on the task.
- Taking the message: βI have written down your question for Dr. Patel's nurse. You will hear back by 4 pm tomorrow at the mobile number you gave me. If anything gets worse before then, call us back and tell whoever answers.β
- Closing with the answer: βI am calling with the answer to your question from Monday. The prescription was sent to Main Street Pharmacy this morning. Is there anything else you were waiting on from us?β
- Closing when the answer needs more time: βDr. Patel needs to see your lab results first. They are expected Thursday. I will call you Thursday afternoon either way.β
- Leaving a minimum-necessary voicemail when no detailed-message permission is on file: βThis is the office of Dr. Patel calling for Dana. Please call us back at the main number. There is no need to worry; this is a routine follow-up.β
If the caller describes symptoms that could be urgent, the callback process is the wrong path. Staff follow the practice's triage protocol and warm-transfer to a nurse or direct the caller to emergency services instead of taking a message.
Worked Example: one queue lead's afternoon
Example: a four-provider family practice has 46 open messages at 1 pm. The queue lead filters for items due before 5 pm and finds 19. Twelve are refills already approved by the nurse, so a medical assistant spends 40 minutes making closing calls and logging the outcomes. Four are test result questions waiting on a provider; the lead flags them in the provider's inbox with the due time. Three are billing questions that were sent to the clinical queue by mistake; she moves them and adds a note to the intake training sheet.
By 4 pm, two messages are overdue because the patients did not answer. Both get a second attempt and a portal message, and the tasks move to waiting on patient with a new due time rather than closed. The next morning the lead reviews the misrouted billing messages with the person who took them. Nothing about the day required new software; it required a named owner, visible due times and a definition of closure everyone used.
Measures to review every week
- Overdue at end of day: the count of messages past their due time when the office closes. The goal is close to zero.
- Median time to close by message type: compare with the due time you promised patients.
- Repeat calls about the same issue within seven days: the clearest sign the loop did not close.
- Misrouted messages: tasks moved from one queue to another, which point to intake training gaps.
- Unreachable rate: tasks closed after failed attempts, which may mean callback numbers are wrong at intake.
Keep the report to one page and review it at the weekly operations huddle. If repeat calls fall and overdue counts stay low for a month, the system is working. If not, look first at the intake fields and the owner coverage on days when staff are out, since those are the two places most loops break. Related guides cover setting callback time standards and handling test result calls.
Frequently asked questions
Should every phone message go into the EHR?
Yes, where possible. Messages kept in the EHR task or messaging module stay with the chart, can be assigned and timed, and leave an audit trail. Paper notes and personal email cannot be tracked or handed over when someone is out.
How many attempts should staff make before closing an unreachable callback?
Many practices use two phone attempts at different times of day plus a portal message or letter, all documented. Clinical results that need action may need more steps under your own policy, so set that rule with your clinical lead.
What is the difference between a message being read and a message being closed?
Read means a staff member has seen it. Closed means the patient has been told the outcome or told exactly when to expect it, and the note records who said what and when.
Who should own the callback queue?
Each queue needs a named lead for the day, usually a senior medical assistant, nurse or front desk lead. The lead does not have to make every call, but they watch due times and reassign work when someone is absent.
References
Medical Group Management Association (MGMA) (2026). Phones are still a bottleneck costing medical practices time they can't afford (opens in a new tab) β
Medical Group Management Association (MGMA) (2024). Ensuring accurate coding and billing for patient portal messages as e-visits (opens in a new tab) β
Annals of Family Medicine (2017). Tethered to the EHR: Primary Care Physician Workload Assessment Using EHR Event Log Data and Time-Motion Observations (Annals of Family Medicine, 2017) (opens in a new tab) β
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR Β§ 164.524 - Access of individuals to protected health information (opens in a new tab) β