Potholes Go to the Cheap Model. A Basement Full of Sewage Wakes the On-Call Operator. Who Draws That Line?

How many of the service requests your office took last year actually needed a superintendent to look at them?

Take a public works operation fielding 4,100 requests in a year. Potholes after the March freeze-thaw. Streetlight out. Missed collection. Dead deer on the shoulder. Basketball hoop in the right-of-way. Plow damage to a mailbox. Sidewalk trip hazard. Sewer smell in a basement. Rusty water on three houses in a row. Signal dark at a five-lane intersection.

Nine out of ten are a form, an address and a work order. One in ten is a decision a licensed operator or a superintendent has to make against a clock, sometimes a regulatory one. The problem is that all 4,100 land in the same place, at the same speed, in front of the same clerk — and the one that matters gets the same three minutes as the mailbox.

What counts as routine on a streets and utilities line?

Routine has a specific meaning here, and it is not "easy." A routine request is one where the information needed to open a correct work order is complete, unambiguous, and asks nobody to judge risk. Pothole at 412 Warren, southbound lane, about the size of a dinner plate: routine. It goes into Cityworks or Cartegraph or Lucity as a street maintenance request against the right asset, and the crew leader picks it up on his tablet in the morning.

A hard case is one where the correct next step depends on something the caller did not say and would not know to say. Sewage in a structure is the clearest example: potentially a sanitary sewer overflow with a state reporting clock attached, a property damage claim, and a decision about whether to send a jet truck now or a camera first. Discolored water at more than one address on a block is another — a main break, hydrant flushing, or something needing a water quality sample before anybody says a word to a resident.

The definition worth taping to the wall: a request is routine when the only unknown is where and when; it becomes hard the moment the unknown is what is actually happening underground.

Why one setting for everything costs you twice

Operations that switched something on in 2025 usually made one of two mistakes. They ran everything through the biggest, most careful model, so every pothole report cost more than it should and the whole thing looked like an expensive way to type an address. Or they ran everything through the cheapest fast option, so a basement backup got a polite confirmation number and a Tuesday appointment — the failure mode that ends up in a claim file and a council meeting.

The 2026 answer is routing, and it stopped being a clever trick and became standard practice. Cisco built model routing into the personal assistant it is rolling out to roughly 90,000 employees, specifically to balance cost against capability, with an emphasis on running things on their own premises. The plain version: the fast, cheap model handles the volume; only the genuinely hard requests get escalated to the strong one, and some get escalated straight past both to a human pager.

flowchart TD
  A["Resident reports a problem by phone or web"] --> B["Fast model takes the address and asks two screening questions"]
  B --> C["Lane 1: pothole, streetlight, missed pickup, dead animal"]
  B --> D["Lane 2: water quality or pressure at 2+ addresses"]
  B --> E["Lane 3: sewage in a structure, dark signal, downed wire"]
  C --> F["Work order created against the asset, crew picks it up at 6:30am"]
  D --> G["Strong model checks recent breaks, valve work and flushing history"]
  G --> H["Distribution foreman gets a one-page brief with addresses mapped"]
  E --> I["On-call operator paged immediately, no summarizing step"]

Who actually draws the line, and how often they redraw it

Not the software vendor. Not the IT director. The line is drawn by the person who carries the consequence: the streets superintendent for surface work, the licensed water or wastewater superintendent for anything below grade. The escalation rules are an operational risk policy written in different words, and the person who signs the state overflow report should be the person who decided what triggers a page.

Write it as a table, not a paragraph. Three columns: what the caller says, which lane it goes to, and what happens within how many minutes. Print it and put it in the same binder as the after-hours call-out list. Review it monthly for the first quarter and quarterly after that, because the boundaries move with the season.

The seasonal part is not optional. In March, "the road is falling apart" is a pothole and belongs in lane one, and you will get 300 of them in six weeks. In late January the same sentence from the same street might be a frost heave over a service line, which is a different lane. During spring hydrant flushing, discolored water is expected and should not wake anybody — unless the address is nowhere near that week's flushing route, which is exactly the check the strong model is worth paying for.

The March pothole surge, run both ways

Take a two-week stretch after the first hard thaw. The office takes 340 requests in ten working days. Under the old arrangement the service request coordinator keys each one, and because she is behind, the two that matter sit in the same queue as the other 338 for most of a day.

Routed, the fast lane opens 290 street maintenance work orders directly against the correct asset, with the location pinned and the resident's photo attached, sorted for the crew leader by route rather than by arrival order. The coordinator reads a summary at 8am instead of typing it.

Thirty-eight go to the strong lane because they were ambiguous — "the road is sinking" near a sewer main is not a pothole, and settlement over a utility cut is a different work order and a different crew. Twelve go straight to a person: three sewage reports, two dark signal calls, one gas odor transferred to the gas utility inside thirty seconds, and six from a resident who has now called three times about the same thing, which is its own escalation rule and one of the most valuable ones you can write.

The arithmetic, and the part that is not about the software bill

Assumptions, illustrative: 4,100 requests a year, 78% clearly routine. At 2026 prices a short intake conversation on a fast model costs a couple of cents; the same conversation on a top-end model with a records check costs closer to fifteen. Frontier AI pricing is down roughly tenfold from 2025, which is why this arithmetic looks the way it does.

Four hundred dollars. That is the entire software saving, and any vendor building a business case on it is wasting your afternoon. The money is elsewhere. At six minutes of clerk time per routine request, 3,198 requests is 320 hours a year; at $30 an hour fully loaded that is $9,600 of coordinator time, most of it going back into the counter, the 811 locate tickets and the permit inbox. The number with no dollar figure is the twelve calls a year that reach the on-call operator in four minutes instead of four hours.

The four calls that must never sit in the cheap lane

Write these as absolute rules, with no summarizing step in between, because a summary is a delay dressed up as efficiency.

Sewage in a structure. Straight to the on-call operator. The reporting clock for an overflow in most states starts when the utility knows, and "the software knew at 9pm" is not a defense you want to test.

A dark or flashing signal at a major intersection. Under the MUTCD a dark signal is treated as an all-way stop and needs law enforcement notified and a signal technician rolling. That is a phone call, not a work order.

Any gas odor, downed conductor, or person in a trench or vault. Transferred out immediately. Your operation is not the responder for two of those three, and delay is the whole risk.

The third call from the same address about the same problem. Not because it is dangerous, but because three calls means the first two were handled wrong, and that is the one pattern automation will repeat forever if nobody writes the rule.

Keep a human reading the routine lane's daily summary for the first three months, then a monthly sample audit — pull twenty closed routine requests and check the lane assignment was right. The Monday-sized first step is smaller: print last year's request categories by volume and mark each one routine or hard with a pen. If your superintendent and your coordinator disagree on more than five categories, that disagreement is the actual project.

Frequently asked questions

Does the resident know which lane they landed in?

They should not have to. Every lane gives them the same thing: confirmation that someone has it, a request number they can quote, and a realistic timeframe. What changes behind the curtain is who reads it and how fast. Avoid one thing — a cheerful automated promise of a timeframe on a request that just got escalated. The escalation should change the message the resident hears, not only the routing.

We already have a 311 system. Is this a replacement?

No. Cityworks, Cartegraph, Lucity, Accela and the rest are still where the work order lives. What routing changes is what happens between the resident speaking and a correct record existing in that system, which today is a person typing. The test of whether it works is whether the records in your work order system got cleaner, not whether something new appeared on a screen.

What happens when the fast lane gets one wrong?

It will, so decide in advance which direction the errors should fall. Set the rules so ambiguity escalates rather than settles: an unclear water complaint goes up, an unclear pothole stays down. You will pay for some unnecessary escalations. That is the correct price, and far cheaper than the one wrong call that goes the other way.

CallSphere builds AI voice and chat agents that answer business phone lines and web chat, book appointments and capture leads around the clock. In this picture it sits at the front door — the line that answers when the resident calls at 8:40pm, takes the address and the two screening questions, and routes the call according to the table your superintendent wrote, rather than sending everything to the same voicemail box.