Home services is skilled trade work buried under portal work. Homeowners pay you to install equipment and fix systems — not to watch a dispatcher toggle between Austin Energy, the city permit lookup, and ServiceTitan because someone submitted a change order at 9pm without a job number.
Permit follow-ups are not installs — but they own Monday morning
Eleven hours. Every week. Gone.
A twelve-truck HVAC and light-commercial shop in Austin tracked one month: 3.2 hours checking permit status across city portals and utility rebate sites, 2.8 hours staging estimate follow-ups, 2.4 hours renaming work-order photos and inspection PDFs from field techs, 1.9 hours reconciling parts POs against open jobs. Zero wrench time. Zero revenue-generating dispatch. Just production work owners never see on the job margin sheet.
Most shops under fifteen trucks know the fix is "hire another dispatcher." The math rarely works. A part-time dispatcher at $22/hour for eleven hours is $968/month plus PTO, sick days, and the Thursday someone calls in during a heat-wave week. You are not short on licensed techs. You are short on a production layer that runs before anyone opens ServiceTitan or Housecall Pro.
That layer is what an isolated cloud computer is built for — persistent folders per job, a real browser that logs into permit portals through a residential VPN, and duties that fire whether you are on a roof or driving to the supply house.
Three duties that replace dispatcher prep work
Start with permits. Not installs.
These three patterns cover most of the eleven-hour block for shops under fifteen trucks. Each maps to a specialist on CloudAxis with scheduled duties — not a chat thread you re-paste instructions into every Monday.
- Permit status sweep (weekdays 5:50am). A Browser specialist logs into your city permit portal, utility rebate site, and AHJ inspection lookup through a residential VPN, matches open permits to active job numbers in your export, and writes rows to
~/files/permits/permit-queue.csv. Approved permits land in a "cleared for dispatch" tab. Jobs stuck in review, missing mechanical drawings, or flagged for additional documentation get a WhatsApp summary at 6:12am — not a blast to the whole crew. Same-day emergency no-cool calls with permit holds get their own row so dispatch does not promise a truck that cannot legally roll. - Estimate follow-up staging (Mondays and Thursdays 6:05am). A Research specialist reads your exported open-estimate report from ServiceTitan or Housecall Pro, cross-checks last contact dates in the customer notes, and builds a call list CSV at
~/files/sales/follow-ups-this-week.csvsorted by ticket size and days since proposal sent. Homeowners who signed digitally in the last 48 hours get moved to a "already closed" tab so your inside sales rep stops calling people who already paid the deposit. - Work-order document filing (Tuesdays, Wednesdays, Fridays 6:20am). A Browser specialist downloads field uploads from your FSM mobile app backend and customer portal, renames to
{job-number}-{address-slug}-{doc-type}-{YYYY-MM-DD}.pdf, and drops them in~/files/jobs/{job-number}/field-uploads/inbox/. Blurry photos, missing model serial plates, and unsigned change orders land in a CSV grid you can fix inline in the Files app — ninety seconds on your phone between site visits, same path the agent reads on the next run.
An eight-truck plumbing shop in Denver set this up on a Saturday. First Monday the Browser duty missed one permit over a shortened address — fourteen minutes to fix in the visible browser. By week three the permit queue filled before 6:30am.
Tell Cloudia the outcome in plain English: "Every weekday at 5:50am, check permit status for open jobs, update the CSV, WhatsApp me only holds and missing docs." She builds the specialist, wires browser skills, and schedules the duty. Watch the first city portal run in the Browser app — non-negotiable for anything involving municipal credentials.
Do not wire agents straight into live dispatch on pass one. Stage everything in
~/files/jobs/ and ~/files/permits/ until naming conventions and hold flags are boringly consistent. Shops that skip staging push wrong permit statuses into ServiceTitan and spend more time on angry homeowner callbacks than they saved. Mark only city portal, utility rebate, and AHJ login URLs as require VPN in settings — VPN minutes are capped per plan. Leave your public website estimate form on standard routing.
The math — part-time dispatcher vs agent stack
$968 versus $39. Different jobs. Same truck board.
Austin shop before picture:
- Labour. 11 hours/week × $22/hour effective dispatcher cost = $968/month. Add ~2 hours operations manager review of permit gaps at $32/hour = $256. Total admin layer: $1,224/month.
- Opportunity cost. Those eleven hours came out of weeks already at capacity — two install slots per month delayed because "Monday permit triage" ate the morning huddle.
After three duties on CloudAxis Pro ($39/month):
- Labour. 1.75 hours/week dispatcher review of flagged rows and estimate exceptions. About $154/month at $22/hour — but that hour is actual customer-facing dispatch, not portal clicking.
- Platform. $39/month. Browser minutes for municipal portals stay inside hard caps — no surprise API bill. Overnight scheduling mechanics in how to make AI agents work overnight.
- Net. $1,031/month back in labour, 9.25 hours returned, $39 software. One $4,200 change order that closes because the follow-up call happened Tuesday instead of never covers the platform for the year.
| Line item | Part-time dispatcher | CloudAxis agent stack |
|---|---|---|
| Monthly labor | $968 (11 hrs × $22) | $0 (duties run unattended) |
| Manager review | $256 (8 hrs × $32) | $154 (7 hrs × $22) |
| Platform cost | FSM seats only | $19–$39/month (Growth or Pro) |
| Before-huddle permit queue | Done manually by 8:45 or skipped | Permit duty runs 5:50am seven days |
| What you still pay humans for | Installs, diagnostics, code compliance, customer walkthroughs | Installs, diagnostics, code compliance, customer walkthroughs |
This is not "replace your dispatch team." It is replace the portal treadmill so the people you have route trucks instead of toggling tabs. For broader document skills — CSV grids, DOCX proposals, PDF inspection reports — see AI document processing in the agent OS.
What still needs a licensed installer — and why that is the point
Agents do not pull permits. They stage.
A condenser pad that needs a structural engineer stamp still needs a lead installer who reads the site photo. A gas line relocation where the permit office flagged incomplete documentation still needs a licensed tech who decides whether to reschedule or send a second truck. Code interpretation, load calculations, and the conversation that survives a declined change order — none of that belongs in a duty.
Here is the reframe most owners miss: you are not buying a robot dispatcher. You are buying back the Monday huddle where your team talks about truck routing instead of which city portal still shows "under review." The Austin dispatcher still assigns every crew. She still calls the two estimate rows the agent flagged as high-value and stale. What changed is she walks into the yard with fourteen permits already cleared — while the shop down I-35 is still logging into the portal at 8:40.
Monday 5:52am again. Same twelve-truck company. The phone buzzes at 6:12. She reads the WhatsApp summary in the break room, taps into the Files app, fixes one address suffix on a flagged row, releases three trucks for the 7:00 block. The first install sits at 7:30. The queue was staged fifty-eight minutes before the huddle. She did not open her laptop until the dispatch board.
The permit portal is not the relationship with your homeowner. It is the head start your competitor already has.
FAQs — home services contractor automation
Can AI agents run HVAC or plumbing field operations automatically?
Not licensed trade work you would stake your contractor license on. Agents excel at permit status sweeps, estimate follow-up staging, work-order document filing, and parts PO reconciliation. Installs, diagnostics, refrigerant handling, gas line work, and signed inspection sign-offs stay with your licensed team. Think production line before the first truck rolls.
How long does setup take for a shop under fifteen trucks?
Most eight-to-twelve-truck shops budget one Saturday for the permit duty and one week of morning test runs before a full schedule depends on it. Cloudia builds the first specialist in under twenty minutes if you have portal credentials and a job folder naming template ready. Match the under-one-hour first agent guide for duty scheduling mechanics.
Will city permit portals block an AI agent logging in from a datacenter IP?
Municipal and utility portals often behave differently for datacenter IPs than for someone browsing from your market. CloudAxis routes marked domains through a residential VPN from your country — the same view someone working from Austin or Denver would see. Run the first week in the visible browser so you catch two-factor and CAPTCHA issues before they hit a Monday schedule. Put work on autopilot at app.cloudaxis.ai — free tier to test, Growth at $19/month for daily duties.
AI document processing automation · How to make AI agents work overnight · AI agents for property management — staging pattern