911E911HQ.comCompliance field desk

Contact center E911

How E911 works with Genesys and contact centers

Contact centers create a special E911 problem: agents may be remote, numbers may be virtual, and the emergency call is for the agent’s location, not the customer’s emergency.

Agent

Agent safety

E911 is for the employee or agent placing the emergency call from the platform.

Precedence

Address hierarchy

Genesys Cloud documents different address precedence rules for remote address, emergency callback identifier, phone site, IVR, and default site.

Scope

PSTN ownership matters

If the customer brings its own PSTN, emergency routing responsibilities may shift outside the bundled platform design.

The contact-center E911 distinction

A contact center may receive emergencies from the public, but enterprise E911 is about the agent or employee dialing 911. The platform must route help to the caller’s physical location, not the caller ID billing address or the customer’s location.

This is especially important for work-from-home agents, outsourced teams, disaster overflow teams, and cloud phone migrations.

  • Give each remote agent a supported emergency address workflow.
  • Confirm whether the agent needs an individual phone number or emergency callback identifier behavior.
  • Separate customer emergency handling scripts from employee E911 routing.
  • Test callback behavior for agent desktops and softphones.
  • Retain evidence that the delivered location was the agent location.

Genesys Cloud address precedence

Genesys Cloud Voice documentation describes a decision order for United States and Canada emergency addresses: remote-worker address first, then emergency callback identifier assignment, then the site associated with a user phone or standalone phone, then default site behavior for IVR or unassigned numbers.

  • Remote address wins when configured for a remote worker.
  • emergency callback identifier assignments can map numbers to emergency locations.
  • Phone site location matters for assigned phones.
  • Default site fallback should be treated as a risk area.
  • Mobile-app emergency behavior may differ from desktop behavior.

What to ask before go-live

The safest contact-center migration plan treats E911 as a production readiness gate. Do not wait until after cutover to discover which agents can update emergency location.

  • Which regions and PSTN models are supported?
  • How are remote agents prompted and validated?
  • Does the E911 service support corporate notifications?
  • What happens when an address fails validation?
  • How do supervisors audit emergency-address readiness?