From the Emergency Services edition of September 28, 2026
Long Beach city page: CommsCoach AI to score 100% of 911 calls for supervisor coaching
City of Long Beach Department of Disaster Preparedness and Emergency Communications (republishing ABC7) · Municipal emergency communications / public reporting · United States (Long Beach, California)
- Publisher
- Long Beach.gov Disaster Preparedness news
- Original publication
- 2026-02-23
- Source retrieved
- 2026-09-29
- Event date
- 2026-02-22
What happened
A February 23, 2026 City of Long Beach news page (republishing ABC7, Feb 22) states LB9-1-1 will use GovWorx CommsCoach AI to review emergency calls and score dispatcher handling. The city reports ~600,000 911 calls/year; national standards target ≥2% QA (~12,000 calls) previously done manually. Director Reginald Harrison says the AI tool enables review of 100% of calls, with supervisors reviewing flagged calls for coaching. Contract cited at ~$68,000/year through February 2028; vendor claims ~250 other 911 centers use the tech. Harrison states AI will not replace dispatchers, take calls, or replace human judgment, and that AI listening stays within the city's secure data system after privacy/HIPAA vetting. Program described as in pilot phase.
Why it matters
Municipal primary URL (not previously archived; Hoodline secondary was) documenting 911 AI QA procurement, HITL coaching, and privacy claims. Why now: pairs with St. John's Aug 2026 AQA metrics as a second independent jurisdiction on full-coverage QA AI after recent non-emergency answering editions.
Evidence and measured results
Opened longbeach.gov HTML via curl. Release date 2026-02-23; 600,000 calls; 2%/12,000 standard; 100% review claim; CommsCoach/GovWorx; $68,000/yr to Feb 2028; HITL coaching and on-premises-data claim from page.
Limitations and uncertainty
City/press announcement of a pilot—not measured post-deployment outcomes; 100% review claim is capability framing; Hoodline/privacy package already partially covered related facts.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-28; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Large PSAPs cannot meet meaningful QA sampling without AI assist or more supervisors.
- Stakeholders
- ECC director
- City privacy/security
- Supervisors
- Dispatcher workforce
- Discovery questions
- Pilot vs production status?
- Will scores enter evals?
- Where does audio process?
- What flag rate is tolerable?
- Value hypothesis
- AI scoring may enable near-full QA coverage if supervisors still coach flags and privacy controls hold.
- Potential engagement
- Pilot governance and KPI design workshop before citywide eval use.
- Unsupported claims
- Proven quality improvement
- AI replaces dispatchers
- HIPAA claim equals completed audit
Pre-sales engineering
Role takeaway
- Fit
- Recording-based AI QA scoring with supervisor flag review.
- Architecture and integration
- 911 recorder → CommsCoach scores → supervisor flag queue → coaching/eval systems.
- Prerequisites
- Recording integration
- Score rubric
- City-approved hosting
- Access logging
- Constraints
- Pilot phase
- Press-only metrics
- Sensitive PHI/PII on calls
- Security
- Enforce city data-system residency claims, HIPAA controls, and least-privilege access to scores/audio.
- Proof of value
- Supervisor agreement on flags
- Coaching cycle time
- QA coverage vs 2% baseline
Delivery
Role takeaway
- Work
- Configure pilot, train coaches, and monitor privacy/labor impacts.
- Dependencies
- City security team
- GovWorx
- ECC supervisors
- Ownership
- Disaster Preparedness/ECC director owns program; supervisors own coaching.
- Skills and adoption
- Teach supervisors to use flags as coaching prompts, not automatic discipline.
- Governance checkpoints
- Privacy review gate
- Pilot exit criteria
- Labor consultation
- Acceptance criteria
- HITL on flagged calls
- No live-call replacement
- Documented data residency
- Risks
- Eval mission creep
- Privacy incident
- Dispatcher distrust
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?
Plan AI QA as a scoring sidecar on call recordings with supervisor flag queues; keep scoring out of live dispatch decisioning unless separately validated.
Governance
Who approves, reviews and stays accountable for outcomes?
Publish how scores enter evaluations, privacy report-card commitments, and pilot exit criteria before citywide performance use.
Security and privacy
What data, permissions and controls need testing?
City claims AI listening stays in city secure systems under HIPAA-aligned vetting—verify residency, subprocessors, and deletion of unmapped sensitive fields in the contract.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Reframes supervisor time from sampling toward coaching flagged calls; requires clear messaging that AI scores support development, not silent replacement.
Procurement
What should contracts, pricing and exit terms secure?
Budget modest SaaS (~$68k/yr cited) plus privacy/security review time; require measurable pilot KPIs before expanding eval use.
Operating model
Which teams own the service once it runs?
Supervisors remain final coaches/evaluators; AI only prioritizes which of 100% scored calls get human attention.
Publication history
- 2026-09-28Emergency Services · Issue 234 resources
Stable resource ID: longbeach-lb911-commscoach-qa-city-20260223