From the Emergency Services edition of October 6, 2026
Boulder Police and Fire Communications Center starts phased AI non-emergency line with live dispatcher monitoring and a complaint path
Boulder Police and Fire Communications Center (BPFC), City of Boulder, Colorado · Municipal PSAP / police and fire emergency communications · United States (Colorado)
- Publisher
- City of Boulder News
- Original publication
- 2026-10-06
- Source retrieved
- 2026-10-07
- Event date
- 2026-10-06
What happened
The City of Boulder announced on Oct 6, 2026 that its combined police and fire dispatch center will use AI on the non-emergency line during limited hours and days, with full implementation targeted for the end of November. It will not answer 911 and will eventually replace the phone menu. The city's FAQ calls the assistant ANET (Automated Non-Emergency Triage) and says it works in English and Spanish, transcribes and summarizes every call, lets dispatchers watch live and join, and transfers on request or when it detects an emergency. Callers can phone in complaints, and CAD-entered calls trigger a PowerEngage survey.
Why it matters
A cross-trained police and fire PSAP (the city says dispatchers handle emergency and non-emergency calls while dispatching police, fire and EMS) is adopting a conversational AI front door; it is the most detailed public description of controls among recent non-emergency AI launches. Cross-relevant to public safety because most listed call types are police matters.
Evidence and measured results
Official announcement and FAQ, not an evaluation (closest schema class used). No vendor, accuracy, hold-time or transfer data are published; the pilot has not started reporting.
Limitations and uncertainty
The release says AI use starts 'this month', while the FAQ says the soft launch begins at the end of October 2026; vendor not named; no results yet.
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
- Routine calls compete with 911 and radio work for the same cross-trained dispatchers, producing hold times.
- Stakeholders
- Dispatch manager
- Police and fire chiefs
- City IT
- Records/privacy officer
- Residents
- Discovery questions
- Which non-emergency call types will the AI handle first?
- How will you test emergency detection?
- What results will you publish before full rollout?
- Who reviews complaints about AI calls?
- Value hypothesis
- A supervised AI intake may shorten non-emergency waits if transfers and summaries prove reliable in the pilot windows.
- Potential engagement
- Pilot evaluation plan covering emergency transfer tests, summary accuracy and caller feedback.
- Unsupported claims
- Measured hold-time reduction
- Accurate emergency detection
- Staff time saved
Pre-sales engineering
Role takeaway
- Fit
- Conversational intake and routing on a PSAP non-emergency line.
- Architecture and integration
- Voice agent on non-emergency trunk; live transcript to dispatchers; summaries for staff review; text links; CAD entries trigger PowerEngage surveys.
- Prerequisites
- Call-type catalog
- Emergency transfer rules
- Bilingual test scripts
- CAD integration for summaries
- Constraints
- No published accuracy data
- Vendor undisclosed
- Launch timing inconsistent between release and FAQ
- Security
- Recordings, transcripts and summaries restricted to authorized staff; confirm vendor retention and text-link security.
- Proof of value
- Emergency transfer rate on scripted English and Spanish calls
- Summary accuracy on sampled calls
- Non-emergency hold time in AI windows vs live windows
Delivery
Role takeaway
- Work
- Run limited windows, sample calls, track transfers and complaints, publish results before full rollout.
- Dependencies
- AI vendor
- Telephony
- CAD
- PowerEngage surveys
- Ownership
- BPFC dispatch manager.
- Skills and adoption
- Dispatchers monitor live transcripts and learn when to step in.
- Governance checkpoints
- Soft-launch review
- Pre-expansion results review
- Post-November full-implementation review
- Acceptance criteria
- All scripted emergencies transferred
- Summary error rate measured on a weekly sample
- Complaints reviewed within a set period
- Risks
- Missed emergency on non-emergency line
- Wrong details written into requests
- Callers unaware they are talking to AI
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?
Conversational voice agent on the non-emergency trunk that collects caller details, reads back a summary, may text links to online forms, creates requests for staff review, and hands off to dispatchers; live transcript visible to dispatchers; CAD entries trigger surveys.
Governance
Who approves, reviews and stays accountable for outcomes?
Phased soft launch with limited windows so staff can monitor and adjust; staff review calls and summaries for quality; complaint path routes back to dispatch. No published metrics or review schedule.
Security and privacy
What data, permissions and controls need testing?
Calls are recorded, transcribed and summarized; access is limited to authorized BPFC and city public-safety staff; retention follows Colorado law and city records policy. Vendor data handling is not described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
English and Spanish support; caller can ask for a dispatcher at any time. The city frames the tool as giving them more time for priority calls, not replacing them.
Procurement
What should contracts, pricing and exit terms secure?
Vendor and contract terms are not disclosed; buyers should ask for data-use, retention and accuracy terms before similar deployments.
Operating model
Which teams own the service once it runs?
AI handles intake and summary; dispatchers supervise live and own every emergency and escalation.
Publication history
- 2026-10-06Emergency Services · Issue 315 resources
Stable resource ID: boulder-bpfc-anet-ai-nonemergency-line-20261006