From the Citizen Engagement & Services edition of November 1, 2026
MIT study of 1 million+ Boston 311 cases: integrating app, phone and web channels sped resolution but favored higher-income neighborhoods
MIT Sloan School of Management (Catherine Tucker, Shuyi Yu, Yifei Wang); City of Boston 311 · 311 and constituent service requests · Boston, Massachusetts, United States
- Publisher
- Route Fifty
- Original publication
- 2026-10-30
- Source retrieved
- 2026-11-02
What happened
Route Fifty reports on an MIT study, published in Information Systems Research, of more than 1 million Boston 311 records from 2011 to 2019 combined with census data. After Boston integrated its app, phone and web channels in 2015, average resolution times fell from roughly one to 2.5 days to about half a day to 1.5 days. Higher-income neighborhoods used the app to file clustered enforcement complaints and got faster resolution, so neighborhood outcomes became less equal. MIT's press release adds that app reports rose from 31 to 245 a day and app resolution time fell about 9.5%. The authors saw similar patterns in other cities' 311 data and recommend equity-aware routing and filters for clustered or duplicate complaints.
Why it matters
Cities adding AI chatbots and automated routing to 311 build on the same channel and routing logic. This study shows efficiency gains can widen service gaps unless routing and prioritization rules account for neighborhood equity.
Evidence and measured results
Peer-reviewed econometric study of administrative records over nine years, reported by Route Fifty with author interviews; MIT's press release was also opened. The paper itself was not opened. Data end in 2019, before AI tools, and the AI concerns are the author's commentary.
Limitations and uncertainty
Pre-2020 data; Boston-specific integration; correlational design despite the policy change; AI implications are the author's view, not tested.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 311 modernization and AI routing can speed average service while widening gaps between neighborhoods.
- Stakeholders
- 311 director
- Equity or civil rights office
- Code enforcement leadership
- Data and analytics team
- Discovery questions
- Do you report 311 resolution times by neighborhood and channel?
- How do routing rules treat clustered complaints?
- Which residents rely on phone instead of the app?
- Value hypothesis
- An equity baseline and routing review can keep service gains from widening gaps; no specific improvement is guaranteed.
- Potential engagement
- A 311 equity baseline and routing-rule review ahead of AI or chatbot deployment.
- Unsupported claims
- That AI routing causes inequity
- That results apply unchanged after 2019
- Any vendor product performance
Pre-sales engineering
Role takeaway
- Fit
- Fits cities with omnichannel 311 platforms planning AI intake or routing.
- Architecture and integration
- Join 311 case data with census tracts to monitor resolution times; add cluster and duplicate detection to routing.
- Prerequisites
- Geocoded 311 case data
- Census or neighborhood boundaries
- Documented routing rules
- Constraints
- Study data end in 2019
- Boston-specific integration
- Complaint types vary by city
- Security
- Publish only aggregates and protect complainant identity, especially for neighbor complaints.
- Proof of value
- Compare resolution time by income band before and after automation
- Measure the share of cases from repeat clustered submitters
Delivery
Role takeaway
- Work
- Add equity metrics and routing safeguards to 311 operations.
- Dependencies
- Clean location data
- Analytics capacity
- Department agreement on prioritization
- Ownership
- 311 director with departmental service owners.
- Skills and adoption
- Supervisors need to read equity dashboards and adjust allocation.
- Governance checkpoints
- Baseline equity report
- Quarterly routing rule review
- Pre-launch review of AI routing
- Acceptance criteria
- Proposed: resolution-time gap between income bands reported quarterly
- Proposed: gap does not widen after automation
- Risks
- Optimizing averages only
- Neglecting phone channel
- Misreading correlation as cause
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?
Merging channels into one case stream changes routing; prioritization logic should weight neighborhood need and detect clustered or duplicate complaints.
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies should monitor 311 resolution times by neighborhood income and channel, and review routing rules before adding AI optimization.
Security and privacy
What data, permissions and controls need testing?
Equity monitoring needs location data joined to census data; publish aggregates and protect complainant identities, especially for complaints against neighbors.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
App-first channels favor residents with digital access; phone and in-person channels still serve residents with less access.
Procurement
What should contracts, pricing and exit terms secure?
311 and AI routing purchases should require equity reporting by neighborhood and channel.
Operating model
Which teams own the service once it runs?
Inspection capacity allocated by complaint volume rewards heavy app users; capacity rules may need need-based adjustment.
Publication history
Read preserved resource versions (JSON)Stable resource ID: route-fifty-mit-boston-311-omnichannel-speed-equity-tradeoff-20261030