About this agent
Ships in the FieldCamp agent marketplace — because team performance is managed by anecdote in most shops, and anecdotes are unfair in both directions.
Without numbers, team management runs on impressions: the tech who complains less seems better, the one on brutal routes seems slower, and the quiet drift of a good tech having a bad month gets noticed a quarter late. Impressions are unfair to exactly the people data would vindicate.
This agent runs the numbers weekly: visits, durations against job-type norms, revenue, on-time rate — per tech, ranked, with context so route luck doesn't masquerade as merit. Excellence gets visible (and praisable), slips get caught at week two instead of month three, and the Monday huddle gets facts where the vibes used to be.
What it actually does
Trigger: Weekly — Monday 9 AM
- 1
Runs Monday at 9
schedule_mondayAfter the week closes, in time for the Monday huddle.
- 2
Computes each tech's week
compute_tech_metricsVisits, durations versus job-type norms, revenue, on-time arrivals.
- 3
Ranks fairly
rank_with_contextRoute difficulty and job mix weighted in — raw counts flatter the lucky.
- 4
Flags the drifts
flag_changesWho's trending up, who's slipping versus their own baseline — worth praise or a question.
What you get
A Monday team scoreboard that's fair, contextual, and two months earlier than the conversation you'd otherwise have.
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.
Team report ready
Mon 9:00 AM · 6 techs analyzed
Details
Flag
Marcus on-time rate −15%
Summary
Priya leads on revenue per visit (3rd week running — her upsell scripts work). Marcus's on-time rate dropped 15% vs his baseline; his routes added two far-north stops — likely routing, not effort. Suggest: rebalance north territory.
Reports to managers, unattended. It never messages technicians directly — performance conversations are yours.
By trade
Same agent, configured to how your vertical actually works.
Questions, answered
Do my techs see this?
By default it goes to managers only. Some shops share a version in the Monday huddle — visibility done openly tends to lift the middle. Your call, configured during setup.
How does it avoid punishing techs with hard routes?
Durations compare against job-type norms and the ranking weighs route difficulty and job mix. The example flag in this very template is one that exonerates the tech and blames the routing.
Is revenue per tech a fair metric?
Alone, no — paired with job mix and visit counts, it's informative. The report presents the cluster, not one number, precisely so it informs conversations instead of replacing them.