From the Emergency Services edition of October 5, 2026
Norfolk E911 Division puts AWS-powered AI on non-emergency lines, projecting 35–40% call diversion while 911 stays human
Norfolk Police Department Emergency 911 (E911) Division, City of Norfolk, Virginia · Municipal PSAP / emergency communications (police, fire and medical calls) · United States (Virginia)
- Publisher
- City of Norfolk News Flash
- Original publication
- 2026-10-05
- Source retrieved
- 2026-10-06
- Event date
- 2026-10-05
What happened
The City of Norfolk announced on Oct 5, 2026 that its Police Department's E911 Division launched an Amazon Web Services AI-powered service for select non-emergency and informational calls. E911 staff answer over 250,000 police, fire and medical calls and about 150,000 administrative calls a year. The city expects the system to divert roughly 35–40% of non-emergency calls immediately. Callers who say 'I want to speak to an agent' are redirected to a non-emergency line for the next available call taker; all 911 calls stay with trained telecommunicators.
Why it matters
A large municipal PSAP that answers fire and medical as well as police calls is adopting a cloud contact-center AI front door; included here for its 911-center operating model (cross-stream with public safety because the division sits in the police department).
Evidence and measured results
Official agency announcement, not an evaluation (closest schema class used). The 35–40% diversion figure is a forecast; no baseline hold times, accuracy, misrouting or post-launch data are published.
Limitations and uncertainty
Forecast only; launch-day announcement; the 'speak to an agent' path returns callers to the human queue rather than an immediate answer; no detail on emergency detection on non-emergency lines.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Administrative calls wait behind 911 traffic, producing long non-emergency hold times.
- Stakeholders
- E911 manager
- Police and fire leadership
- City IT
- City council
- Residents needing human access
- Discovery questions
- What are current non-emergency hold and abandonment times?
- How will diversion be measured against the forecast?
- How are emergencies on non-emergency lines detected?
- What data does the cloud provider keep?
- Value hypothesis
- An AI front door may answer a meaningful share of routine questions immediately, if diversion and safe escalation are measured.
- Potential engagement
- 90-day measurement plan and call-sample review for an AI non-emergency line.
- Unsupported claims
- 35–40% diversion achieved (forecast only)
- Faster 911 answer times
- Lower staffing need
Pre-sales engineering
Role takeaway
- Fit
- FAQ and routing agent on non-emergency PSAP lines.
- Architecture and integration
- Non-emergency trunk to AWS AI service; spoken opt-out to human non-emergency queue; 911 trunks unchanged.
- Prerequisites
- Intent and FAQ catalog
- Emergency-transfer rule
- Call logging and baselines
- Constraints
- No published accuracy data
- Opt-out returns caller to queue
- Voice-only interaction
- Security
- Define transcript retention, encryption and provider data-use limits in the contract.
- Proof of value
- Measured diversion vs 35–40% forecast
- Emergency transfer accuracy on test calls
- Non-emergency hold time before and after
Delivery
Role takeaway
- Work
- Baseline, launch, log opt-outs and transfers, review samples, publish results.
- Dependencies
- AWS configuration
- Telephony
- City service content owners
- Ownership
- Norfolk Police E911 Division operations.
- Skills and adoption
- Telecommunicators review AI call samples and flag wrong answers or missed emergencies.
- Governance checkpoints
- Pre-launch emergency transfer test
- 30-day sample review
- 90-day public results
- Acceptance criteria
- Every emergency spoken on test calls transferred
- Diversion measured against forecast
- Opt-out honored on all requests
- Risks
- Missed emergency on non-emergency line
- Outdated FAQ answers
- Callers frustrated by return to queue
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Cloud contact-center AI (AWS) sits on the non-emergency trunk, answers FAQs, and hands off to the human non-emergency queue on request; 911 trunks are untouched.
Governance
Who approves, reviews and stays accountable for outcomes?
Launch without published success metrics or review cadence; the agency should define how diverted, abandoned and misdirected emergency calls on the non-emergency line are counted before claiming the forecast.
Security and privacy
What data, permissions and controls need testing?
Announcement does not describe recording, transcript retention, or AWS data-use terms; these need to be set out for a public-safety call center.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Opt-out to a human is offered by voice command; callers who cannot use voice prompts or who speak other languages are not addressed. Framed as freeing telecommunicators for critical incidents, not as staff reduction.
Procurement
What should contracts, pricing and exit terms secure?
Uses a hyperscaler contact-center stack rather than a 911-specialist vendor, so contract terms on data, uptime and configuration support should be checked against PSAP requirements.
Operating model
Which teams own the service once it runs?
AI front door for administrative volume, human queue as fallback, 911 fully human.
Publication history
- 2026-10-05Emergency Services · Issue 305 resources
Stable resource ID: norfolk-e911-aws-ai-nonemergency-lines-20261005