Front desk KPI
Hold Time KPI
Hold time measures how long patients wait on the line before reaching someone, from the typical call to the longest waits of the day.
Waiting is the first impression
Before a patient meets your staff or your physicians, they meet your hold music. A long hold tells a new patient what the practice will be like, and tells an established patient that their call is not a priority. Hold time also spends the patient's own day: a parent calling on a work break, someone calling from a parked car.
For staff, long holds mean every call starts with an apology. That small tax on morale adds up over a week.
Queue time versus mid-call hold
Phone systems report waiting in two different ways, and it helps to separate them. Queue time is how long a caller waits before anyone answers. Mid-call hold is how long a caller waits after being answered, while staff look something up or check with a nurse. For each, take total seconds on hold divided by the number of calls that held, over the same period, and report the share of calls that held at all beside it. Then look past the average to the longest waits, because the average hides the callers who suffered most.
- Queue time: from entering the queue to being answered
- Mid-call hold: time placed on hold during an answered call
- Longest waits: the slowest calls each day, read by hour
What stretches the wait
Hold time rises when calls arrive faster than people can finish them. That happens when volume peaks at the start of the day, when calls run long because staff are searching several screens, and when the same people are also checking patients in. Mid-call holds grow when the answer lives with someone else, such as a nurse or the billing office, and the receptionist has to go find it.
An answer with no queue in front of it
An AI receptionist removes the queue for the calls it handles. Katie answers immediately, including when every line is busy, so callers routed to her do not wait for a free person. Routine questions are handled on the spot, and requests that need staff end with a structured summary rather than a long hold while someone walks across the office.
Calls you choose to transfer to a person can still wait if staff are busy. If you send the AI only your overflow, the human queue will still show hold times; read them together with the share of calls the AI answered.
Measuring change without a misleading average
Set your own baseline across several typical weeks, broken down by hour of day. After a change, compare the same hours and watch the longest waits as closely as the average. Check whether a change came from fewer callers holding at all or from shorter waits for those who did. Both are useful, but they mean different things.
Frequently asked questions
- Should calls that hang up while holding count?
- Yes. Include their wait, because they experienced it. Count the hang-ups themselves under call abandonment, so each metric stays focused on one thing.
- Does offering a callback option reduce hold time?
- It shortens what your report shows, but the patient still waits for the return call. If you offer one, measure the time to that callback alongside hold time so the wait is not hidden.
- Why measure the longest waits separately?
- Averages smooth over the experience of the patients who waited longest. Those are the callers most likely to complain, hang up or try another practice.
- Should we report the average or the median?
- Report both, next to the longest waits. The median shows the ordinary caller's experience, the average gets pulled up by a few very long holds, and the gap between them tells you how uneven your day really is.
Put this KPI to work in the operations playbook it belongs to, or browse the rest of the KPI library.