A patient calls to ask whether her Tuesday appointment is still scheduled. Nine words. The interaction takes two minutes, once you include hold time, the greeting, identity checks, the chart, and a note afterward.
An hour later she submits the identical question through the portal, because she wasn't certain the call registered.
Now one question occupies two separate queues.
That is the shape of the problem across athenahealth networks. You gave patients two front doors, and both open into a line somebody has to work by hand.
The phone rings. The case bucket fills. Neither line clears itself.
Here is what makes it frustrating.
The questions are rarely complicated — confirmations, reschedules, "which office am I going to?", "did my refill go through?" Ten seconds of information wrapped inside two minutes of administrative process.
Your staff understand this better than anyone. They feel it every afternoon, working through a backlog of messages that could have been resolved before lunch.
The cost does not stay at the front desk. Patients who cannot get a quick answer are likelier to skip appointments, and agents who spend the day routing instead of helping start reading job postings. A network running modern software ends up feeling unreachable.
Deflecting call center volume across athenahealth locations with texting is how practices interrupt that cycle. Not by adding headcount. By relocating routine questions out of both queues and into text threads that resolve in seconds.
This article covers where the volume originates, why the phone and the portal cannot solve it independently, and what changes once quick questions get their own lane.
You will also see the arithmetic. It shows how many hours each week a ten-office network spends answering questions that never required a phone call, and what that time is worth once you reclaim it.
Your network gave patients two ways in, and both were designed to help. Both now work the same way — questions arrive, and somebody has to pull each one back out by hand.
That is the underlying issue. Neither queue scales with technology. Both scale with headcount.
Watch how it plays out. An agent answers, greets the patient, verifies her identity, opens athenaOne, resolves a ten-second question, writes a note, then reaches for the next caller on hold.
Meanwhile the case bucket she will work after lunch grows by nine more versions of the same question, typed rather than spoken.
She is not answering patients. She is routing them.
| Where the question lands | What staff actually do | Time to close | What the patient feels |
|---|---|---|---|
| Phone queue | Greet, verify, open the chart, answer, document | 2 to 4 minutes | Waiting on hold for a nine-word answer |
| Portal case bucket | Open the case, check the chart, reply, close the case | Often a day or more in backlog | Silence, then a callback she no longer needs |
| Text thread | Read, tap a saved reply, send | Seconds, between other tasks | Answered before she puts the phone down |
The portal case bucket overload staff carry into every afternoon is the quieter half of this. Phone queues at least sound urgent, while cases simply age out of view until the patient gives up and calls — which returns the identical question to the first line.
Then there is the metric every network monitors. Your athenahealth call center average handle time remains stubbornly high because every call carries identical overhead, whether the answer requires ten seconds or ten minutes. Averages are indifferent to how simple the question was.
Turnover follows the same curve. Staff burnout tracks inbox volume more closely than patient volume. Nobody quits because they saw too many patients.
They quit because they spent eight hours working as a human switchboard.
Curogram works as what we call "The Network Switchboard." It gives quick questions a third lane, one that resolves them in seconds rather than holding them for minutes or parking them in a backlog for days.
Curogram's 2-way texting uses department routing and templated replies. Billing questions go to billing. Scheduling requests land in your centralized scheduling team queue instead of bouncing between offices.
Your twenty most common questions each get a one-tap answer. Routine question deflection by text is not a script staff have to memorize — it is a saved reply they send while the patient is still typing.
Every thread ties back to the record in athenaOne.
No side documentation. No hopping between systems mid-sentence. No new case opened for a nine-word exchange.
That matters more than it sounds. Most of the expense of a routine question is not the answer itself. It is the lookup, the documentation, and the context switching that surrounds it.
Threads handled, average response time, and estimated calls and cases avoided all roll up by location. You can identify which office deflects effectively and which one still forwards everything to the phones.
Those are levers. The phone system never gave you one, and the case queue never did either.
Appointment confirmation is the biggest single call driver in most networks, and it is also the easiest to move.
Curogram client data from clinical settings shows practices confirming more than 75% of appointments by text, with SMS open rates around 98% and call volume dropping by roughly half.
Here is what that looks like in hours.
The figures below are an illustrative example, not a study result — swap in your own call logs and the shape holds.
Fifty hours is more than a full-time position, recovered without hiring anyone. For your team, that time goes back into prior authorizations, referrals, and the calls that genuinely need a voice.
The shift staff notice most is in the rhythm of the day. They stop working a pileup and start working a queue — asynchronous, prioritized, and visible to supervisors at every location instead of buried in one office's phone system.
Hold times drop because fewer people are calling. Case buckets shrink because fewer people are typing the same thing twice. And when you reduce inbound calls network-wide, the front desk stops triaging and starts finishing work.
That is the difference between a busy day and a broken one.
Most of what reaches your phones and your portal is routine. Routine belongs on text.
That is the entire argument, and you can evaluate it without purchasing anything. Pull one week of call records and portal cases from a single location. Sort by reason. Count how many were nine-word questions with ten-second answers.
Whatever that number is, it is your deflection opportunity, already quantified. Most practices are surprised by the size of it, and more surprised to realize they have been staffing around it for years.
It also clarifies what each system is for, and where the boundary between them sits. athenaOne is built for your schedule and your record. Curogram is built for your patients' quick answers. Keep the phones and the portal open for the conversations that deserve them — the worried caller, the complex billing dispute, the clinical question that needs a nurse.
The goal was never to remove the human. It was to stop spending human attention on "yes, Tuesday at 2:15 is still good."
Once routine volume moves to text, three things follow. Handle times come down because the calls that remain are genuinely complicated calls. Cases get answered the same day because the bucket is no longer padded with appointment confirmations.
And your staff end shifts having actually helped patients rather than shuttling them between queues.
That last one is what keeps good front-office people from leaving.
If you want the numbers for your own network before you commit to anything, that is a reasonable place to start. Schedule a Demo and we will walk through your call and case mix, model your likely deflection rate, and show the staffing impact location by location.