Five offices, five phone numbers, five different habits. Ask any group with more than two sites where a patient message goes after 5pm and you get five answers.
That fragmentation is what separates a group purchase from a single-clinic one. A solo practice buys texting to cut phone volume. A physician group buys it to make five sites behave the same way, and to see what all five are doing.
Most buying guides ignore that difference. They rank features that any platform will demo well, then leave you to discover at rollout that reporting rolls everything into one number, or that your smallest site cannot be staffed after lunch.
What follows is the group-scale version. First, the compliance floor you have to clear. Then the integration questions that shape daily work, the routing and reporting that only matter above one site, and the pricing models that turn the same practice into very different bills.
Messages encrypted in transit and at rest. A unique login per staff member, with role-based permissions. An audit log that records who sent what and when. A signed business associate agreement with the vendor.
All four are table stakes. HHS sets out what a vendor agreement has to cover in its sample business associate agreement provisions. That sample is model language from 2013, not a safe harbour, so your counsel still reads the real one.
A vendor that hesitates to sign a BAA has answered the question. So has one that says it takes security seriously without naming a standard.
Ask for the SOC 2 Type II report rather than the badge. Type II tests whether controls held up over a period, which is the version that means something. Curogram holds SOC 2 Type II alongside HIPAA compliance, with full message history kept for audit.
TCPA governs consent and opt-outs, separately from HIPAA. The FCC's TRACED Act report and order, adopted in December 2020, requires an opt-out path on exempted calls.
Read that order carefully before quoting it at a vendor. Its healthcare caps of one per day and three per week apply to prerecorded voice calls to residential lines, not to text messages. What carries over to texting is the principle: a patient who replies STOP has to drop off the list without anyone tracking it by hand.
Some platforms only pull from the EMR. A patient confirms by text and still shows unconfirmed in the schedule, so someone opens the chart and fixes it.
Across a group, that cost multiplies by site. Forty fixes a day at three minutes each is ten hours a week per office. Treat that as illustrative and run your own count at the busiest site.
Vendors answer the integration question with a yes. Ask instead which tier your own system falls into. Some EMRs connect through APIs and sync in real time. Others go through HL7 or database-level methods that behave differently.
Groups running different systems at different sites feel this hardest. Our EMR and EHR integration page lists what connects, and any vendor should tell you the tier for each of your systems in writing.
Ask for a live reschedule, end-to-end, into a test schedule. Patient replies, staff sees it, the appointment moves in the EMR while you watch.
A vendor whose sync writes back will do this in about 90 seconds. One who offers a slide, a recorded clip, or a roadmap date has told you the answer without saying it.
A message has to reach the right office on the first hop. Routing by the number texted, by appointment location, or by the patient record avoids the manual redirect that eats the morning.
Each site keeps its own local number and caller ID, and the routing happens underneath. Patients see the office they know. Staff see one queue with clear ownership.
A group-wide average is the number that hides the problem. One site running a 40% confirmation rate and another at 90% average out to something that looks acceptable on a board slide.
Ask to see a per-location report during the demo, with confirmation rate and response time broken out by site. If the vendor can only show a roll-up, you will be managing your network by anecdote.
The question every group asks first: do our offices lose their own numbers? They should not have to. Each location keeps its local number and caller ID, and patients text the line they already have saved.
Ask how the vendor handles this before you sign. Some text-enable your existing lines. Others provision new numbers per site, which means telling every patient panel that the clinic's number changed. Ask which, and ask whether porting is included or billed.
Vendors demo the happy path with one user at one desk. Ask what happens at lunch, during a call-out, or at a satellite with a single front-office staffer.
Three features answer it. Time-boxed access for a float, the ability to hand an open thread to someone else, and one switch that cuts a leaver's access at every site. Mass messaging covers the other direction, when a provider calls out and one message has to reach every affected patient.
Two groups of the same size can get quotes that differ by a wide margin, because the models count different things. The sticker rate matters less than the unit it applies to.
|
Pricing model |
Cheaper when |
The detail that changes the bill |
|---|---|---|
|
Per provider |
Few clinicians across many sites |
Whether NPs and PAs count as providers |
|
Per location |
Many clinicians per site |
Whether a part-time satellite counts as a full site |
|
Per message or bundled volume |
Low, steady message volume |
Whether a long text counts as one message or several |
|
Flat platform fee |
Volume swings month to month |
What the fee excludes: setup, training, added users |
Do nurse practitioners and physician assistants count as providers? At a group with many mid-levels, that one definition can move the monthly bill a long way.
What counts as one message? A text over 160 characters can be billed as several segments, and reminders carrying a name, a time and a link often cross that line. Then ask what setup and live training cost, and whether either is optional.
Write the answers down while the vendor is talking. Claims move between a demo and a statement of work, and a written answer is what you hold them to later.
Rank your own requirements first. Compliance and the BAA sit above everything. After that, weight integration depth, per-site routing and reporting against how your group actually runs.
Pick one workflow, one site, one number. Confirmations at your busiest office is the usual choice, because the result is clear inside a single reminder cycle.
Name the threshold before you start. A pilot without a number to beat becomes a demo that lasted a month, and 30 days at one site costs far less than a two-year contract across all of them.
Assign one internal owner who coordinates with the vendor and flags slippage. Train every location the same way, and give the first site's quick learners a role in training the next.
Build in buffer. EMR connections break, field mappings need correcting, and numbers sometimes need porting, so add two to four weeks beyond the vendor's estimate.
Adoption will not land evenly. One office takes to it in a week, another is still answering the phone for things a text closed a month ago.
Write the procedure down once and train every site against the same version. Then check the per-location report monthly for the first quarter. A site that drifts shows up there long before anyone complains, which is the whole reason to insist on per-site reporting during the demo.
Two-Way HIPAA-Compliant Texting runs on each site's own office number and works alongside the EMR that site already uses. Patients reply from a standard text thread with no app and no account.
At group scale that means one shared workspace. Routing rules per site, role-based access, and reports broken out by location. Automated appointment reminders go out by visit type, location and language. Online patient forms and text-to-pay run without staff involvement.
Curogram connects with 150+ EMR and practice management systems, at depths that vary by system. Confirmation rates across our client base run above 75%, and Atlas Medical Center's no-show rate fell from 14.20% to 4.91% in three months, based on our internal data. Staff typically learn the system in about 10 minutes.
Compliance decides whether you can buy at all. Integration depth decides what daily work looks like. Everything specific to a group sits in the third layer: routing per site, reporting per site, and a pricing unit that matches how your clinicians are distributed.
Groups that get this right stop treating each office as its own island. One workspace, one set of rules, and every site reachable the same way.
Book a demo and bring your site list. We'll map routing and reporting to how your group is actually organised, and name the integration tier for each EMR you run.