{"resourceId":"denver-311-citibot-voicebot-amendment-20261001","versions":[{"version":"external-5963d67abb0024193dd336b633c3d88294d3d1269ad550a80278b7b60082a239","resource":{"id":"denver-311-citibot-voicebot-amendment-20261001","title":"Denver advances Citibot contract amendment for optional 311 AI voicebot amid multi-year deal scrutiny","organization":"City and County of Denver / Hoodline","sector":"Municipal 311 / resident experience","geography":"Denver, Colorado, United States","publishedAt":"October 1, 2026","publicationDate":"2026-10-01","eventDate":"2026-09-22","sourceName":"Hoodline","sourceLabel":"Independent local reporting","sourceUrl":"https://hoodline.com/2026/10/denver-311-callers-may-have-to-talk-to-an-ai-bot-before-reaching-a-human/","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["accessibility-workforce","governance-procurement","operating-model","knowledge-work"],"finding":"Hoodline’s Oct. 1, 2026 report says a Technology Services amendment before Denver City Council would add $3,889,784.94 to the Citibot Inc. agreement (total $4,339,784.94) and extend service through Oct. 1, 2031, enabling an optional 311 AI voicebot purchasable later by written notice. Voice service is priced about $550,000/year for 1 million minutes (~$2.9M of the add-on over five years); Denver’s request form estimates ~$2M/year savings. The bot would identify as a bot, answer from Denvergov.org and city-provided material without wider internet access, transfer immediately on human/live agent/person, and redirect 911 callers. A Community Planning and Development call-center proof of concept is planned for 2026; citywide voice launch targeted for 2027 without full funding secured. Existing Sunny chatbot is cited at 80–95% satisfaction. Governance & Intergovernmental Relations Committee passed the item by consent Sept. 22, 2026; full Council had not voted as of the article, amid skepticism of long multi-year vendor deals.","sledRelevance":"Concrete large-city 311 voice automation procurement with dollars, phased POC, human-escape design, and council process—core local-government resident-services AI, distinct from public-safety dispatch.","evidence":"Cites Denver Legistar contract figures, 9News reporting on Dunwoody comments and pricing, CBS on prior 311 hour reductions, and vendor/city claims on Sunny satisfaction and possible call deflection. Full Council vote and measured voicebot outcomes are not yet available.","architectureImplications":"Voicebot as optional add-on to existing Citibot channel; closed knowledge base from Denvergov.org; queue-specific POC (CPD) before citywide; immediate human transfer intents; separate from 911.","governanceImplications":"Committee consent is not final authorization; five-year extension structure may face the same multi-year contract scrutiny Denver applied to other vendors. Cities should separate optional voice SKUs, funding gates, and published deflection/savings metrics before citywide mandates.","securityPrivacyImplications":"City says it does not collect/retain caller demographics beyond name, address, and contact details; knowledge base constrained to city-provided material. Still requires vendor DPAs, call recording/retention rules, and clear 911 handoff messaging.","caveats":"Amendment not yet approved by full Council. Savings (~$2M/year) and vendor ~65% deflection averages are projections. Sunny satisfaction is city/vendor-reported. Follows separate Feb 2026 ComplyAI/CivCheck permitting contract—do not conflate outcomes.","streamIds":["local-government"],"roles":{"sales":"Resident-experience and 311 leaders want after-hours deflection without trapping callers who need a person. Denver’s pending Citibot amendment puts a priced voicebot option (~$550k/year per 1M minutes; ~$3.89M five-year add-on) on the Council docket with a 2026 CPD proof of concept and 2027 citywide ambition. Use discovery on current hold times, after-hours volume, and human-escape requirements. Do not sell the city’s ~$2M savings estimate as proven—Hoodline reports it as a request-form projection before go-live.","engineering":"Fit is closed-knowledge-base voice deflection in front of live 311/agency queues, with hard intents to human agents and no 911 handling. Integrate city website content feeds, queue routing to CPD then other agencies, and audit logs for bot resolutions vs transfers. Prerequisites: content freshness pipeline, telephony integration, and funding for minutes tiers. Constraints: Council procurement politics on five-year terms, incomplete citywide funding, and digitally hesitant callers. Prove value with containment rate, transfer latency, and CSAT—not vendor national averages alone.","delivery":"Delivery work should sequence committee and full Council approval, a Community Planning and Development proof of concept, content operations for Denvergov.org answers, and agent training on supervised takeover before any 2027 citywide funding ask. Dependencies include Technology Services, 311 operations, City Council, and Citibot. Ownership sits with resident-experience/Technology Services alongside agency queue owners. Risks include multi-year contract backlash, over-automation of complex permitting calls in the POC queues, and accessibility gaps if voice becomes a mandatory first hop without an easy, tested human escape."},"roleDetails":{"sales":{"customerProblem":"311 and agency call centers face volume, after-hours demand, and pressure to expand self-service without abandoning callers who need humans.","stakeholders":["Director of resident experience","CIO/Technology Services","311 operations manager","City Council","Agency call-center leads (e.g., CPD)"],"discoveryQuestions":["What share of inbound 311 calls are informational vs service-ticket creating?","Is voice an optional add-on or mandatory first hop?","What human-escape phrases and transfer SLAs are required?","How will Council evaluate five-year vendor terms and savings claims?"],"valueHypothesis":"A grounded 311 voicebot can deflect routine informational calls if human transfer is immediate and POC metrics beat baseline hold/handle times—savings remain unproven until after POC.","potentialEngagement":"Eight-week 311 voice readiness: baseline call taxonomy, content coverage map, POC success criteria, and Council briefing pack on contract term/risks.","unsupportedClaims":["Guaranteed $2M annual savings","65% deflection as Denver-specific fact","That full Council approval or 2027 citywide funding is secured"]},"engineering":{"fit":"Informational 311 deflection with closed corpus; poor fit for emergency or complex adjudication without human handoff.","architectureIntegration":"Telephony → voicebot NLU → Denvergov.org knowledge base → resolve or transfer to agency queue; separate 911 redirect message.","prerequisites":["Curated city website knowledge base","Queue routing for CPD POC","Human-escape intent library","Call logging/retention policy"],"constraints":["Pending Council authorization","Minutes-based pricing tiers","Incomplete citywide funding","Caller digital confidence variation"],"security":"Limit bot to city-provided content; minimize retained caller data; enforce vendor access controls and 911 non-handling.","proofOfValue":["Containment rate on CPD POC queues","Median time-to-human when requested","CSAT bot vs agent","Wrong-answer / escalation incident rate"]},"delivery":{"work":"Secure Council approval, configure voice POC on CPD queues, train agents on takeover, publish resident notice, evaluate citywide funding.","dependencies":["City Council vote","Citibot configuration","311/CPD staffing","Website content owners"],"ownership":"Technology Services / resident experience owns the channel; agencies own queue-specific answers.","skillsAdoption":"Agents learn supervised takeover; content owners keep Denvergov.org answers current.","governanceCheckpoints":["Council contract approval","POC exit criteria before expansion","Accessibility review of mandatory-bot risk","Annual savings/deflection public report"],"acceptanceCriteria":["Bot self-identifies and honors human-escape intents","911 redirect message tested","POC metrics vs baseline documented","Optional purchase notice process defined"],"risks":["Council rejects multi-year structure","Callers trapped before human agents","Savings narrative outruns measured results"]}},"retrievedAt":"2026-10-01T22:18:34-05:00","enrichedAt":"2026-10-01T22:22:00-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Voicebot may help less web-literate callers but risks blocking people who struggle with automated voice; immediate human-escape and agent jobs redesign are essential. Prior 311 hour reductions already shifted load to Sunny.","procurementImplications":"Optional voice add-on via written notice avoids a second RFP but concentrates spend in a five-year amendment; Council may demand stronger justification versus shorter competitive terms.","operatingModelImplications":"Positions AI voice as first-line informational deflection with live agents for exceptions; requires content ops and queue-owner accountability beyond the vendor contract.","sourceVerification":{"openedUrl":"https://hoodline.com/2026/10/denver-311-callers-may-have-to-talk-to-an-ai-bot-before-reaching-a-human/","referenceExcerpt":"A contract amendment now before Denver City Council would add an AI voicebot to the city's 311 call line","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}