service-e911-configure
Managing E911
When to Use This Skill
Set up and manage Service Cloud Voice (Native CCaaS / Thunderbird) Emergency Calling (E911). Two routing providers are supported: RedSky and External Vendor (a BYOC telephony trunk). get-emergency-config reports the master switch, the active route, and each provider's status. save-emergency-provider configures a provider: REDSKY provisions a RedSky organization and admin user and requires a Voice number lease license, EXTERNAL_VENDOR takes a trunk chosen from get-telephony-providers. Configuring a provider does not turn the service on or change the active route, except that the first provider configured becomes active. set-route-via switches the active route, and the target must be fully configured. update-e911-status is the master switch: enable=true needs a fully configured active provider, enable=false suspends Emergency Calling and keeps provider settings. enable-legacy-red-sky is a legacy one-shot RedSky provision and enable. If RedSky is configured but its admin user was not created, run create-admin-profile to retry. get-exported-users builds a RedSky Device Users CSV from the org's active Contact Center (Native CCaaS) users. All operations require the Contact Center Admin permission for Service Cloud Voice.
Workflow
Read state with get-emergency-config. To set up, run save-emergency-provider (EXTERNAL_VENDOR needs a telephonyProviderId from get-telephony-providers; REDSKY needs the Voice number lease license), optionally set-route-via to pick the active route, then update-e911-status enable=true. enable=false only suspends. If redSkyConfigured but redSkyAdminCreated=false, retry create-admin-profile. enable-legacy-red-sky is the legacy one-shot RedSky enable. Email/name for RedSky come from UserContext server-side. Before running update-e911-status with enable=false, set-route-via, save-emergency-provider with REDSKY, or enable-legacy-red-sky, tell the user what will change and get an explicit yes. Each can change where emergency calls go, or whether they go at all, and REDSKY and enable-legacy-red-sky create an external RedSky organization. Always pass enable explicitly to update-e911-status; omitting it suspends the service.
Critical Constraints
Preconditions:
- The org must have the SalesforceVoice license (Native Voice / Thunderbird). (check:
Service Cloud Voice access) - The calling user must have the Contact Center Admin permission for Service Cloud Voice. This permission guards every E911 operation. (check:
Contact Center Admin role) - Configuring RedSky through save-emergency-provider requires an active Salesforce Voice number lease license (redSkyEligible=true in get-emergency-config). (check:
Voice number lease license) - An External Vendor trunk must be fully provisioned (it has an external trunk identifier and a valid two-letter country) before it can be saved. (check:
Telephony trunk provisioned) - update-e911-status enable=true and set-route-via fail unless the target provider is fully configured. Turning Emergency Calling off suspends it and keeps provider settings, so it can be turned on again. (check:
Provider configured)