From the Citizen Engagement & Services edition of November 7, 2026
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
City of Minneapolis 311 Service Center · Municipal 311 and constituent services · Minneapolis, Minnesota, United States
- Publisher
- City of Minneapolis (news release)
- Original publication
- 2026-11-05
- Source retrieved
- 2026-11-08
- Event date
- 2026-11-05
What happened
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.
Why it matters
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 and measured results
City press release (self-reported launch announcement, not an evaluation); volume figures are city-reported totals without channel mix or resolution-time data.
Limitations and uncertainty
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).
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- Self-service tracking and the Explore Map may reduce status calls and duplicate reports; unproven until post-launch data is published.
- Potential engagement
- A 90-day post-launch channel-shift and status-call baseline compared with 2025 volumes.
- Unsupported claims
- Call deflection or cost savings
- Resident satisfaction improvement
- Accessibility conformance of the new portal
Pre-sales engineering
Role takeaway
- Fit
- Fits large cities replacing a 311 CRM and public portal while keeping legacy channels.
- Architecture and integration
- 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.
- Proof of value
- Self-service share of new requests
- Duplicate-report rate after Explore Map
- Status-check call volume vs 2025
Delivery
Role takeaway
- 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.
- Skills and adoption
- Community help sessions plus staff training on knowledge-base upkeep and status updates.
- Governance checkpoints
- Map privacy review per case type
- Accessibility review before declaring migration complete
- Quarterly public metrics
- Acceptance criteria
- 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
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?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
Public map of open requests creates confidentiality decisions about which case types are shown; the release is silent on how those are governed.
Security and privacy
What data, permissions and controls need testing?
Optional resident accounts and notification preferences add personal data to the 311 platform; the release does not describe privacy notices or retention.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
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.
Procurement
What should contracts, pricing and exit terms secure?
CRM replacement and app publication imply a platform contract, not described in the release.
Operating model
Which teams own the service once it runs?
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.
Publication history
Read preserved resource versions (JSON)Stable resource ID: minneapolis-311-new-portal-app-knowledge-base-launch-20261105