Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Emergency Services edition of October 4, 2026

Independent reportingEmergingNew this fortnight

WRJN: Ozaukee County consolidated center deploys Aurelian Ava on non-emergency line as 911 volume rises 17%

Ozaukee County Sheriff's Office Communications Center (Wisconsin) / WRJN · County consolidated PSAP / emergency communications · United States (Wisconsin)

Publisher
WRJN (Civic Media)
Original publication
2026-09-30
Source retrieved
2026-10-05
Event date
2026-09-30
Read original source

What happened

WRJN reports (Sept 30, 2026) that Ozaukee County's consolidated communications center, serving seven police departments, seven fire departments and the Sheriff's Office, put Aurelian's Ava on its non-emergency line. The center processed 113,538 non-emergency and 17,612 emergency 911 calls in 2025, and emergency volume is up 17% this year. Ava routes callers by stated reason, transfers detected emergencies to 911, and supports Spanish; the sheriff said there will be no job cuts.

Why it matters

Adds another Wisconsin consolidated PSAP, serving fire and EMS as well as police, to the regional Ava adoption cluster, with a clear volume rationale.

Evidence and measured results

Short local news item restating agency claims; no performance data, error rates, or post-launch metrics. 'Rigorous training' is an unspecified vendor/agency claim.

Limitations and uncertainty

Launch announcement only; no outcome data; volumes are 2025 figures and the 17% increase is not broken out by source.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Consolidated center with high non-emergency volume and rising 911 calls needs more peak capacity without layoffs.
Stakeholders
  • Sheriff
  • Communications center manager
  • Member police and fire departments
  • County board
Discovery questions
  • What is your non-emergency to 911 ratio?
  • Which destinations do callers ask for most?
  • How will you test Spanish emergency detection?
  • What results will you publish?
Value hypothesis
Natural-language routing may cut dispatcher time on routine calls; benefit is unproven until measured.
Potential engagement
Pre-launch readiness review: route map, bilingual test plan, and KPI baseline for a consolidated PSAP.
Unsupported claims
  • Measured capacity gains
  • Accuracy of emergency detection
  • Equal Spanish performance

Pre-sales engineering

Role takeaway
Fit
Non-emergency routing agent for a multi-agency consolidated center.
Architecture and integration
Non-emergency line to Ava; routes to divisions; emergency transfer to 911 queue.
Prerequisites
  • Destination directory for 15 agencies
  • Emergency transfer path
  • Bilingual test calls
Constraints
  • No published accuracy data
  • Records-related requests need access limits
Security
Define what jail/bond data the agent can access and how transcripts are retained.
Proof of value
  • Emergency-transfer accuracy in English and Spanish
  • Misroute rate
  • Dispatcher radio/911 time before and after

Delivery

Role takeaway
Work
Build route map, test bilingual emergency transfer, publish caller guidance, and set review cadence.
Dependencies
  • Aurelian configuration
  • Member agency directories
  • Telephony
Ownership
Sheriff's Office communications center operations.
Skills and adoption
Dispatchers learn to review AI routing and report misroutes.
Governance checkpoints
  • Pre-launch test sign-off
  • 30-day review
  • Member-agency feedback
Acceptance criteria
  • Bilingual emergency test set passes before expansion
  • Misroutes logged and reviewed weekly
  • Baseline dispatcher time captured
Risks
  • Spanish dialect gaps
  • Misrouting across 15 agencies
  • Unmeasured benefit claims

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?

Natural-language routing replaces a phone tree; emergency detection triggers transfer to 911; bilingual (Spanish) handling.

Governance

Who approves, reviews and stays accountable for outcomes?

Launch announced without published success measures or review schedule; agencies should set them before claiming capacity gains.

Security and privacy

What data, permissions and controls need testing?

Not addressed; bond and jail inquiries mean the agent touches records-related requests, so data access scope should be defined.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Spanish proficiency claimed; no-job-cuts commitment framed as added peak capacity.

Procurement

What should contracts, pricing and exit terms secure?

Joins Waukesha, Dane and other Wisconsin users of Aurelian; regional buyers can compare terms and results across counties.

Operating model

Which teams own the service once it runs?

AI handles non-urgent routing so dispatchers focus on radio traffic and 911; human dispatch remains the emergency path.

Publication history

  1. 2026-10-04Emergency Services · Issue 285 resources
Read preserved resource versions (JSON)

Stable resource ID: wrjn-ozaukee-county-ava-nonemergency-20260930