The Manager Call Review Workflow: A Week in Twenty Minutes

A call review workflow that works for one practice falls apart at ten. The single-site version assumes a manager who knows the staff, recognizes the regulars, and can tell from two sentences whether a call went badly. A regional manager covering ten locations has none of that context and roughly the same twenty minutes, which means the workflow has to do the noticing on their behalf.

What usually gets built instead is a rollup. Total calls, average handle time, answer rate, sliced by site, delivered monthly. It is genuinely useless for this job. Averages across sites hide the site that is failing, monthly delivery means a problem runs for four weeks before anyone sees it, and none of those measures tell a manager which specific call to open. So regional managers do what they have always done, which is find out about phone problems when a practice manager escalates one, long after it started.

Comparison is the whole point, and it needs a rate

The one thing a multi-site manager can do that a single-site manager cannot is compare. That is the entire analytical advantage of the role and most reporting throws it away by reporting counts.

Counts track site size. A location with three physicians will always have fewer flagged calls than one with twelve, so a ranked list of raw exception counts just re-sorts the portfolio by volume and tells the manager nothing. Every comparison across sites has to be a rate: exceptions per hundred calls, unbooked new-patient calls as a share of new-patient calls, escalations as a share of total.

With rates, outliers become obvious and interesting. One site running double the portfolio rate for unbooked new-patient calls is a specific, checkable finding, and it usually turns out to be one thing: a template with no new-patient slots, a staffing gap at a particular hour, a phone tree option pointing at a voicemail nobody empties.

The useful default view is therefore not a list of sites. It is a list of metrics where at least one site is well outside the portfolio distribution, which is a much shorter list and reads in about a minute.

Weekly, not monthly, and the same day each week

Monthly reporting is the wrong cadence for phone operations because phone problems are usually caused by something that changed, and the useful window for finding the cause is days.

A staffing change, a new phone tree option, a template edit, a provider going out. Each of those produces a step change in the numbers, and a step change is easy to spot in a weekly series and nearly invisible in a monthly average. By the time a monthly report shows a degraded number, the manager is reconstructing what happened four to six weeks ago at a site they do not sit in.

Weekly also matters for the habit. The review has to be a standing slot on the same day, because a review that happens when someone remembers happens for two months and then stops. The content should be identical each week: the outlier list, the escalation view, and last week’s open items.

Twenty minutes buys three screens

The workflow has to fit a realistic amount of attention, and the honest budget is three screens.

First, the outlier list described above. Which metrics have a site outside the normal range this week, with the direction and the size of the gap. This is scanning, not reading.

Second, the escalation view. Every call at every site that hit a phrase on the practice list, with time from phrase to a human on each. This one gets read in full regardless of length, because it is short by construction and because it is the view with actual exposure attached. It is also where a manager notices that one site’s escalation times are systematically longer, which is a staffing or routing fact rather than a training one.

Third, a small number of actual transcripts, chosen by the exception rules rather than by the manager. Five is enough. The purpose is not analysis, it is calibration. A manager who has not read a real call in a month starts making decisions from metrics that have quietly stopped meaning what they used to.

Everything else, the volume charts, the handle times, the full transcript archive, should exist and should not be part of the weekly pass. They are for answering a specific question once you have one.

Standardize the rules centrally, let the thresholds vary

The mistake portfolios make in both directions is either letting every site define its own quality rules or forcing one identical threshold on all of them.

What should be identical across the portfolio: the disposition categories, the definition of an exception, the escalation phrase list, and the scored fields. Without that, no comparison means anything, and the manager spends the review arguing about definitions instead of about performance. This is the single highest-value thing a central operations team can standardize, and it is much easier to do before sites have their own conventions than after.

What should vary: the thresholds that trigger attention. A pediatric urgent care site and a surgical specialty office have genuinely different normal call lengths and different reasonable rates of transfer to staff. Holding them to one number generates noise at one site and misses real problems at the other.

The practical form is a portfolio-wide schema with per-site expected ranges, reviewed quarterly. It sounds bureaucratic and it takes an afternoon.

The findings that repeat across sites are the valuable ones

Single-site review finds single-site problems. The reason to run this centrally is the class of finding that only appears when you look across a portfolio.

The same three questions arriving at every location, which usually means the website says something the practice does not do. A callback rate that spikes at every site on the same weekday, which is a central staffing pattern rather than a local one. An insurance question the automation handles inconsistently across sites, which means the payer configuration was done locally and should not have been.

Those findings are worth more than anything in a per-site review, because one fix resolves them everywhere. They are also completely invisible to any individual practice manager, which is the argument for the regional workflow existing at all.

So the weekly review should end with an explicit question rather than only a site list: what showed up at more than one location this week. Asking it out loud is what turns ten site reviews into a portfolio review.

Key Takeaways

Compare on rates, never counts. Ranked exception counts just re-sort the portfolio by site size and tell a manager nothing.
Lead with an outlier list: the metrics where at least one site sits outside the portfolio distribution. That reads in a minute and is where the work is.
Review weekly on a fixed day. Phone problems come from a change, and step changes are obvious in a weekly series and invisible in a monthly average.
Budget three screens: outlier list, escalation view read in full, and five exception-selected transcripts for calibration. Everything else is for answering a question you already have.
Standardize dispositions, exception definitions, escalation phrases and scored fields across the portfolio. Let per-site thresholds vary, reviewed quarterly.
End every review by asking what appeared at more than one site. Cross-site patterns are invisible to practice managers and one fix resolves them everywhere.

The regional version of call review is a different job from the practice version, and building it as a bigger dashboard is why so many portfolios have reporting nobody uses. What a multi-site manager needs is not more data about each location. It is a short, comparable, weekly view that points at the two sites worth a phone call and the one pattern that is showing up everywhere. Twenty minutes is genuinely enough for that, but only if the workflow has already decided what deserves the attention.

Sources