6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch

6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch

Exam Focus: The Emergency Response Management (ERM) suite equips public sector agencies to rapidly coordinate emergency aid, crisis intake, automated triage, and field response operations during catastrophic events. Candidates must master citizen intake channels via OmniStudio OmniScripts, vulnerability-based triage scoring using the Business Rules Engine (BRE), field team dispatch mechanics, and the vital architectural boundary separating ERM humanitarian operations from municipal 911 / Computer-Aided Dispatch (CAD) systems.

---

The Emergency Response Management (ERM) Suite: Architecture & Purpose

When municipal, state, or national jurisdictions experience catastrophic crises—such as hurricanes, earthquakes, hazardous chemical spills, or infectious pandemics—conventional administrative workflows break down under massive volume surges. Citizens urgently require emergency shelter, food, drinking water, medical supplies, and rescue assistance, while emergency operations centers (EOCs) face fragmented communication channels.

The Emergency Response Management (ERM) suite provides a purpose-built, cross-cloud public sector architecture built on Salesforce Platform, Public Sector Solutions, Health Cloud, and Service Cloud foundations. ERM unifies the disaster response lifecycle across three core pillars:

1. Constituent Crisis Intake: Omni-channel engagement platforms that capture urgent public assistance requests through self-service web portals, mobile messaging, and emergency call centers without bottlenecking agency infrastructure.
2. Dynamic Triage & Prioritization: Automated decisioning algorithms that evaluate vulnerability criteria (e.g., power-dependent medical equipment, mobility impairment, acute injury, infant care) to prioritize incoming requests according to statutory life-safety protocols.
3. Operational Field Dispatch & Resource Mobilization: Rapid mobilization of first-line social workers, public health nurses, damage assessment teams, and volunteer corps, dispatching resources to geolocated disaster zones.

---

Citizen Emergency Intake Channels & Experience Cloud Crisis Portals

During a declared disaster, public communications infrastructure experiences extreme stress. Emergency management agencies must provide intake mechanisms that are accessible across diverse digital channels, resilient under high concurrency, and usable by distressed citizens on low-bandwidth mobile devices.

┌─────────────────────────────────────────────────────────────────────────────┐
│                          Citizen Intake Channels                            │
├──────────────────────────────┬───────────────────────────────┬──────────────┤
│ Unauthenticated Web Portal   │ Emergency Call Center (311)   │ Mobile & SMS │
│ (Experience Cloud + Omni)    │ (Service Console + OmniScript)│ (Digital     │
│ • Zero login friction        │ • Telephony CTI integration   │   Engagement)│
│ • Multilingual crisis forms  │ • Guided operator intake      │ • Low-data   │
│ • Offline-ready Save state   │ • Rapid Person Account match  │   intake     │
└──────────────┬───────────────┴──────────────┬────────────────┴──────────────┘
               │                              │
               ▼                              ▼
┌─────────────────────────────────────────────────────────────────────────────┐
│                       Ingestion & Identity Resolution                       │
│ • Match or Create Person Account (Gov ID / Mobile / Address Geocoding)      │
│ • Instantiate Emergency Service Request (Case / Crisis Incident Record)     │
└──────────────────────────────────────┬──────────────────────────────────────┘
                                       │
                                       ▼
┌─────────────────────────────────────────────────────────────────────────────┐
│                Business Rules Engine (BRE) Expression Sets                  │
│ • Evaluate Severity Metrics: Medical Need + Vulnerability + Hazard Proximity│
│ • Assign Urgency Tier: Tier 1 (Immediate) -> Tier 4 (Routine Recovery)      │
└─────────────────────────────────────────────────────────────────────────────┘

1. Unauthenticated Experience Cloud Crisis Portals

For citizen self-service, agencies deploy public-facing Experience Cloud sites optimized for high concurrency. Key architectural principles include:

• Guest User Intake via OmniScript: Emergency aid request forms are authored in OmniStudio OmniScripts and surfaced to guest (unauthenticated) constituents. Requiring constituents to create portal usernames and passwords during an active evacuation creates unacceptable friction and leads to abandoned requests.
• Micro-Payload Design: Crisis OmniScripts utilize lightweight UI layouts, minimizing external CSS/JavaScript dependencies to ensure fast loading on degraded cellular networks.
• Multilingual Support: Forms utilize Salesforce Translation Workbench and Custom Labels, dynamically rendering in the constituent's preferred language (e.g., English, Spanish, Vietnamese, Tagalog).

2. Emergency Call Center & 311 Inbound Intake

For constituents who cannot access digital tools, emergency call centers (such as municipal 311 hotlines or crisis assistance lines) handle inbound phone requests.

• Operator-Assisted OmniScripts: Call center operators utilize guided OmniScripts within the Public Sector Service Console, capturing caller details, immediate physical danger indicators, and exact GPS or street coordinates.
• Identity Resolution: Integration Procedures execute deduplication logic against existing Account and Contact records, matching phone numbers, national identification numbers, or addresses to associate requests with existing Person Accounts rather than creating orphaned duplicates.

---

Incident Triage, Severity Scoring & Prioritization Logic

Emergency agencies cannot treat all aid requests on a first-come, first-served basis. In a catastrophic event, requests must be triaged according to objective medical and situational vulnerability.

Business Rules Engine (BRE) Triage Scoring

Public Sector Solutions leverages the Business Rules Engine (BRE) with Expression Sets and Decision Tables to compute real-time crisis urgency scores:

Stratification into Urgency Tiers

The BRE Expression Set calculates a cumulative score that stratifies the case into standard operational tiers:

• Tier 1 (Critical / Immediate Life Threat): Score > 75. Triggers automated emergency protocol: immediate operator alert and automated protocol referral to tactical emergency dispatch.
• Tier 2 (High / Urgent Human Services): Score 50–74. Dispatches rapid health response teams, emergency evacuation vehicles, or mobile power generators within 2 to 4 hours.
• Tier 3 (Moderate / Shelter & Basic Aid): Score 25–49. Routes to shelter allocation and food/water distribution queues for same-day relief.
• Tier 4 (Low / Standard Disaster Recovery): Score < 25. Enrolls constituent in secondary recovery programs, disaster relief grant intake, and property damage inspection pipelines.

---

Mobilizing Field Response & Resource Dispatch

Once an incident or crisis request is triaged, the agency mobilizes operational personnel to the physical disaster zone.

Standard Objects in Field Dispatch

• Visit & Visitor: Standard PSS objects representing on-site inspection and relief missions. A Visit record is created for each dispatched response team, linking the primary constituent (AccountId), the physical premise (LocationId), and the assigned emergency worker (VisitorId).
• AssessmentTask & AssessmentIndicatorDefinition: Objective checklists assigned to field teams (e.g., verifying resident vitals, checking potable water access, assessing structural roof integrity, documenting flood water heights).
• Mobile Field App (Salesforce Field Service / PSS Mobile): Mobile responders access their assigned visits on mobile devices with offline capabilities, logging observations, capturing geo-tagged photographs, and obtaining emergency supply delivery acknowledgments even when disconnected from cellular service.

---

Architectural Boundary: ERM vs. Municipal 911 / CAD Systems

One of the most critical architectural boundaries on the AP-222 examination is the strict distinction between Salesforce Emergency Response Management (ERM) and Municipal 911 / Computer-Aided Dispatch (CAD) systems.

[!IMPORTANT] AP-222 Core Architectural Rule: Salesforce Emergency Response Management is NOT a replacement for municipal 911 Public Safety Answering Points (PSAPs) or Computer-Aided Dispatch (CAD) systems. Designing an architecture where Salesforce directly dispatches active blue-light police, fire, or emergency medical vehicles during active 911 emergencies is a major anti-pattern and a failing exam answer.

The Role of 911 / CAD Systems

Municipal CAD systems (operated by emergency dispatchers at 911 PSAPs) are purpose-built, mission-critical operational systems designed for sub-second response times. They manage:

• Active police, fire suppression, and paramedic unit tracking;
• Radio frequency communication interfaces and telemetry;
• Sub-second unit dispatch to active crimes, structure fires, and cardiac arrests;
• Emergency telecommunications compliance (e.g., E911 / NG911 PSAP standards).

The Role of Salesforce ERM

Salesforce ERM operates at the human services, resource coordination, and community recovery layer. ERM coordinates:

• Non-immediate life-safety assistance (potable water, emergency rations, infant formula);
• Emergency shelter tracking, bed availability, and evacuation relocation;
• Public health monitoring, mobile health clinic dispatch, and contact tracing;
• Long-term casework, mental health counseling, and disaster financial relief grants.

┌─────────────────────────────────────────────────────────────────────────────┐
│                          Public Inbound Request                             │
└──────────────────────────────────────┬──────────────────────────────────────┘
                                       │
                  Is there an immediate, active life threat?
                                      / \
                                     /   \
                             YES    /     \    NO
                                   /       \
                                  ▼         ▼
┌───────────────────────────────────────┐ ┌───────────────────────────────────┐
│     Municipal 911 / CAD System        │ │     Salesforce ERM Architecture   │
│ • Sub-second blue-light response      │ │ • Human services & relief aid     │
│ • Police, Fire, EMS tactical dispatch │ │ • Shelter bed & supply allocation │
│ • Radio telemetry & unit routing      │ │ • Vulnerability triage & Visits   │
│ • PSAP NG911 statutory compliance     │ │ • Long-term recovery case grants  │
└───────────────────────────────────────┘ └───────────────────────────────────┘

Integration Patterns Between CAD and ERM

In advanced smart city architectures, CAD and Salesforce ERM integrate via bi-directional event buses or REST APIs:

• CAD-to-ERM Referrals: When a 911 caller's immediate medical danger is stabilized by paramedics, but their home is destroyed, CAD pushes an event to Salesforce ERM to open an emergency shelter and housing assistance case.
• ERM-to-CAD Escalations: If a citizen submitting a routine online food aid form in OmniScript suddenly indicates active chest pain or immediate life danger, the OmniScript immediately presents standard emergency guidance ("Stop and call 911 immediately") and triggers an automated alert.

---

Municipal 911 / CAD vs. Salesforce ERM Architecture

---

💡 Real-World AP-222 Exam Scenarios & Case Analysis

Scenario 1: Hurricane Surge Intake & Scalable OmniScript Deployment

During a major category 4 hurricane, a regional emergency management agency experiences an 800% surge in requests for emergency food, water, and temporary shelter. Internal call center lines are overwhelmed, and citizens are reporting long wait times on the phone. The agency's leadership requires an immediate, high-volume digital intake solution.

How should the enterprise architect configure the citizen intake channel?

• Deploy an unauthenticated OmniStudio OmniScript hosted on a public-facing Experience Cloud site configured for high-volume guest traffic.
• Design the OmniScript with minimal step complexity and lightweight UI components, allowing constituents to submit shelter and aid requests from mobile devices without registering for an account.
• Map the submitted payload via an Integration Procedure that matches or instantiates standard PersonAccount records and generates an emergency aid Case with geolocated premises data.

Scenario 2: Life Safety Escalation & CAD Boundary Adherence

A county emergency operations center uses Salesforce Emergency Response Management (ERM) alongside a legacy municipal 911 Computer-Aided Dispatch (CAD) system. An emergency hotline operator using the Salesforce Service Console receives a phone call reporting an active residential structural fire with residents trapped in an attic.

What architectural principle governs how this request must be handled?

• Immediate life-safety emergencies requiring sub-second tactical blue-light response (police, fire, EMS) belong strictly within the municipal 911/CAD system, not within Salesforce ERM.
• The operator must immediately execute standard emergency transfer protocols to route the caller directly to the 911 PSAP dispatcher.
• Salesforce ERM must not be architected as the primary dispatch mechanism for active structure fires or armed emergencies; its role begins after immediate life safety is secured, coordinating emergency housing and Red Cross disaster relief for the displaced family.

Scenario 3: Medically Fragile Constituent Triage via BRE Expression Sets

An emergency agency receives 15,000 emergency power and heating assistance requests following an ice storm that knocked out the regional electrical grid. Agency staff must prioritize mobile generator deliveries to residents whose lives depend on electric-powered medical equipment.

Which declarative engine within Public Sector Solutions should be configured to calculate this priority score?

• Configure the Business Rules Engine (BRE) using Expression Sets and Decision Tables.
• The Expression Set evaluates input parameters (e.g., oxygen concentrator dependency, ventilator use, resident age, indoor temperature) and outputs a numeric vulnerability score and corresponding Urgency Tier.
• High-priority outputs automatically route cases to the Critical Medical Dispatch queue, where dispatchers schedule mobile generator delivery visits immediately.