arosplatforms™AI consultancy
ar
← All articles

311 Ticket Triage: How Cities Sort, Route and Resolve Requests

311 Ticket Triage: How Cities Sort, Route and Resolve Requests

Hand-drawn civic request triage title card

311 ticket triage is the step where each new service request gets a category, a priority and one owner, so a downed power line is not stuck behind a missed trash pickup. Done well, it is the difference between a city that closes requests quickly and one that bounces them between departments. This guide walks through how US cities do it, where it breaks, and how to build triage that automation can run. We build custom AI systems for government teams, and the case we make below is simple: triage is a rules problem your city already knows how to write down, which makes it a strong place to start with AI.

Arosplatforms
Route City Requests More Consistently
Arosplatforms builds custom AI systems for government teams, helping municipalities modernize records and citizen requests.
Visit

TL;DR

  • Triage means three decisions per request: what it is (category), how urgent it is (priority), and who owns it (routing).
  • Los Angeles found that more than 40% of 311 calls had to be triaged and transferred to other departments, so routing quality drives call volume.
  • Duplicates and manual routing are the known bottlenecks: Philadelphia’s 2025 RFI responses say both are still handled by hand.
  • Written priority rules, service level agreements and a review of reroutes keep triage honest over time.
  • Rules-based triage is a good fit for AI agents that classify, deduplicate and route, with staff handling the exceptions.

Table of Contents

What ticket triage means for a 311 service

Ticket triage is reviewing each new ticket to decide what it is about, how urgent it is, and who should handle it. The term comes from medical triage, where nurses sort patients by urgency. In a help desk, a network outage affecting many users needs fast action while one user’s slow-loading complaint can wait.

In a 311 setting the same logic applies to residents. A request arrives by phone, app, web form or email. Someone or something has to answer four questions:

  1. Is this a request for action, or just a question 311 can answer itself?
  2. Is it a duplicate of something already open?
  3. Is anyone at risk?
  4. Which crew or department owns the fix?

In Orange County, Florida, an NSF-published study of 489,061 requests across 370 service categories found that each category ties to a specific agency, and information-seeking requests are usually handled directly by 311 operators without being forwarded. That is the first triage cut: answer it now, or send it on.

Step 1: Intake that captures what triage needs

Triage is only as good as the information collected at the door. Chicago’s 311 intake form standardizes caller and request information and prompts operators to ask problem-specific questions before the request is processed. The principle holds for every channel: required fields should depend on the category.

What to capture:

Where it goes wrong: free-text-only forms. Staff then spend triage time rereading and guessing the category instead of deciding.

Step 2: Categorize from a fixed list

A fixed category list is what makes routing automatic. Los Angeles offers over 60 service types through 311, and requests entered in its CRM are forwarded automatically to the right department. Orange County’s 370 categories show the other end of the range.

Two practical rules:

Step 3: Set priority by risk and impact

Priority should come from impact and urgency, not from how loudly someone writes. The Orange County study describes three levels, Critical, Important and Routine, set by the responding agency together with 311 management.

A workable scheme:

Priority Test Examples
Critical Immediate risk to people or property Downed power line, sinkhole, water main break
Important Service loss or growing damage, no immediate danger Traffic signal out, repeated flooding
Routine Normal service levels Small pothole, missed collection, tall grass

The routine definition mirrors Lethbridge’s, whose 311 describes a standard request as one that poses no immediate risk to people or property. Lethbridge is in Canada, but the definition is a clean model for US teams.

Hazard rules can be coded. Administrator-set priority rules based on public-safety standards and local policy can flag a potential hazard for immediate review instead of leaving it in the routine queue. Keep a human in the loop for every Critical flag.

One caution from the Orange County data: higher-priority requests are not always resolved faster, because the service itself can be harder. Measure response time by priority and by who handled it, not as one average.

Step 4: Route to one owner and catch duplicates

Good routing ends with a single accountable owner. Chicago’s system routes each saved request to the right department, creates work orders, and assigns and dispatches crews. Tennessee’s municipal advisory service notes that most commercial packages auto-assign the department and prioritize with a code, and that the department must be accountable to someone in city hall for follow-up.

Duplicates are the quiet cost. Ten residents reporting the same pothole should produce one work order and ten updates. Two approaches work:

Matching on location, category and time window is a classic job for automation. A model can propose “likely duplicate of ticket X” and a staff member confirms in one click. Work-order logic is similar in other fields, and our guide to work order prioritization shows how maintenance teams rank jobs.

Field handoff matters too. A real-estate or inspection workflow, such as the intake-to-crew flow described in this guide to inspection request tools, follows the same pattern: capture, assign, confirm, close with evidence.

Step 5: Close the loop with the resident

A request is not done when the crew leaves. San Francisco uses before and after pictures to document closure. Feezza’s analysis adds that the message residents remember is the last one: saying what was done, when and who owns it builds more trust than a bare “closed” status.

Worker documenting a completed pothole repair

Drafting that plain-language closing note from the work-order record is a task an AI assistant does well, with staff approving templates once rather than every message.

Step 6: Track service levels and review the triage itself

Triage needs numbers behind it. In San Antonio, partner departments adopted service level agreements (SLAs) for each service, such as fixing potholes within 48 hours, with departments expected to meet them at least 90% of the time. SLAs can be extended during events like severe storms, and city management reviews a department that keeps missing them.

San Francisco Public Works sets a 48-hour SLA for most street cleaning requests and tracks volume and response time by month, shift and work zone.

Review the triage as well as the crews. Tidio’s process ends with checking whether category, priority and first-time routing were right. Track:

  • Share of requests rerouted after first assignment
  • Duplicate rate by category
  • Time from intake to assignment
  • SLA attainment by priority

Plan for surges as well. After Orange County’s March 2020 emergency declaration, total 311 volume rose 66.5% and the system’s emergency mode raised capacity. Triage rules that can switch modes are worth writing before the storm.

Where AI fits in 311 triage

The steps above are rules plus judgment. AI handles the rules at volume and surfaces the judgment calls:

Triage task What automation does Who stays in charge
Categorize Reads text and photos, proposes a category Staff set the category list
Prioritize Applies hazard rules, flags Critical items Staff review every Critical flag
Deduplicate Matches location, type and time Staff confirm merges
Route Sends to the owning crew and creates the work order Department leads own the routing table
Respond Drafts status and closing messages Staff approve templates

Our AI Agents & Automation for government work follows this shape, and AI workflow automation explains the underlying idea. For the intake side, see our AI customer support agent, and for crew assignment, AI dispatch optimization.

Our perspective

Most 311 delays we would expect to find are not in the field. They sit between departments, in the gap between a request being logged and someone owning it. That is why we start with the routing table and the priority rules, not with a model.

Our approach is to embed with the team, map the real request flow, and build the system on your data with weekly demos so progress is visible. We design for ownership: your staff manage the system, with no vendor lock-in.

A municipality does not need to automate everything at once. Begin with one high-volume category, such as the most-transferred call types, prove the time saved, then extend.

arosplatforms team

Getting started

If you run a city, county or department that handles resident requests, the first move is a scoping exercise: list your categories, priorities and routing rules, and find where tickets get reassigned. Our AI strategy and advisory for government covers readiness assessment and roadmap, and custom AI development for government takes a scoped proof of concept through to a production system. You can also start from the services overview.

FAQ

What is ticket triage?

Ticket triage is reviewing each incoming ticket to assign a category, a priority and an owner. The goal is that urgent problems are handled first and routine ones do not clog the queue.

How do 311 teams decide what is urgent?

They use written priority levels set with the responding agency, for example Critical, Important and Routine. Hazards such as a downed power line or sinkhole are flagged for immediate review rather than waiting in the routine queue.

How are duplicate 311 requests handled?

Cities use location-based matching, public maps of open tickets, or staff review. The aim is one work order per problem, with every reporter kept informed.

Can AI do 311 triage?

AI can propose categories, flag likely hazards, match duplicates and draft resident updates. Staff keep ownership of the category list, routing table and every high-risk decision.

Sources