988 and mobile crisis technology: call handling, dispatch, and bed data

Reference article · 5 min read

SAMHSA's national guidelines describe a crisis system in three parts: someone to talk to, someone to respond, and somewhere to go. Each part runs on different software, usually bought at different times by different offices. A contact center platform sits at the 988 center. A dispatch and field documentation system sits with the mobile crisis provider, often a contracted community behavioral health agency. A bed registry sits at the state or regional level. The clinical chart sits in an electronic health record that none of the others can see.

The useful question for a county is rarely which product is best. It is how these systems hand off to one another, what each is permitted to know, and whether the resulting record answers the questions a board of supervisors and a state agency will ask. What follows walks the stack in the order a crisis moves through it.

How 988 contacts arrive and route

The Lifeline is a network of independently operated centers, not a single call center. Calls have historically routed on the area code of the calling number, which sends some contacts to a center far from where the person actually is. Georouting for wireless calls has been deployed to reduce that mismatch, and text and chat route differently again, so a center's assigned coverage area and its real contact mix differ. Confirm current routing behavior with the Lifeline administrator rather than assuming. Three details matter when evaluating center technology:

• Answer rate and rollover. Contacts a local center cannot answer within the network's threshold roll to backup centers. Telephony reporting must separate offered, answered in-state, and rolled-over contacts, because state answer rate is the metric most often cited publicly.
• Multichannel parity. Text and chat need queueing, transcript retention, and supervisory monitoring equal to voice. Agencies often discover the chat platform is a separate product with separate reporting.
• Transfers to specialty subnetworks and to 911. Most 988 to 911 interoperability today is a warm voice transfer, not a data exchange. Ask whether your local arrangement passes any structured information and which system holds the record of the transfer.

Dispatching a mobile crisis team

Mobile crisis dispatch resembles public safety dispatch but is not identical. The team needs the intake summary, a location with on-scene detail such as building access, a callback number, and clear status timestamps: requested, accepted, en route, on scene, cleared, transported. Those timestamps become your response time reporting, so define them before go-live.

Safety flags deserve deliberate policy. A flag drawn from law enforcement history can escalate a response that did not need escalating, and it can follow a person for years. Decide in writing who may create a flag, what evidence supports it, how long it persists, and who reviews it. Plan for connectivity too: teams work in basements and rural areas, so the field application should function offline and sync later.

Somewhere to go: bed and service availability

Bed registries fail for predictable reasons, and buyers can test for each.

• Staffed versus licensed. A facility may be licensed for beds it cannot staff tonight. The registry should show what is actually available.
• Admission criteria. Availability means little without age range, acuity, medical clearance requirements, involuntary status handling, and payer acceptance.
• Update cadence. Manual updates decay. An automated feed from the facility's admission and discharge system is more reliable, and the contract should say how often data must refresh.
• Scope beyond inpatient. Stabilization units, observation chairs, crisis residential, sobering centers, and respite belong in the same view.
• Registry versus referral. A list of open beds is not a placement. Ask whether the system supports requesting, accepting, and confirming placement, and whether that exchange is logged.

Follow-up and the care coordination record

Follow-up contacts, warm handoffs to outpatient care, crisis plans that the next responder can see, and closed-loop referrals all require a record spanning organizations. That record depends on consent, so consent capture, scope, expiration, and revocation should be first-class system features rather than a scanned form in a document folder.

Data sharing limits

Treat this as a design constraint and involve counsel early.

• Crisis line operations are not automatically covered by HIPAA; coverage depends on how the entity is organized and what it bills. Clinical records held by treatment providers generally are.
• Substance use disorder treatment records carry additional federal protections with their own consent and redisclosure rules, amended in recent rulemaking. Confirm current requirements with counsel rather than older guidance.
• Law enforcement access should be defined field by field. An officer supporting a scene may need a location and a safety-relevant fact, not a diagnosis or history.
• State law governs retention and public records treatment of crisis records, and exemptions vary. Confirm before configuring.
• Imminent risk disclosures are real but narrow. Write the policy, log each use, and review it.

Reporting and what to require

States increasingly require response time and outcome reporting, and Medicaid financing for mobile crisis services depends on clean encounter data. Confirm current federal and state requirements directly, since financing options and reporting rules change. When you procure, require in writing:

1. Definitions of every reported metric, including when the response clock starts and what counts as a diversion.
2. Full data export in a documented format, plus a documented API, with export rights that survive termination.
3. Role-based access, per-field permissions, and an immutable audit log you can query yourself.
4. Availability and failover terms fit for a service that runs continuously, with tested degraded-mode procedures.
5. Disclosure of subcontractors, hosting locations, and any automated or AI-assisted features, including whether your data trains models.

HQT works with state and local agencies on integration, data exchange, and systems engineering for public safety and health programs.

Frequently asked questions