A behavioral health organization can run five programs off one phone number and still be running one inbox. Outpatient, IOP, residential, crisis stabilization, and billing all share the line. Every inbound message lands in the same pile, and someone has to read all of it to sort any of it.
We call that pile the “general mailbox.” It’s why plenty of texting projects stall in IT review. An ungoverned channel keeps no record of who saw a message, when they saw it, or whether anyone acted, so a compliance officer asking about a Friday night text has nothing to look at.
Routing solves the sorting problem before a human touches the thread. Keyword, program, and list-based rules push each conversation into the queue that owns it: crisis threads to crisis staff, copay questions to billing, intake replies to the intake team.
Clinical documentation stays in SmartCare EHR, where your clinicians already work. Curogram sits alongside it and handles traffic.
None of this needs a separate phone number per program, which is the first workaround most organizations try.
Five numbers scatter the audit trail across five systems, and clients who already have your main line saved will keep texting it anyway. Queues do the separation inside a single number, and the record stays in one place.
An after-hours message from an IOP client mentions self-harm. It lands in the general queue behind a billing question and two reschedule requests, and it sits there until the front desk opens at 9 AM. Nobody ignored it. Nothing in the system marked that thread as different from the 40 others waiting.
Incident review starts with one question: who owned that message overnight? A shared inbox has no answer, because ownership was never assigned to anyone. Rapid response and clean handoff are the core of the crisis service, and an unowned queue misses on both counts.
Without routing, triage is a person. Someone opens every thread, decides which program it belongs to, and forwards it, usually as a screenshot pasted into another system because the conversation itself can’t be moved. Shift change ends coverage, and the context leaves with whoever was on.
Count the touches on one intake question: read, classify, screenshot, send, confirm it arrived. Five actions before anyone replies to the client. Most of that volume never needed a human at all.
Based on our internal data, more than 75% of appointment confirmations resolve without staff touch once automation handles them.
Three inputs do most of the work. Keywords catch content, so a defined crisis vocabulary flags a thread and escalates it the second it arrives. List membership catches people: clients enrolled in IOP route to the IOP queue, MAT participants to theirs, court-mandated clients to case management. Message context handles the rest, so a reply to a billing statement stays with billing.
Rules stack in priority order, and crisis sits at the top. A flagged message jumps the queue even when the sender is on the billing list. Everything else follows the program map you drew. Routing assumes two-way HIPAA texting is already in place, and the rules layer on top of it.
Substance use treatment communications carry an extra restriction. SMS bodies hold logistics and secure links only: appointment time, location, a link to sign in. No diagnosis, no clinical detail, and no program name that reveals SUD treatment.
A compliant confirmation reads “Your Thursday 2 PM appointment is confirmed, reply C to confirm.” Program membership lives in SmartCare, not in the message body.
Routing supports that rule by limiting who can open the thread at all. Role-based access keeps Part 2 conversations inside the team that owns them, and every view, assignment, and escalation writes to a log. When an auditor asks who read a specific thread in March, you answer with a record.
Program Queues with Assignment and Escalation gives each team its own view of the conversations it owns. A thread carries an assigned staff member, a status, and a full action log, so a shift change hands off the record instead of a verbal summary. Crisis-flagged threads escalate to on-call staff right away and stay escalated until someone accepts them.
Curogram is EHR-agnostic and connects with EHR systems used across behavioral health, so a SmartCare division and a division on another platform can share one governed communication layer with separate queues.
Confirmations feeding those queues come from appointment reminders, and replies to a broadcast route the same way any other inbound text does, which matters most for mass messaging.
|
Inbound Message |
General Mailbox |
Program Queues |
|---|---|---|
|
Crisis language, 11 PM |
Read at 9 AM by whoever opens the inbox |
Escalated to on-call in seconds, acceptance logged |
|
“What’s my balance?” |
Interrupts a clinical team member |
Lands in billing, clinicians never see it |
|
IOP reschedule request |
Screenshot forwarded to program staff |
Assigned inside the IOP queue with history attached |
Three changes show up inside the first month. Clinical staff stops reading billing questions. Crisis coverage has a name attached to every thread. And nothing drops at shift change, because the queue carries the history rather than the person.
Automation removes the volume underneath all of it. At one multi-site medical group, automated confirmations moved the no-show rate from 14.20% to 4.91%, based on our internal data.
Those confirmations resolve on their own more than 75% of the time, leaving the queue holding conversations that need a person.
Security review asks three questions: who can access a conversation, what gets logged, and how message content is restricted. A shared inbox answers none of them.
Program queues answer each one with role-based access, complete action logs, and templates that keep clinical detail out of the body. Bring that documentation to the review, and the meeting moves on to configuration.
Texting at organizational scale is a routing problem. SmartCare EHR structures your programs, and the communication layer decides which conversations reach which program team, in what order. Once the rules exist, the general mailbox stops being a place where messages wait.
Mapping goes faster than most teams expect. Pull up the org chart, list the programs, name an owner for each queue, and define the crisis vocabulary that triggers escalation. For most organizations that is one whiteboard session.
Schedule a demo and we’ll model routing on your actual programs, including the divisions running a different EHR. You’ll see the queues, the escalation path, and the audit log before anything touches your phone number.