Key takeaways
- For a practice, a call is resolved when the patient’s need is met or handed to a named next step with a time the practice then keeps.
- Measure it three ways: repeat calls from the same number within seven days, disposition tags, and a one-question patient check.
- Most repeat calls trace back to a handful of causes: unclear callbacks, missing information, refill and prior authorization status, and messages that go unanswered.
- Every repeat call removed shortens the queue for everyone else, so FCR work often improves speed of answer and abandonment too.
What resolved means in a medical office
Contact centers define first call resolution as the share of contacts where the customer’s need is met on the first attempt, with no follow-up contact needed. A medical practice needs a slightly different definition, because many calls cannot be finished on the phone. A front desk staff member cannot answer a clinical question or approve a refill. What they can do is take the request to the right person, set a clear expectation and make sure the practice meets it.
A workable definition: a call is resolved on first contact when the patient’s need is met on that call, or when it is handed to a named next step with a time, and the patient does not need to call again about the same need before that time. A patient who calls back because nobody returned the message by the promised time counts as a repeat, even if the original call was handled politely.
That definition puts the focus where the workload is. Repeat calls add to the queue at the busiest hours and consume staff time twice for the same need. Practice leaders already name eligibility and prior authorization (45%) and scheduling (31%) as the most time-consuming phone tasks for staff[1]; repeats on top of those make the load heavier.
Three ways to measure it
No single method is perfect. Use at least two and compare them.
- Repeat-caller analysis. Export inbound calls with caller number and time for four weeks. Count numbers that called more than once within seven days. This overstates repeats slightly, since a family may call about different children, but it needs no extra staff work.
- Disposition tags. Ask staff to tag each call at the end with its purpose and outcome: resolved, handed off with a time, or unresolved. Run it for two weeks at a time, twice a year. Tags show which call types repeat most.
- A one-question check. When staff answer a call, they ask whether the patient has called about this before. A yes, with the reason, is recorded. It is quick and catches repeats through other channels too.
Report FCR as resolved-or-handed-off calls with no repeat within seven days, divided by all calls in the sample. Report the top three repeat reasons with it; the reasons are more useful than the rate.
The usual causes of repeat calls
| Repeat reason | Typical root cause | Fix at the desk | Fix in the process |
|---|---|---|---|
| “Nobody called me back” | No time given, or the callback list is not worked at a set hour | Always give a callback window and write it in the message | Work callback lists at fixed times; track overdue callbacks daily |
| Refill status | The patient does not know the request went to the clinical team or the pharmacy | Explain the steps and the usual timing | Send a status text or portal message when the refill is sent |
| Prior authorization status | The patient was not told what happens next or how long it takes | Explain the step and who will contact them | Update the patient when the request is submitted and when the payer answers |
| Missing information | The first call did not collect insurance, referral or records details | Use a checklist for new-patient and referral calls | Pre-registration form sent with the confirmation |
| Directions, hours, forms | Information hard to find elsewhere | Answer and point to the source | Put it in reminders, the greeting and the website |
| Test results | The patient was told to expect a call that did not come | Give the real process and time | Results release rules agreed with clinicians and explained to patients |
Status calls about refills and prior authorizations deserve special attention. Prior authorization alone consumes an average of 13 hours of physician and staff time each week, and 40% of physicians employ staff dedicated exclusively to it[2]. Every patient who calls to ask where their authorization stands adds to that load. A proactive status update, even one that says “still waiting on your insurer,” often prevents two calls.
Messages are part of first contact too
Repeat calls often start as unanswered messages. In a 2025 MGMA poll, 70% of medical groups reported an increase in patient portal message volume in 2024; only 1% reported a decrease[3]. A study of primary care physicians found inbox management took 85 minutes of their daily EHR time[4]. When messages wait, patients pick up the phone.
Source: Medical Group Management Association (MGMA), 2024[3]
Show the data
| Item | Value |
|---|---|
| Reported an increase | 70% |
| Reported a decrease | 1% |
Set and publish a response time for portal messages, route administrative messages to the front desk rather than the clinical inbox, and check overdue messages before the morning phone peak. Patients who are encouraged by their provider to use the portal access and use it at higher rates[5], so a reliable portal reply standard is one of the best ways to move routine requests off the phone.
Make callbacks reliable
The single most common promise at a front desk is “someone will call you back.” It is also the promise most often broken, usually not through carelessness but because nobody owns the callback list at a set time. A short callback standard fixes most of this.
- Every message records the patient’s best number, the reason in one line, who it is routed to and the promised callback window.
- Callback lists are worked at fixed times, for example mid-morning and mid-afternoon, by a named person for each list.
- Any message older than its promised window appears on a daily overdue list that the office manager reviews before lunch.
- If the answer is not ready by the promised time, the patient still gets a call or message saying so and giving a new time.
- Clinical messages follow the clinical team’s own standard, but the front desk can see whether they are overdue and tell a patient who calls.
Measure the share of callbacks completed within the promised window for one week each month. When that share rises, repeat calls fall, because most patients call again only when the window passes in silence. It is one of the cheapest improvements a practice can make, and it needs no new system: a shared list, a set time and a named owner are enough.
Walk-ins count too. A patient who comes to the desk to ask about a message they left yesterday is a repeat contact. Ask desk staff to log these for the same two-week measurement periods so the picture is complete.
Build an FCR habit in five steps
Agree the definition
Write the definition above, with the seven-day window, into the front desk procedures. Make sure everyone counts the same way.
Measure two weeks
Run disposition tags for two weeks and the repeat-caller export for the same period. Note the top three repeat reasons.
Fix one reason
Pick the most common repeat reason and change one thing: a script, a status message, a callback time. Do not try to fix all three at once.
Close every call the same way
Train the closing script below. It catches the second question on the first call instead of on a second call.
Re-measure in a quarter
Repeat the two-week measurement and compare the repeat reasons. Move on to the next reason once the first has fallen.
Closing script: “So I have it right: I’ve sent your refill request to Dr. Lee’s team, and you should hear from the pharmacy or from us by tomorrow afternoon. If you haven’t, call us and mention today’s request. Is there anything else I can help with while I have you?”
Example: one repeat reason, fixed
Example: a fictional dermatology practice runs disposition tags for two weeks and finds that about one in six calls is a repeat. The largest group is patients asking whether a prior authorization for a medication has been approved. Staff had been saying “we’ll let you know,” with no time or method given.
Example, continued: the practice adds two steps. When a request is submitted, the patient gets a portal message or text explaining that the insurer usually takes several business days and that the practice will send an update when it hears back. When the payer responds, a second message goes out. The scripted answer for status calls now gives the submission date and the next expected update. At the next measurement, repeat calls about authorizations have dropped noticeably, and the morning queue is shorter. These figures are illustrative.
What not to do
- Do not pressure staff to finish clinical questions on the phone to improve the rate. A correct handoff with a kept time counts as resolved.
- Do not count a call as resolved because the caller hung up satisfied. Check whether they called again.
- Do not measure only the phone. Repeats move between phone, portal and walk-ins.
- Do not publish individual FCR league tables. Repeat calls are usually caused by process gaps, not by the person who answered.
First call resolution sits alongside average speed of answer and call abandonment rate, and it feeds new-patient call conversion: a new patient who has to call twice often does not.
Frequently asked questions
How do you measure first call resolution in a medical practice?
Count calls that were resolved or handed to a named next step with a time, and that had no repeat call about the same need within seven days. Use phone data for repeats and disposition tags for reasons.
Does a clinical question routed to a nurse count as resolved?
Yes, if the patient was given a clear next step and time and did not need to call again before then.
What causes most repeat calls?
Usually missed or vague callbacks, status questions about refills and prior authorizations, missing information from the first call, and unanswered portal messages.
How does FCR affect the phone queue?
Each repeat call adds to the queue, often at peak times. Reducing repeats shortens waits and lowers abandonment for every caller.
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) ↑
American Medical Association (2026). AMA survey: Prior authorization reform pledge falls short with physicians (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) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024 (Data Brief No. 77) (opens in a new tab) ↑