From the Citizen Engagement & Services edition of November 9, 2026
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
City and County of Denver · Municipal 311 chatbot and constituent services · Denver, Colorado, United States
- Publisher
- City and County of Denver (denvergov.org status page)
- Original publication
- Undated city status page (states unavailability beginning Nov. 5, 2026)
- Source retrieved
- 2026-11-10
- Event date
- 2026-11-05
What happened
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.
Why it matters
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 and measured results
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.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-09; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- Continuity planning can limit service disruption from AI channel loss; benefit is risk reduction, not savings.
- Potential engagement
- A chatbot continuity and exit-plan review covering contract, data and channel fallback.
- Unsupported claims
- That the outage caused a measured call increase
- Reason for unavailability beyond archived reporting
- Any resident harm
Pre-sales engineering
Role takeaway
- Fit
- Fits cities running vendor-hosted AI assistants across web, SMS or messaging apps.
- Architecture and integration
- 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.
- Proof of value
- Failover test per channel
- Data export completeness check
- Call and wait-time monitoring after channel loss
Delivery
Role takeaway
- 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.
- Skills and adoption
- Prepare agents and web content for displaced chatbot questions, including multilingual callers.
- Governance checkpoints
- Contract renewal timeline review
- Exit and data-return terms
- Resident communication on channel changes
- Acceptance criteria
- 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
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?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
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.
Security and privacy
What data, permissions and controls need testing?
The notice does not say what happens to stored Sunny conversation data or WhatsApp/SMS records after service ends.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
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.
Procurement
What should contracts, pricing and exit terms secure?
Illustrates contract-lapse risk when an AI service extension is brought late and rejected; city had budgeted funds but no approved contract.
Operating model
Which teams own the service once it runs?
311 must absorb displaced chatbot demand during business hours; the city earlier planned three additional 311 agents by next summer (archived).
Publication history
Read preserved resource versions (JSON)Stable resource ID: denver-sunny-chatbot-offline-since-nov5-city-status-notice-20261105