ROI Analysis
Four Front-Office Numbers Worth Showing Your Partners
Partner meetings run on revenue and volume, which hide the front office entirely. Four front-office numbers that explain what those two are actually doing.
Partner meetings run on two numbers, revenue and volume, and both of them are lagging summaries of things that already happened. The front-office numbers that explain why revenue moved rarely make it into the room, which is how a partnership ends up debating a result nobody can trace.
It is not that the data is missing. It is that nothing in a standard financial packet describes the front door, so the conversation defaults to the two totals everyone already knows.
A partnership that only sees revenue and volume can tell that something changed. It cannot tell whether patients could not get through, could not get booked, or got booked and never came back for the second half of what they started.
Number one: requests that never became an appointment
The first number is the one nobody keeps, because the record of it disappears with the call. How many people contacted the practice wanting to be seen and did not end up on the schedule.
That is not the same as a booking count. Bookings tell you about the people who succeeded. This tells you about the ones who did not, and it is the only number in the set that measures demand you failed to convert rather than demand you served.
What makes it findable is treating every inbound request as an object with an outcome rather than as a conversation that ended. Booked. Referred elsewhere. Could not be scheduled for a reason worth recording. Never reached again after the first contact.
Bring the reasons, not just the total. A partnership that hears we lost 60 requests last month will argue about the number. A partnership that hears 60 requests did not convert, and 22 of them were the same coverage question, will fix the coverage question.
Number two: how much of the phone is one repeated question
The second number is the composition of your phone volume, and it is the one that changes what partners believe about staffing.
In a March 10, 2026, MGMA Stat poll, practice leaders named the most time-intensive phone tasks for their staff as eligibility and prior authorization at 45%, scheduling at 31%, intake at 9%, prescription refills at 6%, and other at 9%. Coverage questions consume more staff time than booking does across medical groups generally.
In sleep medicine the local version usually looks different, and that is the point of measuring your own. Equipment and supply reorder calls tend to arrive on the same line as new-patient requests, and they behave differently. They are frequent, short, largely identical, and they compete directly with the calls that create new revenue.
Report the mix rather than the volume. Total calls is a number that grows every year and tells a partnership nothing. The share of calls that are one repeated, resolvable question is a number that suggests an action.
Number three: the sequence completion rate
The third number is the one most specific to this specialty, and it is the complication that makes generic front-office reporting useless here.
A sleep medicine episode is not a visit. It is a sequence, and patients routinely drop out of it midway. A study is one appointment type with its own prep and its own authorization rules, a follow-up is another, and the front office is expected to carry the patient across all of them without anything in the schedule enforcing the link.
Native reminders make the drop-off worse in a predictable way. They fire on the chronologically first appointment, so a patient with two appointments gets reminded about one of them. The second leg becomes a no-show that gets recorded as a patient who did not show up, when what actually happened is a patient who was never reminded.
So measure completion of the set, not attendance at each appointment. What share of patients who started the sequence finished it, and where in the sequence the drop happens. The automation can confirm each leg separately and raise the ones where a leg is missing entirely. What it cannot do is decide what the patient needs next, which stays with the clinician and shows up in the sequence as an order the front office then works.
Number four: how long open work sits before somebody touches it
The fourth number is aging. Not how much work exists, but how long it waits, which is the difference between a busy practice and a leaking one.
Open patient cases carry an age, and the distribution of that age is the honest picture of front-office capacity. A practice with 200 open items where the oldest is four days is fine. A practice with 60 where a third are past three weeks has a queue nobody is working, and the totals look better at the second practice.
Pick the thresholds before you look at the data, so nobody negotiates them afterwards. Open past one day, past a week, past a month. Then report the count in each bucket every month, in the same units, so the trend is readable at a glance rather than reconstructed each time.
Aging is also the number that survives a staffing change. Volume rises and falls with the season and the referral pattern. How long work sits is a direct measurement of whether the practice can keep up with itself.
Set the expectation about what automation changes
Once these four numbers exist, somebody will propose automating against them, and the partnership will want to know what to expect. Be accurate rather than optimistic, because the first overpromise costs you the next three proposals.
When MGMA asked practices using AI in patient visits about the effect on staff workload, about 44% said it has not reduced workload, 39% said it has, and 17% were unsure. Practices reporting broader use were more likely to report a positive effect. That is a mixed result and it is worth quoting honestly in a partner meeting.
The honest framing is redeployment rather than reduction. Repetitive, complete work gets absorbed. The exceptions still route to a person, and the person is now spending their time on the exceptions instead of on the reorder call that arrives forty times a week.
Which is why these four numbers are the right ones to agree on before anything changes. Requests that did not convert, phone mix, sequence completion, and aging are all measurable now, with the same definitions afterwards. A partnership that sets its baseline first can tell whether anything worked. One that does not will be arguing about revenue again in six months.
Key Takeaways
- Report requests that never became appointments alongside bookings, because bookings only describe the patients who got through.
- Bring the reasons behind the non-conversions, since a partnership will argue about a total and act on a named cause.
- Measure the composition of phone volume rather than the count, and name the one repeated question that is eating the most staff time.
- Score sequence completion instead of per-appointment attendance, because a sleep episode spans several linked appointments and drop-off happens between them.
- Age your open patient cases against thresholds chosen in advance, since how long work waits is a better capacity signal than how much exists.
- Set the four baselines before automating anything, and describe the expected effect as redeployed staff time rather than reduced headcount.
A partnership cannot manage a front office it never sees, and revenue and volume do not show it. Four numbers fix that: requests that did not convert and why, what your phone volume is actually made of, how many patients finish the sequence they started, and how long open work sits before anyone touches it. All four come off athenaOne, all four hold their meaning over time, and together they explain the two numbers your partners were already arguing about.
Related reading
- building a front-office scorecard that survives contact with a partner meeting
- what patient case close reasons tell you
- carrying a patient from the study to the follow-up
Sources
Ready to See It in Action?
See how PGA reports the four athenaOne front-office numbers a sleep medicine partnership actually needs
Schedule a Demo →Written by Kevin Henrikson