From the Local Government edition of October 15, 2026
Denver council rejects Sunny chatbot and Slalom tech extensions; critics cite unmeasured accuracy and ~$600K/year unfunded voicebot
City and County of Denver, Colorado · Municipal 311 digital services and IT contracting · Denver, Colorado, United States
- Publisher
- The Badger (Denver Metro)
- Original publication
- October 15, 2026
- Source retrieved
- 2026-10-16
- Event date
- 2026-10-13
What happened
Oct 15 report on the Oct 13 votes: Citibot/Sunny five-year extension failed 9–3; Slalom three-year/$5M extension failed 10–2. Staff said Sunny would not continue after the current paid period (through end of October) without an extension. Council criticized unreliable answers (one member said Sunny directed her to a park outside Denver) and insufficient measurement of accuracy and user satisfaction; they argued automation should not come at the expense of 311 staffing. Staff said ~40% of 311 inquiries arrive digitally; a voice assistant was only a possible future pilot contingent on funding, estimated ~$600,000/year with funding not identified. Slalom work was described as technology/data capacity, not specifically AI services; staff warned some projects may go unfinished without replacement capacity.
Why it matters
Same-day follow-on to the Oct 14 archived Denverite Sunny rejection, adding measurement-gap critique, unfunded ~$600K voicebot detail and parallel Slalom capacity vote—useful for renewal and AI-adjacent IT contracting lessons.
Evidence and measured results
The Badger article opened in full via WebFetch and curl. Vote tallies attributed to meeting recording; voicebot cost from city's Citibot extension request as reported. Prior Denverite coverage already archived for the core Sunny vote.
Limitations and uncertainty
Overlaps yesterday's Sunny coverage; Slalom contract is not specifically AI; mayor's office still seeking a Sunny path per prior reporting.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-15; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Council will not extend a resident chatbot without measured accuracy and clear human-access value; optional voicebot lacks funding.
- Stakeholders
- City council
- Technology Services
- 311 operations
- Mayor's office
- Residents
- Discovery questions
- What accuracy sampling method exists today?
- Is voicebot funding identified?
- What is the paid-through date and shutdown runbook?
- How is path-to-human measured?
- Value hypothesis
- Published accuracy and escalation metrics may support a shorter renewal; not guaranteed.
- Potential engagement
- Two-to-four week measurement and shutdown/continuity plan before month-end.
- Unsupported claims
- That Sunny is accurate at any stated rate
- That voicebot funding exists
- That Slalom rejection is an AI-specific finding
Pre-sales engineering
Role takeaway
- Fit
- Cities renewing vendor 311 chatbots under elected scrutiny of metrics.
- Architecture and integration
- Instrument answer logging for sampling; ensure knowledge/transcript export; time-box any voice pilot behind funding.
- Prerequisites
- Transcript access
- 311 topic gold answers
- Contract end date clarity
- Constraints
- Council vote requirements
- Unfunded voice scope
- Short runway to paid-through date
- Security
- Plan vendor data return/deletion if service ends.
- Proof of value
- Blind accuracy sample with method published
- Measured human handoff rate
- Shutdown drill completed
Delivery
Role takeaway
- Work
- Run accuracy sample, brief council, execute continuity or renegotiation without unfunded voice.
- Dependencies
- Vendor cooperation
- 311 staffing plan
- Council schedule
- Ownership
- Technology Services with 311 operations.
- Skills and adoption
- Staff score sampled answers and document escalation failures.
- Governance checkpoints
- Measurement report before any new vote
- Shutdown/continuity decision by paid-through date
- Acceptance criteria
- Proposed: accuracy method and sample size published
- Proposed: human-access path tested on all channels
- Proposed: voicebot only if funding identified
- Risks
- Hard stop of Sunny
- Project delivery gaps after Slalom
- Repeated council rejection
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?
Without renewal, resident chatbot continuity depends on city-controlled content and 311 integrations; Slalom rejection stresses need for alternate specialized delivery capacity.
Governance
Who approves, reviews and stays accountable for outcomes?
Council treated measurement of accuracy/satisfaction as a prerequisite for multi-year AI spend; voice add-on lacking identified funding weakened the package.
Security and privacy
What data, permissions and controls need testing?
Not discussed for Sunny shutdown or Slalom; vendor transcript handling at contract end remains an open operational issue.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Debate pits digital deflection and staff relief against desire for human 311 responses and hiring.
Procurement
What should contracts, pricing and exit terms secure?
Multi-year AI chatbot extension and separate high-rate on-call tech capacity both failed; expect shorter terms, funded options and published metrics.
Operating model
Which teams own the service once it runs?
Sunny framed as digital 311 channel (~40% digital share claimed); council wants human access preserved and accuracy measured.
What changed
New Oct 15 independent report of the Oct 13 votes adds measurement-gap critique, ~$600K/year unfunded voicebot detail and the parallel Slalom 10–2 rejection; core Sunny non-renewal was covered 2026-10-14 via Denverite.
Publication history
- 2026-10-15Local Government · Issue 405 resources
Stable resource ID: denver-sunny-slalom-extensions-rejected-measurement-gaps-20261015