Peak demand is the stress test of any crisis routing system. When 988 queues lengthen, mobile crisis teams are at capacity, and PSAPs are managing concurrent emergencies, the interface between systems can degrade quickly. Safe systems plan for surge explicitly: defined capacity triggers, temporary routing adjustments, fallback options, and post-surge review. This article builds on the 988–911 crisis routing and interfaces framework and complements the wider crisis response models discussion on operational resilience.
Understanding degradation risk at the interface
Degradation occurs when demand exceeds staffing, technology, or field response capacity. Symptoms include abandoned calls during transfer, mobile crisis no-shows, rushed triage, and default escalation to law enforcement because other options are unavailable. Oversight bodies increasingly require evidence of surge planning, including documented capacity thresholds and measurable diversion protection.
Defining capacity triggers that activate surge protocols
Surge planning begins with quantifiable thresholds: call queue length exceeding X minutes, mobile crisis teams at 90% utilization, PSAP wait times beyond defined limits, or repeated transfer loops within a 30-minute window. When a trigger is met, a defined protocol activates automatically rather than relying on ad hoc leadership decisions.
Operational Example 1: Automatic triage modification during high queue volume
What happens in day-to-day delivery: When 988 queue time exceeds five minutes, the system shifts to a surge triage script that prioritizes immediate lethal risk screening within the first 60 seconds. Lower-acuity callers are offered scheduled callback within a defined window. Supervisors monitor queue dashboards and authorize temporary staffing reallocation.
Why the practice exists (failure mode it addresses): During surge, detailed assessments can delay identification of imminent risk. The modified script ensures high-risk callers are escalated rapidly while protecting staff from overload.
What goes wrong if it is absent: Staff attempt full assessments for every caller, increasing abandonment risk and emotional fatigue. High-risk callers may wait too long. Transfers to 911 occur late and under stress, increasing error rates.
What observable outcome it produces: Improved time-to-escalation for Tier 1 calls during surge periods, reduced abandonment rates, and measurable stabilization of average handling time without loss of safety.
Operational Example 2: Mobile crisis load balancing across jurisdictions
What happens in day-to-day delivery: When one county’s mobile crisis teams reach capacity, a regional agreement allows cross-jurisdiction dispatch if ETA remains within safe parameters. The shared incident identifier travels with the dispatch, and the receiving team logs acceptance and ETA. A supervisor confirms arrival status within a set timeframe.
Why the practice exists (failure mode it addresses): Without load balancing, callers in high-volume regions default to 911 even when nearby teams in adjacent areas have availability.
What goes wrong if it is absent: Geographic inequity increases; some callers receive mobile crisis while others receive police-only response purely due to capacity distribution. Repeat contacts rise in underserved zones.
What observable outcome it produces: Balanced utilization across regions, reduced law enforcement-only dispatch in peak areas, and clearer performance dashboards demonstrating equitable response.
Operational Example 3: Surge fallback pathway when all mobile crisis teams are unavailable
What happens in day-to-day delivery: When mobile crisis availability reaches zero, the protocol activates tele-stabilization plus scheduled follow-up within 24 hours. If risk escalates during the call, the escalation matrix is re-applied and 911 engaged under defined Tier 1 criteria. Supervisors log each fallback activation and review daily.
Why the practice exists (failure mode it addresses): Surge without fallback planning leads to chaotic escalation. Staff may promise in-person response that cannot occur, eroding trust and increasing liability.
What goes wrong if it is absent: Callers are told “no teams available” with no alternative plan. They may disengage or escalate risk. Repeat calls spike within hours or days.
What observable outcome it produces: Reduced repeat crisis contacts during peak periods, measurable documentation of fallback utilization, and improved caller retention in tele-stabilization workflows.
Governance and post-surge review
Surge protocols must include after-action review within 72 hours of peak events. Metrics include average queue time, abandonment rate, percentage of law enforcement-only dispatch during surge, repeat contact within 7 days, and staff overtime utilization. Funders and state agencies expect evidence that surge plans are tested and refined, not just written.
Capacity stress is inevitable. Unsafe degradation is not. When triggers, load balancing, and fallback pathways are defined in advance, the 988–911 interface remains stable even under pressure.