From the Emergency Services edition of September 16, 2026
La Vergne deploys Aurelian AVA on non-emergency line amid 73% non-emergency call share
City of La Vergne Emergency Communications Center (Aurelian AVA) · 911 / PSAP emergency communications (police and fire dispatch) · La Vergne, Tennessee, United States
- Publisher
- Rutherford Source
- Original publication
- 2026-09-16
- Source retrieved
- 2026-09-17
- Event date
- 2026-09-16
What happened
On 2026-09-16 Rutherford Source reported La Vergne’s Emergency Communications Center deployed Aurelian’s AVA on the non-emergency line to gather information, create CAD calls for service, and transfer potential emergencies to telecommunicators, citing ~50,000 annual calls with non-emergency about 73% (33,367) versus 12,299 911—while vendor claims of 60–75% automation and ~15 hours/week savings are not presented as La Vergne audited outcomes.
Why it matters
Why now: published on the edition date after the 2026-09-15 last run; extends the archived Jonesboro/Maine/Weber non-emergency AI pattern with a same-day U.S. fire/EMS-serving PSAP deployment announcement and explicit emergency-transfer control.
Evidence and measured results
Article states deployment, CAD create capability, emergency monitoring/transfer, language support (55+), Speck understaffing quote, volume split, and Aurelian typical partner-agency automation/hours claims. No La Vergne misroute or diversion audit table.
Limitations and uncertainty
Announcement journalism; vendor metrics not local audits; center also serves police; no hang-up or critical-escalation rates published.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-17; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Non-emergency volume (~73% here) competes with 911 and radio for scarce telecommunicators, while leaders refuse unattended AI on true emergencies.
- Stakeholders
- Emergency Communications Manager
- Telecommunicators
- Fire Rescue and police chiefs served by the center
- City leadership / PIO
- Discovery questions
- What local diversion and misroute metrics will be published at 30/90 days?
- How are AI-created CAD incidents labeled and reviewed?
- What is the emergency-transfer success rate on tested scripts?
- How is AI disclosed to non-emergency callers?
- Value hypothesis
- If AVA reliably absorbs routine non-emergency work and escalates emergently, telecommunicators may regain attention for 911—subject to local audited diversion, not vendor partner averages.
- Potential engagement
- 90-day non-emergency pilot design with CAD QA sampling, public-notice draft, and stop-rules tied to escalation failures.
- Unsupported claims
- Guaranteed 60–75% local automation
- 15 hours/week saved per telecommunicator as proven here
- Safe AI answering of 911
- Staffing reductions justified by this announcement
Pre-sales engineering
Role takeaway
- Fit
- Non-emergency multi-channel virtual assistant with CAD write and emergency transfer—not live 911 answering.
- Architecture and integration
- Non-emergency DNIS/channels → AVA dialog → CAD CFS create or human queue on emergency cues; recording/QA store aligned with PSAP retention.
- Prerequisites
- Emergency-phrase escalation tests
- CAD field for AI-originated incidents
- Vendor DPA / training-use limits
- Staff reclaim playbooks
- Constraints
- No local audited diversion yet
- Vendor metrics are partner generalizations
- Policing and fire share the same center capacity
- Security
- Encrypt recordings/transcripts; restrict vendor model training on caller audio; monitor social-engineering against the agent.
- Proof of value
- Local diversion % on audited logs
- Critical escalation success rate
- Hang-up / abandoned rate versus baseline
- Telecommunicator available minutes during peaks
Delivery
Role takeaway
- Work
- Configure AVA, train reclaim and CAD review, publish scope, and run a 90-day metrics gate before expansion.
- Dependencies
- Aurelian/CAD admin access
- QA auditor time
- Legal/PIO review
- Minimum emergency staffing floor
- Ownership
- Emergency Communications Manager owns scope; QA owns sampling/stop-rules; PIO owns public messaging.
- Skills and adoption
- Keep emergency call-taking proficiency while teaching AI supervision and CAD QA of AI-created incidents.
- Governance checkpoints
- Written non-emergency-only policy
- Public notice approval
- 90-day local metrics versus vendor claims
- Acceptance criteria
- Documented emergency-transfer tests passed
- AI-originated CAD incidents reviewable in logs
- Published description of AI scope
- Risks
- Vendor claim treated as SLA
- Mission creep onto 911
- Under-reviewed AI CAD entries
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 integrated to CAD for call-for-service creation, with emergency-intent detection transferring to human telecommunicators; multi-channel (voice/text/web) alongside traditional trunks.
Governance
Who approves, reviews and stays accountable for outcomes?
Publish scope (non-emergency only), require escalation QA before treating vendor 60–75% claims as local performance, and brief served fire/police agencies on AI-created CAD incidents.
Security and privacy
What data, permissions and controls need testing?
Voice/text/web AI sessions carry caller identity and location—apply PSAP retention, vendor training limits, and access controls comparable to recorded non-emergency lines.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
55+ language and text/web channels may help some callers, but human fallback must remain for complex or emergency situations; staffing shortages remain the root driver.
Procurement
What should contracts, pricing and exit terms secure?
Separate vendor typical performance claims from contractual SLAs; require local diversion/escalation reporting and exit rights at 90 days before multi-year lock-in.
Operating model
Which teams own the service once it runs?
Operate AVA as a non-emergency capacity valve with humans owning emergencies and CAD QA; do not reduce minimum 911 staffing based on unvalidated automation percentages.
Publication history
- 2026-09-16Emergency Services · Issue 113 resources
Stable resource ID: la-vergne-aurelian-ava-nonemergency-2026