Front desk KPI

Time to Schedule KPI

Time to schedule measures how long it takes from a patient first asking for an appointment to having one booked, separate from how far out it is.

Booking speed is not appointment availability

Two waits shape a patient's access to care. One is the wait for the visit itself, which depends on provider capacity. The other is the wait to get booked at all: the phone tag, the voicemail, the request to hold while someone checks. This metric is about the second wait, the one the front desk controls.

A patient who has asked for an appointment and does not have one yet is still shopping. The longer they wait to be booked, the more likely they book elsewhere or decide not to come.

From first request to a booked slot

Find the patient's first request: the first inbound call about an appointment, a portal request or a web form. Find the moment the appointment was created in the EHR schedule. Time to schedule is creation time minus first request time. For patients booked during the first conversation, it is the length of that call. For everyone else, it includes every missed connection in between. Report the share booked on first contact as well as the typical time for the rest.

What adds days to a simple booking

The first call goes unanswered or into voicemail. The scheduler who does answer needs information the patient does not have at hand. The visit type requires a nurse's input before anything is booked. Or the scheduler is in the middle of another task and takes a message instead of booking on the spot. Each of these turns a few minutes of work into a cycle of return calls.

Making the first call count

An AI receptionist can shorten time to schedule by making the first contact productive. Katie answers immediately, even when every line is busy, and Annie picks up after hours. Scheduling calls are handled against the visit types and appointment lengths your practice sets. Each call ends with a structured summary, so whatever still needs a person arrives as a written request with details rather than as a missed call.

It does not change how far out the next available visit is. If your provider schedule is full for weeks, faster booking gets the patient a slot sooner in the process, not sooner on the calendar. Track the two separately so neither takes credit for the other. When a request still needs staff to book it, the clock runs until they do, so how quickly summaries are worked counts here too.

Measuring new patient requests first

Set your own baseline from a sample of new patient requests, since they show the effect most clearly and are the most likely to go elsewhere. After a change, compare the share booked on first contact and the time for the rest. Count requests that never became a booking, because a faster time across fewer bookings is not an improvement.

Frequently asked questions

How do we find the first request if the patient called several times?
Search your call log for the patient's number in the days before the booking. The earliest call about scheduling starts the clock.
Should we include follow-up visits booked at checkout?
Exclude them. They are booked in person at the end of a visit and have no request wait. Including them makes the metric look better than what patients experience on the phone.
Is this the same as days to the next available appointment?
No. That measures provider capacity. Time to schedule measures how long it takes the practice to book a request, whatever date the appointment lands on.
What about requests that need a nurse before booking?
Keep them as their own group. The clinical review adds necessary time, and you want to see it rather than bury it inside the overall figure. If those requests are slow, check how quickly the nurse receives a complete request.

Put this KPI to work in the operations playbook it belongs to, or browse the rest of the KPI library.