From the Emergency Services edition of September 22, 2026
Colorado Springs Communications Center launches Axon Prepared AI; S.A.R.A.H. answers non-emergency calls first while humans keep all 911
Colorado Springs Police Department Public Safety Communications Center · Local emergency communications / PSAP · Colorado Springs, Colorado, United States
- Publisher
- KKTV
- Original publication
- 2026-09-22
- Source retrieved
- 2026-09-23
- Event date
- 2026-09-22
What happened
On 2026-09-22 CSPD announced its Public Safety Communications Center has launched Prepared by Axon after April 2026 testing. Trained call takers still answer all 911 calls; the AI agent S.A.R.A.H. now answers non-emergency calls first. Non-emergency traffic is more than half of telephone volume. The stack transcribes calls, translates in dozens of languages, identifies critical details, generates summaries, and helps route non-emergency calls to police and fire. Callers may still request a person; staff will review performance and update responses as community needs change. No independent answer-time or diversion metrics are published in the article.
Why it matters
Direct PSAP/dispatch operating-model evidence for emergency-services: joint communications-center AI that protects human 911 answering while offloading non-emergency load that includes fire and medical service requests. Transferable to other multi-agency PSAPs evaluating vendor AI front doors. Policing brand on the agency is noted; this edition uses the piece for dispatch/fire/medical routing and 911 answer-time intent, not for investigative policing use cases.
Evidence and measured results
KKTV quotes CSPD that Prepared by Axon assists emergency and non-emergency response; testing began April 2026; call takers continue to answer all 911; S.A.R.A.H. answers non-emergency first; non-emergency is over half of calls; transcription, real-time translation in dozens of languages, critical-detail identification, summaries, and routing to police and fire; human option retained; regular performance review planned. No measured before/after KPIs in the article.
Limitations and uncertainty
Police-department press framing; independent measured outcomes (answer-time deltas, diversion rate, false-route rate) are not in the article. Axon vendor capabilities described via agency release. Medical routing is mentioned at system-purpose level without EMS outcome data.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- PSAPs need to shed non-emergency load so telecommunicators can protect 911 answer times without replacing humans on emergencies.
- Stakeholders
- Communications center directors
- Fire/EMS dispatch supervisors
- City IT/security
- Elected officials watching 911 metrics
- Discovery questions
- What share of calls is non-emergency today?
- Which languages must be covered?
- How is escalate-to-human logged and audited?
- Which 911 answer-time KPI is the success metric?
- Value hypothesis
- An AI non-emergency front door can free capacity for 911 if humans retain all emergency calls and diversion quality is measured.
- Potential engagement
- Bounded PSAP intake pilot design and KPI workshop for Axon-class non-emergency agents—not a guaranteed citywide AI 911 program.
- Unsupported claims
- Guaranteed faster 911 answers from this launch alone
- Safe AI handling of life-threat calls
- Proven EMS outcome improvement
Pre-sales engineering
Role takeaway
- Fit
- Voice AI agent on non-emergency trunks with ASR/translation/summary feeding CAD, while 911 stays human-answered.
- Architecture and integration
- Telephony front door to AI agent to CAD/RMS notes; parallel recording and human takeover path; monitoring for agent outage failover to humans.
- Prerequisites
- Mapped non-emergency vs 911 call flows
- CAD API or wrap-up fields for AI summaries
- Language pack requirements
- Recording/retention policy alignment
- Constraints
- 911 must remain human-answered per agency claim
- Joint police/fire routing increases misroute risk
- Vendor lock-in to Axon Prepared stack
- Security
- Protect transcripts/summaries as CJIS/HIPAA-adjacent sensitive data; define training-data use and access logging.
- Proof of value
- Measure non-emergency diversion and escalate rates
- Track 911 answer-within-15s before/after
- Sample translation/summary error reviews weekly
Delivery
Role takeaway
- Work
- Configure S.A.R.A.H. flows, train call takers on takeover, publish caller guidance, and stand up performance review rituals.
- Dependencies
- Axon Prepared licensing
- Telephony/CAD vendors
- Communications center supervisors
- City service directory accuracy
- Ownership
- Public Safety Communications Center owns operations; IT owns integrations; fire/EMS liaisons own routing accuracy feedback.
- Skills and adoption
- Telecommunicators need takeover drills and trust that AI is not scoring them punitively; supervisors need QA sampling of AI sessions.
- Governance checkpoints
- Go-live checklist confirming human 911 path
- 30-day metrics review
- Content change-control board for AI responses
- Acceptance criteria
- 100% of 911 calls still human-answered in logs
- Caller human-option path tested
- Published diversion and escalate metrics for first 30 days
- Risks
- Misrouting fire/medical non-emergency requests
- Public trust backlash if AI answers unexpected emergencies
- Unmeasured vendor claims overstated in procurement
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?
Expect a telephony/IVR or voice-agent front door integrated with CAD/call-taking workflows, real-time ASR/translation, and summarization that updates call records. Keep a hard path for all 911 to human telecommunicators and a clear escalate-to-human control for non-emergency sessions. Plan language coverage, summary quality monitoring, and failover if the AI agent is unavailable.
Governance
Who approves, reviews and stays accountable for outcomes?
Document the non-emergency-only scope, human 911 retention, caller notice about AI, and change-control for response content as services change. Align review cadence with communications-center leadership and elected oversight. Avoid marketing autonomous emergency triage from this launch announcement alone.
Security and privacy
What data, permissions and controls need testing?
Call audio, transcripts, translations, and AI summaries are sensitive public-safety data. Require vendor data-handling terms, retention limits, access controls, and audit of who can read summaries. Clarify whether model training uses local call content.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Translation in dozens of languages may improve access for LEP callers on non-emergency lines; workforce benefit is claimed capacity for 911, but burnout reduction is not measured here.
Procurement
What should contracts, pricing and exit terms secure?
Sole-source or platform-aligned Axon procurement is likely; require measurable SLAs for diversion quality, uptime, and human escalate—not feature marketing alone.
Operating model
Which teams own the service once it runs?
Shifts non-emergency intake to AI-first with human backup; emergency path unchanged. Requires ongoing content stewardship as city services change.
Publication history
- 2026-09-22Emergency Services · Issue 175 resources
Stable resource ID: kktv-cspd-axon-sarah-nonemergency-20260922