Study guide
6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch
Salesforce Accredited Agentforce 360 for Public Sector Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Overview, Architecture & Constituent Data Modeling
1.1 AP-222 Exam Blueprint, Passing Standards & Credential Overview 1.2 Public Sector Solutions Layered Architecture & Industry Common Layer 1.3 Person Accounts & Constituent Data Modeling
2 Chapter 2: Licenses, Permits, and Inspections (LPI) — Intake & Issuance
2.1 Regulatory Authorization Types & Application Intake 2.2 Business License & Permit Issuance, Conditions & Status Tracking 2.3 Application Reviews, Multi-Department Approvals & Renewals
3 Chapter 3: Inspections, Code Enforcement, and Compliance
3.1 Inspection Types, Action Plan Templates & Onsite Visit Execution 3.2 Regulatory Codes, Assessment Indicators & In-Field Checklists 3.3 Regulatory Code Violations, Enforcement Actions & Remediation Workflows
4 Chapter 4: Grants Management & Grantmaking Lifecycle
4.1 Funding Programs, Funding Opportunities (NOFOs) & Public Discovery 4.2 Grant Application Intake, Review Workspaces & Multi-Stage Scoring 4.3 Funding Awards, Disbursement Schedules & Post-Award Reporting
5 Chapter 5: Benefits Management & Assistance Programs
5.1 Benefit Programs, Benefit Schedules & Beneficiary Data Architecture 5.2 Discovery Framework Assessments & Question Versioning 5.3 Rules-Based Eligibility Determination & Recertification Lifecycle
6 Chapter 6: Employee Experience & Emergency Response Management
6.1 Public Sector Employee Experience & Workforce Operations 6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch 6.3 Rapid Resource Allocation, Volunteer Coordination & Contact Tracing
7 Chapter 7: Document Processing, Intelligent Automation & Reporting
7.1 Document Checklist Items, Content Management & Upload Portals 7.2 Intelligent Document Automation (IDA), the Document Workspace & the IDA vs. IDA/IFR Decision 7.3 Intelligent Document Reader (OCR with Amazon Textract) & eSignature Integration 7.4 OmniStudio Document Generation & Dynamic PDF Production 7.5 Public Sector Operational Reporting, Compliance Dashboards & CRM Analytics
8 Chapter 8: OmniStudio for Public Sector — Guided Intake & 360 Views
8.1 OmniScript Architecture, Step Design & Conditional Branching 8.2 Data Prefill Patterns, Context Passing & Save-for-Later 8.3 FlexCard Architecture, Constituent 360 Layouts & Action Frameworks
9 Chapter 9: OmniStudio Integration & Server-Side Processing
9.1 Data Mappers (DataRaptors) — Turbo Extract, Extract, Transform & Load 9.2 Integration Procedures — Action Chaining, Batching & Error Handling 9.3 External API Integrations, HTTP Actions & Named Credentials
10 Chapter 10: Business Rules Engine (BRE) & Dynamic Fee Calculation
10.1 Expression Sets — Calculation Steps, Formulas & Versioning 10.2 Decision Tables & Decision Matrices for Policy Decisioning 10.3 Dynamic Fee Schedules, Calculation Procedures & Regulatory Pricing
11 Chapter 11: Experience Cloud Citizen Portals & Service Console
11.1 Public Sector Experience Cloud Site Templates & Citizen Self-Service 11.2 Guest vs. Authenticated User Journeys & Identity Verification 11.3 Multilingual Localization, Custom Labels & Translation Workbench 11.4 Public Sector Service Console, Workspace Tabs & Omni-Channel Routing
12 Chapter 12: Security, Compliance, Government Cloud & Best Practices
12.1 Data Security, Org-Wide Defaults (OWD) & Sharing Architecture 12.2 Government Cloud Tiers, FedRAMP & DoD Compliance 12.3 Salesforce Shield, Field Audit Trail & Platform Encryption 12.4 Declarative-First Strategy, Process Library & Deployment with IDX Workbench
13 Chapter 13: Agentforce & AI Innovation for Public Sector
13.1 Agentforce Architecture, Agent Builder & Public Sector Agents 13.2 Topic Definitions, Instructions, Actions & CRM/Data Cloud Grounding 13.3 Einstein Trust Layer, Guardrails & Responsible AI Governance
14 Chapter 14: Discovery, Requirements & Solution Design
14.1 Documenting Business Needs, Agency Value & Vision for Desired Outcomes 14.2 Discovery & Design Approaches and Solution Documentation 14.3 Mapping Business Processes, Personas & Requirements
15 Chapter 15: Org Setup, Data Management & Integration Governance
15.1 Setting Up an Org for Agentforce Public Sector 15.2 Data Management Strategy, Data Quality & Integration Governance
6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch
Key Takeaways Explain This Topic AI
The Emergency Response Management (ERM) suite unifies crisis intake, clinical and non-clinical triage, emergency aid allocation, and field response across natural disasters, public health emergencies, and civil crises.
Citizen crisis intake must support omni-channel pathways—including unauthenticated public-facing OmniScripts on Experience Cloud, contact center telephony, and SMS—optimized for high concurrency and resilient performance during surge events.
Incident triage leverages the Business Rules Engine (BRE) and Expression Sets to compute dynamic severity scores, prioritizing vulnerable populations, life-safety requirements, and time-critical medical dependencies.
ERM coordinates human services, social relief, and rapid resource allocation; it is explicitly designed to complement, rather than replace, municipal 911 Public Safety Answering Points (PSAPs) and Computer-Aided Dispatch (CAD) systems.
Field response dispatch integrates with standard Visit, Location, and field coordination records, assigning specialized personnel and mobile relief units to verified disaster zones based on proximity, skills, and situational severity.
Last updated: September 2026
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:
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.
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.
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:
Assessment Factor Evaluation Criteria Vulnerability Weight
Life-Sustaining Medical Need Patient depends on electrical power for oxygen, dialysis, or life-support +40 Points
- Mobility & Evacuation Capability Non-ambulatory, bedridden, or lacking private transportation +25 Points
- Household Vulnerability Presence of infants under 1 year or seniors over 75 years living alone +15 Points
- Immediate Environmental Threat Active structural collapse, rising water over 3 feet, or gas leak +35 Points
- Shelter & Basic Necessities Displaced with safe temporary shelter, requiring food/water only +10 Points
- 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
Architectural Dimension Municipal 911 / CAD Systems Salesforce Emergency Response Management (ERM)
Primary Mission Sub-second tactical dispatch of first responders for active life threats Strategic coordination of human services, humanitarian aid, and recovery
Responding Personas Armed law enforcement, municipal firefighters, emergency paramedics (EMS) Public health workers, social caseworkers, building inspectors, volunteers
Response Latency Target Seconds (0 to 180 seconds to unit dispatch) Hours to Days (2 to 72 hours for humanitarian relief, weeks for grants)
Core Software Engine Mission-critical CAD consoles with specialized radio/telephony hardware Cloud-based Public Sector Solutions, OmniStudio, and Service Console
Key Relational Data Active apparatus status, GPS unit telemetry, radio incident logs Person Accounts, Emergency Cases, Shelters ( Location ), Visit records
Post-Incident Role Concludes when scene is cleared and units return to service Initiates long-term recovery: shelter transitions, food aid, and disaster grants
- 💡 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.