From the Emergency Services edition of September 17, 2026
Akron dispatchers tell residents Ava AI handles non-emergency calls; ~39k fully automated
Akron Combined Communications Center · 911 / PSAP emergency communications (combined fire and police dispatch) · Akron, Ohio, United States
- Publisher
- Signal Akron (Akron Documenters)
- Original publication
- 2026-09-09
- Source retrieved
- 2026-09-18
- Event date
- 2026-08-26
What happened
Signal Akron Documenters (published Sept 9, 2026) record an Aug 26 Ward 7 meeting where Akron dispatch said Ava AI is used for non-emergency—not 911—routing since May 2025 (still trial), citing 84,149 AI-handled calls with nearly 39,000 fully automated and 1,200/17,322 (7%) needing callbacks, while residents questioned wait times and whether AI pushed people to dial 911.
Why it matters
Why now: Sept 9 local measured non-emergency AI disclosure after the 2026-09-16 La Vergne AVA deployment edition—adds public-trust scrutiny plus callback-rate figures absent from many launch stories.
Evidence and measured results
Documenters notes: 62 workers; 330,000 calls/year; Ava since May 2025 trial; not on 911; 84,149 AI-handled; ~39,000 fully automated; 17,322 completed by AI agents with 1,200 (7%) callbacks (period unclear); frustration/cursing escalation to agent; residents asked about 911 spillover; presenters acknowledge dislike of AI.
Limitations and uncertainty
Documenters paraphrased meeting notes (not investigative audit); callback metric period unclear; combined center includes policing workloads—relevance for stream is fire/EMS-serving dispatch capacity and non-emergency AI controls.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-18; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Combined PSAPs adopt non-emergency AI under staffing pressure while residents distrust automation and lack published spillover metrics.
- Stakeholders
- Dispatch supervisors
- Fire/EMS leadership
- City council/ward offices
- Residents/311 users
- Discovery questions
- What exact dates cover the 84k/39k/7% figures?
- Is 911 spillover measured?
- What are trial exit criteria?
- How are fire non-emergency calls classified?
- Value hypothesis
- If automation reduces non-emergency load without increasing 911 misuse or unsafe callbacks, trial continuation may be justified—without claiming emergency performance gains.
- Potential engagement
- Public metrics brief plus bounded QA sampling of automated sessions.
- Unsupported claims
- Faster 911 answers proven
- 7% callback as standing SLA
- Resident acceptance
- Safe staff cuts
Pre-sales engineering
Role takeaway
- Fit
- Non-emergency Ava agent for routing/info with human escalation; 911 remains human.
- Architecture and integration
- Non-emergency trunks → Ava → CAD/route or agent; frustration detection to human; separate 311 weekend path.
- Prerequisites
- 911 trunk separation
- Callback workflow
- Logging of AI-handled vs automated-complete
- Public script
- Constraints
- Trial since May 2025
- Metric period ambiguity
- Combined police/fire center politics
- Security
- Protect collected identity/address; limit vendor training; authenticate agent handoff.
- Proof of value
- Dated automation and callback rates
- 911 spillover rate
- Emergency-line occupancy
- Resident complaint themes
Delivery
Role takeaway
- Work
- Maintain human 911, publish Ava scope, sample automated calls, report spillover metrics to council.
- Dependencies
- QA capacity
- CAD/reporting extracts
- 311 weekend staffing policy
- Ownership
- Communications center supervisor owns trial controls; council liaison owns public questions.
- Skills and adoption
- Train reclaim of frustrated callers and explanation of when to use 311 vs non-emergency vs 911.
- Governance checkpoints
- Trial exit review
- Quarterly public metrics
- Spillover investigation if 911 wait complaints rise
- Acceptance criteria
- Dated KPI definitions
- No AI on 911 trunks verified
- Published callback and spillover figures
- Risks
- Meeting-note stats treated as audit
- Resident bypass to 911
- Unclear metric windows
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?
Non-emergency conversational agent (Ava) for routing/info collection with escalation on frustration; separate 311 weekend coverage; independent of Summit County’s system.
Governance
Who approves, reviews and stays accountable for outcomes?
Publish that 911 is human-only, clarify metric time windows, and study whether non-emergency AI increases 911 dialing—as residents asked.
Security and privacy
What data, permissions and controls need testing?
AI collects name, phone, address, and call reason—apply retention and vendor training limits; document escalation when callers refuse AI.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Residents dislike talking to AI; frustration escalation exists but accessibility for disabled/LEP callers is not evaluated in the notes.
Procurement
What should contracts, pricing and exit terms secure?
Trial since May 2025 without published exit criteria in the notes—procurement should demand dated KPIs and spillover monitoring before renewal.
Operating model
Which teams own the service once it runs?
Non-emergency AI plus weekend 311 automation changes how the public reaches humans; emergency model remains human call-taking per officials.
Publication history
- 2026-09-17Emergency Services · Issue 124 resources
Stable resource ID: akron-documenters-ava-nonemergency-ai-2026