About this agent
Ships in the FieldCamp agent marketplace — because the follow-ups buried in visit notes are the ones that turn into Friday surprises.
The day's truth lives in visit notes, and visit notes are write-only memory in most shops: techs record "needs part, will return" and "customer wants quote for the back unit" all day, and nobody reads the pile until something breaks loose later.
This agent reads the pile every evening. Completions, cancellations, jobs that ran long, and — the real payload — every note that implies a tomorrow: parts to order, quotes promised, return visits implied. The dispatcher gets one summary at six o'clock instead of an archaeology project on Friday.
What it actually does
Trigger: Daily at 6 PM
- 1
Runs at end of day
schedule_6pmEvery evening at 6 PM — after the trucks are back, before the day evaporates.
- 2
Reads everything the techs wrote
read_visit_notesEvery visit note and job status change from the day, in one pass.
- 3
Pulls out the implied tomorrows
extract_followupsParts to order, quotes promised, return visits implied — flagged with the source note.
- 4
Writes the dispatcher's digest
write_summaryDone, not done, ran long, needs action — skimmable in two minutes.
What you get
An end-of-day digest with every follow-up the day generated — read in two minutes, nothing buried.
A run, as you’d see it
Agent runs land on a timeline — what fired, what the agent found, and the action waiting for a human. This is that screen.
Evening summary ready
Today · 23 visits · 6:00 PM
Details
Flagged
4 follow-ups from visit notes
Summary
21 of 23 visits completed; two rescheduled. Marcus's 2 PM ran 90 minutes long (attic access). Follow-ups: order condenser fan for #JOB-2210, quote promised to Hendersons, return visit implied at Mesa Vista, callback for gate code.
Read-and-summarize only, unattended — it surfaces follow-ups; acting on them stays with your team.
By trade
Same agent, configured to how your vertical actually works.
Parts-needed notes get pulled into a single order-tomorrow list.
Weather-shortened days summarize what moved and what the backlog now looks like.
Questions, answered
Where does the summary go?
In-app notification to the roles you choose — typically dispatcher and owner. Slack delivery is a configuration option through a custom connection.
Can it create the follow-up tasks itself?
The template surfaces them; task creation can be added behind approval during setup. Most shops start read-only and add task drafting once they trust the flags.
What if techs write thin notes?
The summary makes the thinness visible — "3 visits closed with no notes" is its own flag. Shops report note quality improves within weeks of the summary existing, because now someone reads them.