Trades agent system
Brief every tech at 6 a.m.
A 6 a.m. job builds one digest per tech: the route, the customer's history, open estimates at those addresses, equipment age, membership, parts, gate codes, and one sales note.
- Difficulty
- Difficulty 2 of 5 in the research brief.
- Setup time
- Estimate, not from the brief: about a day if the FSM already has the route, membership, and equipment fields filled in.
The pain
The tech's hours are the bottleneck, and the morning still starts with someone reading the board out loud. The brief does not claim a dollar saving. It claims better attachment of memberships and options, and fewer return trips for missing parts or missing history.
HIRI's Q2 2025 contractor tracker: 43% of contractors had labor difficulties.
HIRI Contractor Activity Tracker
Source type · Industry research
A Simpro survey of 600-plus trade businesses: 69% see AI's value in routing and cutting downtime.
Contractor Magazine, reporting a Simpro survey
Source type · Vendor survey
6:00 a.m. cron
Pull today's stops for each tech
Attach history, open estimates, equipment age, membership, parts, and gate codes
LLM writes one sales-opportunity note per stop, from fields that exist
One SMS or WhatsApp digest, with a voice-note option
Trigger
A cron job at 6:00 a.m. local time, one run per tech who has stops that day.
Data sources
- Today's route from the FSM
- Each customer's history, open estimates at those addresses, equipment age, and membership status
- Parts to load and gate codes
- A sales-opportunity note the office is willing to have the tech see
Build it
- 1
Run it at 6:00 a.m. for techs who have stops
Skip anyone with an empty board. The message should arrive before they load the truck, not at the first driveway.
- 2
Assemble the stop from the FSM, not from memory
For each address: who the customer is, prior visits, any open estimate, equipment age, membership status, parts to load, and the gate code if you store one.
- 3
Add one sales note only when the data supports it
Membership missing, an open estimate at that address, or equipment old enough that the office already wants a conversation. Do not tell the tech to pitch something the record does not support.
Branch. If a field is blank, say it is blank. A missing gate code is more useful than a guessed one.
- 4
Deliver one digest, plus a voice note if they will not read
SMS or WhatsApp, one message per tech. Offer the same brief as a short voice note for anyone who listens on the way in.
Tools and rough monthly cost
One of the smaller bills on this site: a daily orchestration run and a handful of messages per tech. No voice agent required unless you add the voice-note option.
| Tool | Job | Rough monthly |
|---|---|---|
| ServiceTitan, Housecall Pro, or Jobber | Route, history, estimates, equipment, membership | Your existing FSM plan. |
| n8n or Make | The 6 a.m. cron and the per-tech assembly | Often the low tens of dollars. Unverified public list-price estimate, October 2026. Not a figure from the research brief. Check the vendor.Unverified |
| Twilio or WhatsApp | The digest | Per-message usage. WhatsApp has its own conversation pricing. Unverified public list-price estimate, October 2026. Not a figure from the research brief. Check the vendor.Unverified |
| LLM API | The one-note-per-stop summary and the optional voice script | Usually a few dollars a month. Unverified public list-price estimate, October 2026. Not a figure from the research brief. Check the vendor.Unverified |
Expected ROI
The brief does not give a dollar figure for this hack. The outcome it names is better attachment of memberships and options, and fewer return trips. The labor context is HIRI's 43% of contractors reporting labor difficulties, and a Simpro vendor survey in which 69% see AI's value in routing and cutting downtime. Measure return trips for missing parts and memberships sold from the brief, using your own baseline.
Caveats
- The 69% figure is from a Simpro survey, a vendor. Do not treat it as an independent result.
- ServiceTitan's Zapier path is not officially supported. A direct API read is the sturdier way to build a 6 a.m. job.
- Jobber webhooks only carry an ID and must be answered within 1 second. A morning pull does not have to use webhooks.
- There is no cited stat for minutes saved by a morning brief. Do not invent one.
Example prompt
Change the names, fees, and slots before you run it. It does not add facts that were not in the brief.
Write the 6 a.m. brief for one tech. Use only the stops and fields you were given. For each stop, in this order: time, name, address, why we are there, membership status, equipment age, any open estimate at that address, parts to load, gate code. If a field is missing, write "not on the record." Add one sales note only when an open estimate, a missing membership, or equipment age is in the data. No jokes. No weather. Under 40 words per stop. Do not tell them to upsell a replacement unless the record says the office wants that conversation.