About this agent
Ships in the FieldCamp agent marketplace — because the gap between "request received" and "request understood" is where response times go to die.
A request queue is only useful if someone keeps it triaged — and triage is the first job skipped on a busy day. Untriaged, every request looks the same size, the urgent one waits behind four routine ones, and the one missing a gate code gets discovered missing at the curb.
The copilot triages on arrival. Each new request gets classified by work type, scored for urgency with the reason stated, checked for the information your dispatch actually needs, and tagged with a suggested next step — schedule it, call back for details, or route to a specific team. Your queue reads like someone already went through it, because something did.
What it actually does
Trigger: Request created
- 1
Catches the new request
request_createdFires on creation — form fills, agent-created records, or office entries all triage the same way.
- 2
Names the work
classify_workService type and category from the request text, mapped to how your shop slices its work.
- 3
Scores the urgency
score_urgencyLow to urgent, with the one-line reason — "active leak" outranks "quote when convenient."
- 4
Spots what's missing
flag_gapsNo address, no access details, no equipment info — flagged now, not at the curb.
What you get
A request pipeline that's already classified, urgency-scored, and gap-flagged when your dispatcher opens it.
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.
Request created
Web form · 8:14 AM
Details
Classified as
AC repair — residential
Summary
Customer reports AC blowing warm air, second floor only. Urgency: high — heat wave forecast this week. Missing: unit location and attic access details. Suggested: schedule diagnostic, ask about access in the confirmation.
Pure copilot — it annotates the queue and suggests; scheduling and customer contact stay with your team.
By trade
Same agent, configured to how your vertical actually works.
Questions, answered
Where do the triage notes show up?
On the request itself — classification, urgency with reason, missing-info flags, and the suggested next step, right where your dispatcher already works the queue.
Can it schedule the work itself?
No — by design this template suggests and a human schedules. If you want event-driven action, pair it with agents that act under approval gates; triage stays a copilot.
How does it know what counts as urgent for us?
The defaults are sensible per trade, and we tune them to your rules during setup — what your shop treats as drop-everything is configuration, not the agent's opinion.