{"resourceId":"denver-sunny-slalom-extensions-rejected-measurement-gaps-20261015","versions":[{"version":"external-1cd8c3d76f447f70eb100fb802461fa023cc1e6e1f641b35edf08da1010594d4","resource":{"id":"denver-sunny-slalom-extensions-rejected-measurement-gaps-20261015","title":"Denver council rejects Sunny chatbot and Slalom tech extensions; critics cite unmeasured accuracy and ~$600K/year unfunded voicebot","organization":"City and County of Denver, Colorado","sector":"Municipal 311 digital services and IT contracting","geography":"Denver, Colorado, United States","publishedAt":"October 15, 2026","publicationDate":"2026-10-15","eventDate":"2026-10-13","sourceName":"The Badger (Denver Metro)","sourceLabel":"Independent local news report of council meeting","sourceUrl":"https://denver.thebadger.news/articles/2026-10-15-denver-council-sunny-311-slalom-contract-extensions","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","operating-model","accessibility-workforce"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Without renewal, resident chatbot continuity depends on city-controlled content and 311 integrations; Slalom rejection stresses need for alternate specialized delivery capacity.","governanceImplications":"Council treated measurement of accuracy/satisfaction as a prerequisite for multi-year AI spend; voice add-on lacking identified funding weakened the package.","securityPrivacyImplications":"Not discussed for Sunny shutdown or Slalom; vendor transcript handling at contract end remains an open operational issue.","caveats":"Overlaps yesterday's Sunny coverage; Slalom contract is not specifically AI; mayor's office still seeking a Sunny path per prior reporting.","streamIds":["local-government"],"roles":{"sales":"Sales framing: Denver's follow-on coverage shows renewals fail when accuracy is unmeasured and add-ons are unfunded. Help clients define accuracy sampling and human-access SLAs before multi-year asks; separate optional voicebots into funded line items. Discovery: what accuracy evidence exists, voicebot funding status and 311 staffing narrative. Bounded engagement: pre-renewal measurement package and council briefing—not a five-year sole extension. Interpretation: satisfaction scores without accuracy methods will not carry the vote.","engineering":"Engineering framing: Fit is incumbent resident AI needing independent answer scoring and exportable knowledge/transcripts if the vendor contract ends this month. Proof of value: blind accuracy samples, handoff success and a documented decommission path. Constraints: council calendar and paid-through date. Interpretation: measurement instrumentation is now a renewal requirement, not a nice-to-have.","delivery":"Delivery framing: If Sunny shuts off at month end, execute content/export fallback and 311 staffing coverage. For any renegotiation, publish accuracy methods and drop unfunded voice scope. Ownership: Technology Services with 311. Risks: service gap, unfinished Slalom-dependent projects and continued trust erosion. Interpretation: treat Oct 31 as a hard operational deadline."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Published accuracy and escalation metrics may support a shorter renewal; not guaranteed.","potentialEngagement":"Two-to-four week measurement and shutdown/continuity plan before month-end.","unsupportedClaims":["That Sunny is accurate at any stated rate","That voicebot funding exists","That Slalom rejection is an AI-specific finding"]},"engineering":{"fit":"Cities renewing vendor 311 chatbots under elected scrutiny of metrics.","architectureIntegration":"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.","proofOfValue":["Blind accuracy sample with method published","Measured human handoff rate","Shutdown drill completed"]},"delivery":{"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.","skillsAdoption":"Staff score sampled answers and document escalation failures.","governanceCheckpoints":["Measurement report before any new vote","Shutdown/continuity decision by paid-through date"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-15T22:22:30-05:00","enrichedAt":"2026-10-15T22:28:00-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Debate pits digital deflection and staff relief against desire for human 311 responses and hiring.","procurementImplications":"Multi-year AI chatbot extension and separate high-rate on-call tech capacity both failed; expect shorter terms, funded options and published metrics.","operatingModelImplications":"Sunny framed as digital 311 channel (~40% digital share claimed); council wants human access preserved and accuracy measured.","updateExplanation":"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.","sourceVerification":{"openedUrl":"https://denver.thebadger.news/articles/2026-10-15-denver-council-sunny-311-slalom-contract-extensions","referenceExcerpt":"Other critics said the city had not sufficiently measured the chatbot's accuracy or user satisfaction.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}