Your Permit Coordinator Opens Nine City Portals Before 8 a.m. An Agent Now Does That Clicking.

You tried this in 2024. Somebody sold your office a "bot" that logged into the city permit portal and pulled statuses. It worked for five weeks, until the county redesigned the page and moved the Schedule Inspection button, at which point it silently did nothing for eleven days and a crew tore off a roof with no permit on it. You paid to build it and paid again to stop using it. Reasonable people in this trade are done with that pitch.

Here is what is actually different in 2026, in one sentence, before any of the rest: the agent now looks at the screen and works out where the button went, the same way a new hire would, instead of following a script that breaks the moment a page changes.

Nine portals before eight in the morning

Count the logins in your permit coordinator's browser. A residential roofer working a metro area pulls permits in eight or ten municipalities, and every one runs a different system — Accela Citizen Access here, Tyler EnerGov there, eTRAKiT, iWorQ, CityView, and two towns that still want a PDF emailed to a clerk. No export. No combined view. No way to ask "which of my 34 open jobs has an issued permit" except by logging into nine systems and reading nine lists.

So that is what happens. Every morning, before the phones start, the permit coordinator goes portal to portal: check what got issued overnight, download the permit card into the job file, schedule the dry-in inspection for tomorrow's tear-offs before the jurisdiction's cutoff, and note the two applications that got kicked back for a missing product approval sheet or an expired contractor registration. Ninety minutes to two hours, five days a week, and the whole thing is a memory test.

Then there is the second set of portals: the carrier side. Xactanalysis, Alacrity, Symbility Connect — wherever your restoration assignments and supplements live, checked daily for status, again with no export. And the distributor portals for delivery confirmations, and the manufacturer's contractor portal where enhanced warranties get registered.

What the miss actually costs

The costs are not the ninety minutes. They are the three specific misses.

The inspection cutoff. Most jurisdictions want the dry-in or in-progress inspection requested by mid-afternoon the day before, or by seven in the morning same day. Miss it and a roof that got dried in yesterday sits until an inspector can be scheduled, the crew is on another job, and the final inspection slides a day or three — which slides the certificate of completion, which slides the invoice, which slides the final insurance payment and the mortgage company's release of the depreciation check.

The permit that was never issued. A crew shows up, tears off, and a code officer or a neighbour notices. Stop-work order, re-inspection fees, a very bad afternoon, and in some jurisdictions a mark against the contractor registration you need to keep working there.

The kicked-back application nobody read. It sat in a portal message centre for six days because that portal does not email. Your homeowner, meanwhile, has been told the install is Thursday.

Computer use — the ability for an AI agent to drive a screen the way a person does, logging in, clicking, reading and filing — matters most in trades like roofing that run on somebody else's web portal where no connection was ever built and no export exists.

flowchart TD
  A["6:30 a.m. - agent opens each city portal"] --> B["Reads permit status for tomorrow's tear-offs"]
  B --> C{"Permit issued?"}
  C -->|"No"| D["Flags the job red on the production board"]
  C -->|"Yes"| E["Requests the dry-in inspection before the cutoff"]
  E --> F{"Did the portal reject the request?"}
  F -->|"Yes"| G["Screenshot and reason to the permit coordinator"]
  F -->|"No"| H["Saves the permit card and inspection window to the job file"]
  D --> G

The 6:30 a.m. run, described honestly

The agent starts before the office does. It has the production board — the list of addresses scheduled for tear-off in the next three days — and a set of credentials for each jurisdiction. It opens the first portal, signs in, searches by address or permit number, reads the status, and takes the two or three actions that are safe to take unattended: download the issued permit card into the job folder, request the inspection for a scheduled address, note the status change.

It does not guess. When a portal shows something it does not recognise — a plan review comment, a fee balance, a message from a plans examiner — it captures the screen and puts it on a short list. By the time the permit coordinator sits down at 7:45, there is one page waiting: 31 jobs checked, 26 unchanged, 3 permits issued and filed, 1 inspection booked for tomorrow at the Frisco address, and 1 that needs a human because the portal is asking for an updated certificate of insurance.

Her ninety minutes became fifteen, and the fifteen are the part that needed her. That is the whole promise. It is not a robot running your permit department; it is the clicking removed from the reading.

Why the 2024 version broke and this one bends

The old approach recorded a fixed path: click here, then here, then type into the third box. Any change to the page broke it, and broke it quietly. The 2026 approach works from what is on the screen. If Schedule Inspection moved from a sidebar to a dropdown, the agent finds it, the way your coordinator would after five seconds of squinting. If it genuinely cannot, it stops and says so, with a picture. Silent failure is what cost you money the first time.

Two practical rules make this safe. First, read freely, write narrowly — let it look at everything, let it take only the specific actions you listed. Second, everything it does gets logged with a screenshot, so when a jurisdiction says the inspection was never requested, you can show the confirmation page. And use real named accounts with the jurisdiction where the rules require it; do not share one login across a system that is auditing who filed what.

Putting a number on days-to-cash

The honest way to value this is not hours saved. It is days of delay removed between the last shingle and the last dollar.

Delay removed: one job in three, 2.4 days each, is about 0.8 days of average delay across all jobs. On $554,200 a month, roughly $18,200 a day of revenue, 0.8 days pulls about $14,600 of cash forward permanently — a one-time cash benefit, plus the ongoing interest saved on the float, about $134 a month at 11%. Small. The labour is bigger: 7.5 hours a week at $26 is $845 a month, and cutting it to 1.5 hours saves about $676 a month, or $8,100 a year.

The real money is the tail nobody budgets: one stop-work order avoided, one re-inspection fee, one crew mobilised to a house with no permit. Call that $2,000 to $5,000 a year at this size, more where contractor registration is taken seriously. Add it up and you are near $12,000 to $15,000 a year for something that runs on a few hundred dollars a month and, unlike the 2024 version, does not need rebuilding every time a county updates its website.

What you should not hand to a screen-driving agent

Do not let it submit a permit application unattended. Applications carry attestations, and a signature on a jurisdiction's form is a legal act by your licence holder. Let it fill the form and stop at submit.

Do not let it accept a plan review correction or agree to a fee. Those are decisions with money and code interpretation attached.

Do not point it at a carrier portal to file a supplement. Reading supplement status is fine and useful. Filing one is a negotiation, and your estimator's judgment about what to argue and what to let go is the difference between a healthy job and a fight.

And do not skip the weekly spot-check. Once a week, someone opens two portals by hand and confirms the agent's summary matches reality. Ten minutes. It is the cheapest insurance in the whole arrangement.

Frequently asked questions

Is it against the city's terms of service to have software log in for us?

It varies by jurisdiction and it is worth ten minutes of reading before you start. Many portals are silent on it; some prohibit automated access outright. Where it is prohibited, do not do it — and ask the jurisdiction whether they offer a contractor account with status notifications, because a surprising number now do and nobody in your office ever asked.

What happens when a portal adds a login code sent to a phone?

The agent stops and asks a person. That is the correct behaviour, and it is one reason to run the portal sweep first thing in the morning when your coordinator is at her desk rather than overnight. Some shops route those codes to a shared office line so any of two or three people can clear them.

Can it do the same on our supplier and manufacturer portals?

Yes, and the warranty registration one is often the highest-value target of the lot, because a missed enhanced warranty registration is invisible for years and then very expensive. Having the agent check every completed job against the manufacturer's contractor portal each Friday closes a gap most shops do not know they have.

How long does it take to set up for nine different cities?

Days rather than months, because there is no custom build per portal — you are describing the task in plain language and giving it credentials, not writing a path for each site. Budget the time instead on deciding which actions it may take unattended in each jurisdiction, which is a policy conversation between you and your permit coordinator.

The other queue that fills while your coordinator is buried in portals is the phone. Homeowners calling about an inspection date, adjusters calling back, and new storm damage calls all land in the same 8 a.m. window. CallSphere builds AI voice and chat agents that answer the line and the website chat around the clock, take the address and the reason for the call, and book inspections and estimates onto the right calendar — so the morning portal sweep and the morning phone rush stop competing for the same person.