How Salt Lake City automates resident service requests, work order routing, and inter-department coordination
Salt Lake City is the capital of Utah, serving over 200,000 residents across streets, parks, utilities, public safety, and community services. Behind every pothole reported and every permit applied for sits a workflow stack that turns a resident request into a routed work order, a routed work order into a completed job, and a completed job into a public-facing record.
Running a city is running hundreds of overlapping services for residents who do not care which department owns what. A resident reports a pothole — they do not care that the fix involves Streets, Engineering, and 311. To make city government feel responsive, the request has to land in one place, route to the right department automatically, get done on a known SLA, and close out with the resident notified. Salt Lake City automates that loop so the resident experience matches the budget being spent on it.
The four pain points Salt Lake City's automation has to solve
Requests come in through too many channels. 311 calls, website forms, mobile app, walk-ins at the front counter, social media tags. Without one intake, a complaint about the same pothole can sit in five inboxes.
Routing to the right department is harder than it looks. Pothole on a state highway? Different owner than a city street. Tree down on private property versus right-of-way? Different rules. Misrouted tickets die slowly.
Inter-department work has no shared timeline. A water-line repair needs Utilities to dig, Streets to repave, and Permits to close. If those teams work off three systems, the job is done in fits and starts.
Transparency requires public-facing data, not just internal data. Residents want to know what their report did. Without a public dashboard that shows request volumes, SLAs, and resolutions, 'the city is working on it' sounds like a brush-off.
Four automation patterns that keep Salt Lake City moving
One intake for every channel
311 calls, website forms, mobile app, walk-ins, and social media tags all funnel into one ticketing system — deduped, geo-tagged, and classified before any department sees them.
Rules-based department routing
Tickets route automatically based on location, asset type, and ownership. State highway vs city street vs private property — the right team gets the right ticket the first time.
Cross-department work order coordination
Jobs that touch multiple departments live on one timeline with explicit handoffs. The water repair, the repave, and the permit closure all show up against the same address.
Public-facing transparency dashboards
Request volumes, SLAs, and resolutions publish to a public dashboard. Residents see what was reported, what was done, and how long it took — by neighbourhood and by category.
The four-stage pipeline
Every resident request in Salt Lake City runs through the same four-stage shape — intake from any channel, route to the owning department, resolve with cross-team coordination, report back publicly. The same pipeline serves a single pothole report and a snow-storm worth of service calls.
Case study: Salt Lake City
Salt Lake City
Challenge
Run a responsive city government across hundreds of services and many departments, with residents who do not care which org chart owns what — and do it on a public budget that does not allow each department to buy its own systems.
Solution
Salt Lake City built a service pipeline where intake is unified across channels, routing is rules-based by location and ownership, cross-department work shares one timeline, and a public dashboard closes the loop with residents. The city feels responsive because the workflow is responsive.
More from Government & Education
Minneapolis — public-sector service requests → Udacity — online tech education → Habitat for Humanity — global housing nonprofit →Frequently asked questions
How does Salt Lake City handle resident service requests?
Reports from 311 calls, the website, the mobile app, walk-ins, and social media all land in one ticketing system. Tickets are deduped, geo-tagged, and classified automatically before any department sees them — so residents do not have to know which channel is the right one.
How does Salt Lake City route work to the right department?
Routing is rules-based by location, asset type, and ownership. A pothole on a state highway, a city street, or private property all route to the correct owner the first time, rather than bouncing between departments.
How does Salt Lake City keep residents informed?
Request volumes, SLAs, and resolution times publish to a public dashboard broken out by neighbourhood and category. Residents can see what was reported, what was done, and how long it took — without filing a records request.
Run your city the same way
Byteflow gives you the workflow shape — intake, route, resolve, report — so residents feel a responsive city and your departments share one timeline.
Start automating →Easy automation. For everyone.