{"resourceId":"denver-co-sunny-chatbot-continuity-311-call-warning-20261021","versions":[{"version":"external-4a21949dea64307ae57496afbf22f43ff0263db9384a6c42c8d50d0714f71493","resource":{"id":"denver-co-sunny-chatbot-continuity-311-call-warning-20261021","title":"Denver warns of a 40% rise in 311 calls if its Sunny chatbot lapses, and plans three new 311 agents, after council rejected the Citibot extension","organization":"City and County of Denver, Colorado","sector":"311 resident services","geography":"Denver, Colorado, United States","publishedAt":"21 October 2026, 7:40 PM MT (Denver7, Ryan Fish)","publicationDate":"2026-10-21","eventDate":null,"sourceName":"Denver7 (KMGH)","sourceLabel":"Local broadcast news reporting with city statements","sourceUrl":"https://www.denver7.com/news/local-news/after-council-pushback-denvers-ai-chatbot-faces-uncertain-future","evidenceClass":"independent-reporting","outcomeClass":"mixed","topics":["operating-model","governance-procurement","accessibility-workforce"],"finding":"Denver7 reported on 21 October 2026 that, after Denver City Council voted 9-3 the previous week to reject a five-year, $3.9 million contract extension with Citibot, the city is exploring options to keep its Sunny chatbot. The city said the contract ends at the end of October, though money is budgeted through this year and into 2027. It plans to hire and train three new 311 agents by next summer and warned that if Sunny became unavailable it would expect a 40% increase in 311 calls with longer waits. The mayor's office cited a satisfaction rating of around 90% and support for 72 languages; Councilmember Paul Kashmann said the city should hire people instead.","sledRelevance":"This is new information after the archived council vote: the city's own continuity estimate and a staffing response, showing what a sudden chatbot lapse is expected to cost a 311 operation.","evidence":"City statements to Denver7: 40% projected increase in 311 calls if Sunny lapses; three new 311 agents by next summer; budget into 2027; around 90% satisfaction; 72 languages. Council vote 9-3. None independently verified.","architectureImplications":"A single-vendor chatbot carrying a large share of 311 contacts becomes a dependency; continuity plans need a fallback channel or a portable knowledge base if the contract ends.","governanceImplications":"The council has now forced a decision on boundaries for AI in resident service; contract renewals that arrive late leave little room for review, which several members criticised.","securityPrivacyImplications":"Not addressed in the article. A vendor transition would raise questions about conversation data retention and return.","caveats":"The 40% figure is a city projection, and the satisfaction figure has no stated method. The article does not report accuracy measures, which were a council concern in earlier coverage.","streamIds":["local-government"],"roles":{"sales":"Framing: Denver shows the cost of not planning for chatbot continuity. The city now projects a 40% rise in 311 calls if Sunny lapses, while the council wants humans hired and boundaries set. Conversations with other cities should focus on exit plans, evidence packages for councils and staffing balance, not on adding channels. Satisfaction and hold-time claims here are city statements without method and should not be used as proof of value.","engineering":"Framing: vendor lock-in is a real architecture risk for resident assistants. If a contract ends, the city needs its knowledge base, intents, integrations with the 311 CRM and conversation history in portable form. Engineers should design for a fallback to web forms and phone routing, and for a possible in-house or alternative-vendor rebuild, which one academic quoted suggests is now easier.","delivery":"Framing: continuity and workforce planning belong in delivery from day one. Denver's response combines hiring three agents with exploring options to keep Sunny. Interpretation: delivery teams should maintain a tested runbook for chatbot outage or contract lapse, publish accuracy and escalation metrics to council regularly, and schedule renewals early enough for scrutiny."},"roleDetails":{"sales":{"customerProblem":"A 311 operation that depends on a chatbot faces a sudden contract lapse and a council sceptical of AI replacing staff.","stakeholders":["Mayor's office","Denver Technology Services","311 operations","City Council","Citibot","Residents using digital channels"],"discoveryQuestions":["What share of contacts would shift to phones if the bot stopped?","What accuracy and escalation evidence would satisfy council?","Is the knowledge base portable to another platform?","How will new agents and the bot divide work?"],"valueHypothesis":"Bounded: continuity planning and transparent metrics may reduce the risk of service disruption and political reversal.","potentialEngagement":"Continuity and evidence review for an at-risk resident chatbot, covering exit options and council reporting.","unsupportedClaims":["The 40% call increase as a measured fact","90% satisfaction as a validated measure","Reduced burnout or attrition caused by the bot"]},"engineering":{"fit":"Cities running vendor chatbots that carry a material share of 311 contacts.","architectureIntegration":"Web chatbot integrated with the 311 reporting hub; vendor-hosted; a planned voicebot was part of the rejected extension.","prerequisites":["Export rights to knowledge base and logs","Fallback routing to forms and phones","CRM integration documentation"],"constraints":["Contract expires end of October","Council approval needed for extension","Unknown portability of vendor configuration"],"security":"Vendor transition requires defined handling of conversation data deletion or return.","proofOfValue":["Simulate a bot outage and measure phone queue impact","Benchmark an alternative build on the same content","Publish accuracy sampling to council"]},"delivery":{"work":"Prepare continuity runbook, staffing plan and evidence pack for any renewed or replacement contract.","dependencies":["Council decision","Budget into 2027","Hiring three 311 agents","Vendor cooperation on data"],"ownership":"Denver Technology Services with 311 operations.","skillsAdoption":"New agents need training; staff may need skills to review bot answers if an alternative is built.","governanceCheckpoints":["Council review of accuracy and escalation metrics","Renewal brought forward well before expiry","Labour impact statement"],"acceptanceCriteria":["Proposed: documented fallback live before any lapse","Proposed: monthly accuracy sample published","Proposed: phone wait time tracked against pre-lapse baseline"],"risks":["Service disruption in November","Longer wait times","Further council rejection","Costly emergency procurement"]}},"retrievedAt":"2026-10-21T22:13:32-05:00","enrichedAt":"2026-10-21T22:18:42-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"72-language support is claimed; losing it could reduce access for non-English speakers. Council framing centres job protection; the city plans three new agents.","procurementImplications":"Late renewal left little time for review; a rebuild or alternative vendor would need a new procurement.","operatingModelImplications":"Shows a hybrid human-plus-bot 311 model under political pressure, with the city adding staff while seeking to keep automation.","sourceVerification":{"openedUrl":"https://www.denver7.com/news/local-news/after-council-pushback-denvers-ai-chatbot-faces-uncertain-future","referenceExcerpt":"we would expect to see a 40% increase in 311 calls, with a corresponding increase in caller wait times.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}