{"resourceId":"minneapolis-311-new-portal-app-knowledge-base-launch-20261105","versions":[{"version":"external-ae26d19f5f894fa99143258810f267f3ab85245f7f5f6fa06273fcd6e3065c44","resource":{"id":"minneapolis-311-new-portal-app-knowledge-base-launch-20261105","title":"Minneapolis launches new 311 portal, mobile app, Explore Map and public knowledge base as 311 marks 20 years; 2025 volume was 118,000+ requests plus 380,000 calls and emails","organization":"City of Minneapolis 311 Service Center","sector":"Municipal 311 and constituent services","geography":"Minneapolis, Minnesota, United States","publishedAt":"2026-11-05","publicationDate":"2026-11-05","eventDate":"2026-11-05","sourceName":"City of Minneapolis (news release)","sourceLabel":"Minneapolis launches new 311 system as department marks 20 years of committed service","sourceUrl":"https://www.minneapolismn.gov/news/2026/november/new-311-system/","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["operating-model","accessibility-workforce"],"finding":"On Nov. 5, 2026 the City of Minneapolis announced a new 311 system: an online portal and mobile app (now in the App Store and Google Play) with more reporting options, request tracking without calling, optional accounts with direct update notifications, an Explore Map of open requests so residents can see whether an issue is already reported, and a public knowledge base linked to request forms. Phone, email and other channels remain. The city reports 311 volume rising from 58,000+ service requests in 2006 to 118,000+ in 2025, plus 380,000 phone and email contacts. Community help sessions are scheduled Nov. 18, Dec. 2 and Dec. 9. The release does not mention AI, accessibility testing status, or outcome metrics for the new system.","sledRelevance":"A large U.S. city replacing its 311 CRM and digital front door, with published baseline volume, is directly in CE scope and gives a before-state against which self-service shift and call deflection can later be measured.","evidence":"City press release (self-reported launch announcement, not an evaluation); volume figures are city-reported totals without channel mix or resolution-time data.","architectureImplications":"New public portal and app on a replacement 311 CRM with knowledge base, account-based notifications and a public map of open cases; legacy phone/email intake retained alongside.","governanceImplications":"Public map of open requests creates confidentiality decisions about which case types are shown; the release is silent on how those are governed.","securityPrivacyImplications":"Optional resident accounts and notification preferences add personal data to the 311 platform; the release does not describe privacy notices or retention.","caveats":"Launch announcement only; no satisfaction, deflection, accuracy or accessibility-conformance data. The vendor and the portal's chat assistant are not named in the release (see the companion MACOPD resource).","streamIds":["citizen-engagement"],"roles":{"sales":"Sales framing: a city-scale 311 replatform with published volume is a measurable baseline, not a success story yet. Minneapolis reports 118,000+ requests and 380,000 calls and emails in 2025 and now offers tracking, notifications, a public map and a knowledge base. Discovery should ask what share of contacts are status checks, which channels residents actually use, and how success will be reported. A bounded engagement is a post-launch channel-shift and status-call baseline. Do not claim call deflection or satisfaction gains; the release reports none.","engineering":"Engineering framing: the new portal, app, knowledge base and Explore Map sit on a replacement 311 CRM while phone and email intake continue. Fit work is integration of department work queues, notification templates and map filters for confidential case types. Prerequisites include a maintained knowledge base and a channel-tagged reporting model. Proof of value should measure self-service share, duplicate-report reduction from the map, and status-call volume against the 2025 baseline, not launch features.","delivery":"Delivery framing: launch is the start of adoption work, not the end. Minneapolis 311 owns the portal, with departments responsible for request types and status updates that make tracking meaningful. The city's Nov. 18, Dec. 2 and Dec. 9 help sessions show in-person adoption support. Acceptance criteria below are proposals: status freshness, notification delivery and duplicate rates. Keep phone and in-person channels staffed while residents migrate, and publish results against the 2025 baseline."},"roleDetails":{"sales":{"customerProblem":"Rising 311 demand (118,000+ requests and 380,000 calls/emails in 2025) handled through channels where residents had to call for status updates.","stakeholders":["311 Service Center Director","Mayor's office","Department request owners","Residents and community groups"],"discoveryQuestions":["What share of 2025 calls and emails were status checks?","Which metrics will show the new portal is working?","How are department status updates kept current?"],"valueHypothesis":"Self-service tracking and the Explore Map may reduce status calls and duplicate reports; unproven until post-launch data is published.","potentialEngagement":"A 90-day post-launch channel-shift and status-call baseline compared with 2025 volumes.","unsupportedClaims":["Call deflection or cost savings","Resident satisfaction improvement","Accessibility conformance of the new portal"]},"engineering":{"fit":"Fits large cities replacing a 311 CRM and public portal while keeping legacy channels.","architectureIntegration":"Portal, app, knowledge base and public map on the replacement CRM, linked to request forms and account notifications.","prerequisites":["Curated knowledge base","Channel-tagged reporting","Department status-update discipline"],"constraints":["Release names no vendor or architecture","Confidential case types must be withheld from the map","App and web parity required"],"security":"Govern resident account data, notification preferences and what the public map exposes about addresses and case types.","proofOfValue":["Self-service share of new requests","Duplicate-report rate after Explore Map","Status-check call volume vs 2025"]},"delivery":{"work":"Drive adoption of the new portal and app while keeping phone, email and in-person intake working.","dependencies":["311 CRM platform","Department case owners","App store publication"],"ownership":"Minneapolis 311 Service Center.","skillsAdoption":"Community help sessions plus staff training on knowledge-base upkeep and status updates.","governanceCheckpoints":["Map privacy review per case type","Accessibility review before declaring migration complete","Quarterly public metrics"],"acceptanceCriteria":["Status updated within a defined window for most open cases","Notification delivery success measured","Year-over-year channel mix published"],"risks":["Residents unaware of new channel","Stale statuses erode trust","Launch claims outpace measured outcomes"]}},"retrievedAt":"2026-11-07T22:13:12-06:00","enrichedAt":"2026-11-07T22:18:01-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"City keeps phone, email and in-person channels and schedules in-person help sessions; the mayor frames the launch as making services more accessible, but no conformance status is stated.","procurementImplications":"CRM replacement and app publication imply a platform contract, not described in the release.","operatingModelImplications":"311 remains the city's non-emergency front door; the release reinforces 911-versus-311 guidance and positions self-service tracking to reduce status-check calls.","sourceVerification":{"openedUrl":"https://www.minneapolismn.gov/news/2026/november/new-311-system/","referenceExcerpt":"In 2025, there were more than 118,000 service requests submitted, and an additional 380,000 contacts which included phone calls and emails","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}