From the Emergency Services edition of October 6, 2026
TMJ4: Ozaukee County residents split on Aurelian AVA non-emergency assistant as 911 calls rise 17%
Ozaukee County Sheriff's Office consolidated communications center (Wisconsin) / Aurelian · County consolidated dispatch / non-emergency call handling · United States (Wisconsin)
- Publisher
- TMJ4 (WTMJ-TV Milwaukee)
- Original publication
- 2026-10-06
- Source retrieved
- 2026-10-07
- Event date
- 2026-10-06
What happened
TMJ4 reported on Oct 6, 2026 that Ozaukee County's AI assistant AVA, provided by Aurelian, routes non-emergency callers to the right department or to 911, with the sheriff's office saying emergency calls rose 17% in a year and that 911 staffing is unaffected. Residents were mixed: some social media commenters worried it could slow connections to a person, while others would try it. One resident said even non-emergency calls can be urgent. In a test call, AVA identified itself as an automated AI assistant and said connection time depends on call volume and need.
Why it matters
Adds the caller's side to a rollout already in the archive: residents question whether AI intake delays human help, the main acceptance risk for dispatch centers adopting the same product across southeastern Wisconsin.
Evidence and measured results
Local reporting with two named residents, unquantified social media sentiment, and a reporter's test call; no performance data. The archive's earlier Ozaukee item (WRJN) covered the launch itself; this source is new and adds public reaction.
Limitations and uncertainty
Two resident interviews and social media comments are not representative; no measured wait times or transfer data; the 17% rise is a sheriff's office figure.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Rising 911 volume pushes counties to automate non-emergency answering while residents worry about losing quick access to a person.
- Stakeholders
- Sheriff
- Communications center manager
- County board
- Residents
- Discovery questions
- How long does it take to reach a person after asking?
- How are urgent non-911 calls handled?
- What feedback have residents given?
- Value hypothesis
- AI intake may free dispatchers if residents can still reach a person quickly, which has to be measured.
- Potential engagement
- Caller-experience and time-to-human measurement across counties using the same assistant.
- Unsupported claims
- Shorter waits
- Resident acceptance
- Dispatcher time saved
Pre-sales engineering
Role takeaway
- Fit
- Vendor AI assistant for non-emergency routing.
- Architecture and integration
- Non-emergency line to AVA; routing to departments; transfer to 911 dispatch.
- Prerequisites
- Call logs with transfer timestamps
- Urgency escalation rules
- Records access scoping
- Constraints
- No published performance data
- Anecdotal reaction only
- Security
- Limit what case and bail information the assistant can disclose and to whom.
- Proof of value
- Time-to-human after request
- Share of urgent calls escalated
- Complaint rate
Delivery
Role takeaway
- Work
- Publish caller metrics, review urgent-call samples, share with peer counties.
- Dependencies
- Aurelian
- Sheriff's office records
- Neighboring counties
- Ownership
- Ozaukee County Sheriff's Office communications center.
- Skills and adoption
- Dispatchers review flagged calls and give feedback on routing rules.
- Governance checkpoints
- 30-day caller metrics
- Quarterly complaint review
- Acceptance criteria
- Time-to-human reported monthly
- Every complaint reviewed
- Risks
- Callers abandon before reaching a person
- Urgent calls misjudged
- Trust erosion
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?
Vendor conversational assistant on the non-emergency line with routing to departments and transfer to 911.
Governance
Who approves, reviews and stays accountable for outcomes?
Public skepticism argues for published performance and complaint data; none is reported.
Security and privacy
What data, permissions and controls need testing?
Not addressed in the report; callers can ask about case information and bail, which implies access to records data that should be scoped.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Residents' preference for a person is the main concern; the sheriff says 911 staffing does not change. The AI discloses that it is automated.
Procurement
What should contracts, pricing and exit terms secure?
Same vendor product spreading across neighboring Wisconsin counties, which allows peer comparison if agencies share data.
Operating model
Which teams own the service once it runs?
AI first answer on non-emergency lines with human dispatch behind it.
Publication history
- 2026-10-06Emergency Services · Issue 315 resources
Stable resource ID: tmj4-ozaukee-ava-resident-reaction-20261006