{"resourceId":"denver-sunny-chatbot-offline-since-nov5-city-status-notice-20261105","versions":[{"version":"external-7b8d835df5d9f3e935f1bfd6b6a3fa2d2bfc9446075c0076c9e1a3f635809057","resource":{"id":"denver-sunny-chatbot-offline-since-nov5-city-status-notice-20261105","title":"Denver's Sunny chatbot has been unavailable on denvergov.org, text and WhatsApp since Nov. 5, 2026; residents directed to site search, online reporting and weekday 311 hours","organization":"City and County of Denver","sector":"Municipal 311 chatbot and constituent services","geography":"Denver, Colorado, United States","publishedAt":"Undated city status page (states unavailability beginning Nov. 5, 2026)","publicationDate":null,"eventDate":"2026-11-05","sourceName":"City and County of Denver (denvergov.org status page)","sourceLabel":"Sunny - City and County of Denver: Sunny is Unavailable","sourceUrl":"https://www.denvergov.org/Sunny","evidenceClass":"government-evaluation","outcomeClass":"cautionary","topics":["governance-procurement","operating-model","accessibility-workforce"],"finding":"Denver's official Sunny page now states that beginning November 5 the city's chatbot is unavailable and can no longer be accessed through Denvergov.org, text messaging or WhatsApp. Residents cannot ask Sunny questions, receive automated answers, report issues through Sunny, or get chatbot help outside business hours; they are directed to site search, online issue reporting, and 311 by phone Monday-Friday 7 a.m. to 5 p.m. The city says it is exploring solutions to restore Sunny as quickly as possible. This is the operational outcome of the council's Oct. 13 rejection of the Citibot extension, already covered in the archive.","sledRelevance":"Why now: the archived Oct. 14-21 coverage (Denverite, Denver7, The Badger) reported the council vote and the city's warning of a 40% rise in 311 calls if Sunny lapsed. The city's own page now confirms the lapse actually happened on Nov. 5, turning a contingency into a live continuity case for any jurisdiction depending on a vendor-operated AI front door.","evidence":"Official city status notice inspected directly; it states the start date and lost capabilities but gives no reason, no call-volume data and no restoration date.","architectureImplications":"Vendor-operated chatbot spanning web, SMS and WhatsApp channels was removed as a whole; fallback is site search, online forms and staffed 311 hours, with no after-hours conversational channel.","governanceImplications":"Contract approval lapse removed a resident-facing channel; shows the need for council-approved continuity or exit plans for AI front doors before contract expiry.","securityPrivacyImplications":"The notice does not say what happens to stored Sunny conversation data or WhatsApp/SMS records after service ends.","caveats":"Undated status page; reason for unavailability is not stated on the page (linking it to the council vote relies on archived reporting); no measured impact on 311 call volume or wait times yet. Earlier Sunny coverage is in the local-government archive; this resource records only the new Nov. 5 status.","streamIds":["citizen-engagement"],"roles":{"sales":"Sales framing: Denver turns AI chatbot continuity into a concrete buying concern. Sunny went offline on Nov. 5 across web, text and WhatsApp after the council rejected its contract extension, leaving residents with search, forms and weekday 311 hours. Discovery should ask what happens to a city's AI front door if a contract lapses, who owns transition, and what fallback capacity exists. A bounded engagement is a continuity and exit-plan review for existing chatbots. Do not claim the outage increased calls; no data is published.","engineering":"Engineering framing: Sunny's removal took out three channels at once, showing how tightly a vendor-hosted assistant can bind web chat, SMS and WhatsApp. Integration design should keep knowledge content, intake forms and service-request routing in city-owned systems so channels can be swapped. Prerequisites are exportable content and conversation data. Constraints include vendor-owned phone numbers and messaging accounts. Proof of value is a tested failover path and documented data export, not chatbot features.","delivery":"Delivery framing: an AI front door needs a contingency runbook like any critical service. Denver 311 now carries displaced demand during weekday hours while the city explores restoration. Acceptance criteria below are proposals: a documented fallback for each channel, call-volume monitoring after any channel loss, and data-return terms on exit. Brief councils on continuity risk before contract renewals, and communicate channel changes clearly to residents, including multilingual users."},"roleDetails":{"sales":{"customerProblem":"A resident-facing AI chatbot can disappear overnight when its contract lapses, shifting demand to limited-hours phone service.","stakeholders":["311 director","Technology Services","City council committee","Mayor's office"],"discoveryQuestions":["What is the fallback if the chatbot contract lapses?","Who owns the phone numbers, content and conversation data?","How will call-volume impact be measured?"],"valueHypothesis":"Continuity planning can limit service disruption from AI channel loss; benefit is risk reduction, not savings.","potentialEngagement":"A chatbot continuity and exit-plan review covering contract, data and channel fallback.","unsupportedClaims":["That the outage caused a measured call increase","Reason for unavailability beyond archived reporting","Any resident harm"]},"engineering":{"fit":"Fits cities running vendor-hosted AI assistants across web, SMS or messaging apps.","architectureIntegration":"Assistant fronting 311 knowledge and issue reporting across web, text and WhatsApp; fallback to search, forms and phone.","prerequisites":["City-owned knowledge base","Exportable conversation data","Independent service-request intake"],"constraints":["Vendor-owned messaging numbers","Contract approval timelines","No after-hours human channel"],"security":"Clarify retention and deletion of chatbot conversation logs and messaging records when service ends.","proofOfValue":["Failover test per channel","Data export completeness check","Call and wait-time monitoring after channel loss"]},"delivery":{"work":"Maintain resident service while a chatbot channel is down and plan restoration or replacement.","dependencies":["311 staffing","Online reporting system","Contract approval"],"ownership":"Denver 311 with Technology Services.","skillsAdoption":"Prepare agents and web content for displaced chatbot questions, including multilingual callers.","governanceCheckpoints":["Contract renewal timeline review","Exit and data-return terms","Resident communication on channel changes"],"acceptanceCriteria":["Fallback documented for every channel","Call and wait times reported weekly during outage","Data returned or deleted per contract"],"risks":["Longer 311 waits","Loss of multilingual after-hours access","Rushed replacement procurement"]}},"retrievedAt":"2026-11-09T22:09:06-06:00","enrichedAt":"2026-11-09T22:15:04-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Loss of after-hours and multilingual chat (archived reporting cited 72 languages) shifts demand to weekday phone hours; TTY relay listed as a remaining channel.","procurementImplications":"Illustrates contract-lapse risk when an AI service extension is brought late and rejected; city had budgeted funds but no approved contract.","operatingModelImplications":"311 must absorb displaced chatbot demand during business hours; the city earlier planned three additional 311 agents by next summer (archived).","sourceVerification":{"openedUrl":"https://www.denvergov.org/Sunny","referenceExcerpt":"Beginning November 5, Sunny, the City and County of Denver's chatbot, is currently unavailable","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}