From the Emergency Services edition of September 18, 2026
Grays Harbor Communications deploys AVA for non-emergency calls while keeping humans on 911
Grays Harbor Communications (GHCC) / Aurelian · 911 / PSAP non-emergency call automation (consolidated fire, EMS, and law dispatch) · Grays Harbor County, Washington, United States
- Publisher
- The Daily World
- Original publication
- 2026-09-16
- Source retrieved
- 2026-09-19
- Event date
- 2026-09-16
What happened
On 2026-09-16 The Daily World reported GHCC deployed Aurelian’s AVA on the non-emergency line only—explicitly not answering 911—so telecommunicators can prioritize emergency calls and radio traffic; 2025 volumes were 42,014 emergency and 60,596 non-emergency (~60% non-emergency); AVA may create CAD calls for human review, supports 45+ languages, and transfers suspected emergencies; Aurelian claims 60–75% non-emergency handling within 90 days at current agencies—without a published Grays Harbor post-go-live audit in the article.
Why it matters
Why now: published 2026-09-16 and not archived; newly relevant after 2026-09-16/17 La Vergne and Akron Ava catalogue entries—documents another U.S. consolidated fire/EMS PSAP expanding non-emergency AI with a hard 911 human boundary.
Evidence and measured results
Article dated Sept 16, 2026; Green quotes that trained telecommunicators answer 911; 42,014 / 60,596 2025 volumes; nearly 60% non-emergency; CAD create-for-review; 45+ languages; emergency-transfer design; Aurelian CEO quote; vendor 60–75% within 90 days; ~40 agencies / 15M residents / >99.95% uptime since Apr 2024 (vendor).
Limitations and uncertainty
Local journalism plus vendor platform averages; no independent GHCC outcome table; combined LE/fire/EMS center—stream focus is fire/EMS capacity and emergency-line protection.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-19; 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 PSAPs drown emergency telecommunicators in non-emergency volume without a safe automation boundary that keeps humans on 911.
- Stakeholders
- ECC directors
- Fire/EMS chiefs
- County executives
- Public information officers
- Discovery questions
- Is 911 hard-excluded at the trunk?
- What local diversion KPI will be published at 90 days?
- How are emergency-intent transfers audited?
- What CAD fields may AVA write?
- Value hypothesis
- If non-emergency AI cuts hold times without raising 911 spillover under audited transfer rules, agencies may justify a bounded pilot—without claiming clinical benefit.
- Potential engagement
- Bounded non-emergency diversion pilot design with spillover and CAD-review package.
- Unsupported claims
- Guaranteed FTE reduction
- Local 60–75% diversion proven here
- 911 answer-time improvement from this article
- Safe live 911 AI answering
Pre-sales engineering
Role takeaway
- Fit
- Non-emergency conversational AI with CAD create-for-review and emergency transfer; humans retain 911.
- Architecture and integration
- Non-emergency trunks → AVA → CAD ticket / transfer; 911 trunks untouched.
- Prerequisites
- Trunk separation verification
- CAD write ACLs
- Emergency-intent test set
- Public script
- Constraints
- Vendor portfolio averages only
- No local post-go-live audit in source
- Combined LE/fire/EMS politics
- Security
- Limit vendor training on caller PII; authenticate CAD writes; log transfers.
- Proof of value
- Local diversion rate
- Callback/reopen rate
- 911 spillover complaints
- Emergency-line occupancy
Delivery
Role takeaway
- Work
- Cut over non-emergency numbers, train CAD review, sample transfers, publish KPIs.
- Dependencies
- CAD vendor support
- QA sampling capacity
- PIO messaging
- Ownership
- ECC executive director owns scope; QA supervisor owns transfer audits.
- Skills and adoption
- Teach staff to reclaim emergency transfers and explain AVA scope to callers.
- Governance checkpoints
- Go-live trunk check
- 30-day spillover review
- 90-day continue/stop
- Acceptance criteria
- Documented 911 exclusion
- Dated diversion KPIs
- Sampled transfer accuracy
- Risks
- Vendor averages as local proof
- Mission creep to 911
- Unmonitored CAD junk tickets
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 trunk AI conversational agent with CAD call-for-service creation and human review; hard separation from 911 trunks; language and emergency-intent detection as transfer triggers.
Governance
Who approves, reviews and stays accountable for outcomes?
Publish local diversion, callback, and 911-spillover metrics with dated denominators before treating vendor 60–75% claims as GHCC results; keep public reassurance scripts aligned with trunk separation.
Security and privacy
What data, permissions and controls need testing?
Non-emergency identity/location collection still needs vendor retention, training-use, and CAD-write authentication controls even when 911 audio is out of scope.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
45+ language support may help LEP non-emergency callers, but accessibility for disabled callers and AI-averse residents is not evaluated; workforce impact is telecommunicator attention shift toward 911/radio.
Procurement
What should contracts, pricing and exit terms secure?
Demand local KPI definitions and spillover SLAs in the Aurelian contract rather than accepting portfolio 60–75% marketing as acceptance criteria.
Operating model
Which teams own the service once it runs?
Splits non-emergency intake from emergency call-taking so the same understaffed crew can protect 911/radio priority while AI drafts non-emergency CAD work.
Publication history
- 2026-09-18Emergency Services · Issue 134 resources
Stable resource ID: grays-harbor-ava-nonemergency-2026