Most multi-location DrChrono groups can pull days in A/R by site in a few clicks. Some can tell you each provider's visits per day for any week this year.
Many chose DrChrono partly for its open API, and they put that data to work on billing, coding, and provider output. Ask the same group which location answers patient texts fastest, and you'll get five opinions, one from each site manager.
Patient communication is where the numbers stop. Reminder calls, callback notes, and review requests live on desk phones and sticky notes, so nothing lands in a form anyone can compare.
Location-level patient engagement reporting for DrChrono groups closes that gap by measuring the layer that decides whether the schedule fills.
Our position is plain. A group this data-driven should track patient messaging the way it tracks claims: by site, by week, with a named owner. Curogram makes that possible because every text, reminder, and campaign it runs already leaves a time-stamped record.
The cost of skipping this is concrete. A 2% billing variance gets an email thread within days. A 20% no-show rate at one site can run all year, because no report puts that site next to its peers.
We'll use a five-site example throughout, with two locations we'll call Harbor and Midtown. Harbor wants another front desk hire.
Midtown runs the same volume with one fewer person. Whether Harbor needs the hire is a question one weekly report per site can settle, and that same report shows which of Midtown's habits are worth copying.
DrChrono groups tend to be run by people who like numbers. Billing runs on a weekly A/R aging report. Providers see visit counts by office, and some ops teams pull utilization from the API into a BI tool every day.
Then there's the front desk. Confirmation calls happen on a desk phone. A patient's "running 10 minutes late" text lands on a staff member's cell, or it sits in a voicemail box nobody checks until the line goes quiet.
None of that activity writes a row anywhere. DrChrono records the outcome, such as a No Show status on the appointment.
It can't record the three unanswered calls that came before it, or how long the patient waited for a reply. So the step that most shapes whether a slot gets filled has no data behind it.
Take our five-location group. In the monthly ops review, Harbor's site manager asks for another front desk hire. Her case: the phones never stop, and patients complain about slow callbacks.
Midtown handles about the same patient volume with one fewer person on staff. That fact cuts both ways. Harbor could be short-handed, or Harbor's process could be slower.
Nobody in the room can tell which. Harbor's median reply time to a patient text might be twice Midtown's, and that number has never existed in a form anyone could put on a slide.
So the debate turns on who tells the better story. The hire gets approved or denied on feel, in a group that would never sign a new payer contract without a model behind it.
Problems last longest where no report can see them. A billing anomaly of 2% triggers a review within days. A no-show problem at one site can run for a year, because nothing compares that site to the other four.
Run the math for one site with round numbers. These figures are illustrative, so swap in your own visit count and average payment.
|
Illustrative site |
Value |
|
Booked visits per month |
3,000 |
|
Missed visits at a 20% no-show rate |
600 |
|
Missed visits at a 10% group norm |
300 |
|
Extra missed visits |
300 |
|
Lost revenue at $100 per visit |
$30,000 a month |
Even at half these numbers, one site leaks $15,000 a month, or $180,000 a year. That's more than the salary of the front desk hire Harbor keeps asking for.
For a real benchmark, based on our internal data, Atlas Medical Center cut its no-show rate from 14.20% to 4.91% in three months after moving to automated reminders and two-way texting.
Every group has a site that does something better. Maybe Midtown's front desk texts every unconfirmed patient at 2 p.m. the day before. Maybe one office asks every patient for a Google review at checkout, while the others ask when they remember.
Those habits rarely spread past the site that started them. Nobody can point to the site that has them, because nobody can see which site gets the best results.
Without a shared number, "Midtown is great at confirmations" is one manager's opinion against another's.
Some groups try a manual fix. Each site manager logs confirmation calls in a shared sheet, and someone in ops totals it on Fridays.
It rarely survives the first busy month. Counts are self-reported, so the site under the most pressure logs the least. Sites also define terms their own way. At one office, a voicemail counts as "confirmed." At another, only a call-back does.
Reply time is the bigger hole. No one writes down how long a patient text sat before a staff member answered it, because the person who'd log it is the one who was too busy to answer. The sheet ends up tracking effort at the sites that have time to fill it in.
So the best playbook stays in one building. New hires at weaker sites learn the local habits, and the gap between the top and bottom sites holds steady from one year to the next.
Every reminder Curogram sends gets a time stamp. So does every patient reply, every staff answer, and every review link a patient taps. Those records exist because the group's texting runs through the platform, so collecting them costs nothing extra.
That changes what reporting takes. Most groups that want front desk metrics expect a BI project, with an analyst, a data feed, and months of build time.
With Curogram, the numbers come out of the daily work itself. A confirmation rate is confirmed replies divided by reminders sent, per site, per week.
Curogram acts as the group's network scoreboard. It's the per-location analytics medical group leaders already expect for billing, applied to the layer where patients and staff actually talk.
For most groups, the first engagement KPI multi-location practice leaders ask about is confirmation rate, since it predicts next week's no-shows. The scoreboard tracks four more next to it.
|
Metric |
What it measures |
Why ops cares |
|
Confirmation rate |
Share of booked visits confirmed by text |
Early sign of next week's no-shows |
|
Median response time |
Time from a patient text to a staff reply |
Front desk load and patient experience |
|
No-show trend by location |
Week-over-week no-show rate per site |
Lost revenue, traced to one office |
|
Review velocity |
New Google reviews per week |
Local search pull for each office |
|
Campaign conversion |
Recall texts that turn into booked visits |
Revenue from lapsed patients |
Every metric filters by location, service line, and period. If you want to benchmark locations, confirmation rate is the cleanest place to start. Each site sends the same reminders, so the math works the same way everywhere.
Review velocity earns its own column because each office has its own Google Business Profile.
Based on our internal data, 90% of new patient leads see that profile before they visit your website. A site with flat review growth is losing new patients at the search page, before anyone calls.
Engagement numbers carry more weight when they connect to the numbers you already watch. Curogram ties each metric to the appointment in DrChrono. A confirmation lines up with whether that patient arrived, cancelled, or got marked No Show.
That link lets an ops lead test real questions. Did the site with the slowest reply time also post the worst no-show trend last month? Do patients who confirm by text show up more often than patients reached by phone?
It also means a DrChrono communication performance report can sit next to the utilization and revenue views your group already trusts. Both draw on the same appointment records, so nobody has to argue about whose numbers are right.
A ranking only works if every site is measured the same way. Because all five offices send reminders and answer texts through the same system, the rules match by default.
A visit counts as confirmed when the patient replies to the reminder. Reply time runs from the moment a patient's text arrives to the first staff answer. A no-show comes from the DrChrono status on the visit itself, so it can't be logged one way at Harbor and another way at Ridge.
That matters most in the room where the numbers get used. When Harbor's manager sees her 41-minute reply time, she can't argue that Midtown counts differently. Talk moves straight to the cause.
Service line filters handle the other fairness problem. A busy pediatrics office and a quiet specialty clinic shouldn't share one target, so each can be compared with its own kind of site.
Data-driven practice operations usually run on a weekly rhythm: a Monday huddle, an A/R review, and a provider output check. The scoreboard fits that rhythm with weekly views per site.
A setup we see work well:
Ops leaders look at the slide before the A/R review starts. Site managers see their own row next to the group median, which turns the scoreboard into a shared target. That's the empty frame on the reporting wall, filled with the same kind of number the group uses everywhere else.
Back to our five-site group. Once texting runs through Curogram, the first weekly view looks like this.
All numbers here are illustrative, built to show how a real ranking reads.
|
Site |
Confirmation rate |
Median reply time |
No-show rate |
|
Midtown |
82% |
6 min |
7% |
|
Lakeview |
79% |
9 min |
8% |
|
Ridge |
77% |
12 min |
9% |
|
Bayside |
74% |
18 min |
11% |
|
Harbor |
63% |
41 min |
17% |
Harbor's staffing request now has context. Its reply time is almost seven times Midtown's, and its no-show rate is more than double. Ops stops asking whether Harbor needs a hire and starts asking what Harbor does differently.
Bayside deserves a look too. At 74%, it sits just under the group median, and its reply time is creeping up. One more slow week would put it on the same path as Harbor, which is exactly the kind of drift a quarterly review would miss.
Harbor's manager opens the message log for her site. Patient texts pile up between 11 a.m. and 2 p.m., when the same two staff cover check-in, checkout, and the text inbox at once.
Midtown splits that work. One person owns the inbox during peak hours and does nothing else. Midtown also sends a second reminder at 2 p.m. the day before to any patient who hasn't confirmed.
Neither habit costs a dollar. Harbor's manager had heard of the 2 p.m. text before, but she had no way to know it was worth copying until Midtown's row sat next to hers.
Harbor adopts both rules. It names an inbox owner for the 11-to-2 window and turns on the second reminder for unconfirmed visits.
A weekly view makes the result easy to track. Two reports in, the reply time trend line points down.
By week six, the group can judge the change against Harbor's own baseline and against Midtown's numbers. It works in reverse, too: if a strong site starts to slip, it shows up within two weekly cycles.
Harbor's hiring decision gets made last, with data. If Harbor's numbers close most of the gap, the group saves a salary. If they don't, the request comes back with proof.
Per-Location Dashboards give a DrChrono group one scoreboard across every site. Each dashboard tracks confirmation rate, median response time, no-show trend, review velocity, and recall campaign conversion. Group rollups sit on top, and every view filters by location, service line, and period.
The data comes from work Curogram already handles. Appointment reminders, two-way texts, review requests, and recall campaigns all run through the platform, so each one leaves a time-stamped record.
Metrics tie back to DrChrono appointment outcomes. That means a confirmation rate at Harbor connects to Harbor's actual arrivals and No Show statuses, the same records your utilization and revenue reports use.
Access follows your org chart. Site managers see their own location next to the group median. Administrators see every site at once. Conversations behind the numbers stay inside a HIPAA-compliant platform with access controls and audit trails.
A few ways groups put the dashboards to work:
Based on our internal data, Curogram clients hold an average confirmation rate above 75%. Our internal data also shows a 24% drop in inbound calls from automated texting, which gives the front desk room to work the numbers the dashboard shows.
A group that runs on data deserves data on the layer that fills its schedule. Right now, many DrChrono groups have rigor everywhere except patient messaging, and that's the layer where a weak site loses the most money without anyone seeing it.
DrChrono already holds your clinical and financial record. Curogram adds the record of how each site talks to patients: how fast staff reply, how many visits get confirmed, and which offices bring lapsed patients back. Put together, those two records answer staffing and process questions that used to end in a stalemate.
Try a quick test this week. Ask your team for last week's confirmation rate, broken out by location. If the answer takes more than a minute, or arrives as "pretty good at most sites," you've found the blind spot.
Book a demo with Curogram. We'll set up the scoreboard against your real location list and show you the first ranking live, so you can see which site leads and which one needs help before your next ops review.