facebook-pixel
Field ops on autopilot →AI Dispatcher → 1:1 demo

Weekly Reporter

The Weekly Reporter is an AI agent in FieldCamp that runs every Monday at 8 AM and builds the week's operations report — KPIs across jobs, revenue, and schedule performance, an executive summary in plain language, and the follow-up actions the numbers imply — delivered before your week starts.

Runs Mondays 8 AMBuilds KPI reportsWrites executive summaries

A real template from the FieldCamp marketplace, configured on your operation. Setup included in your plan.

About this agent

Where it came from

Ships in the FieldCamp agent marketplace — because the weekly report every owner means to build is the first casualty of every actual week.

Every owner has the same Monday intention: look at last week properly — what we did, what it earned, what slipped — and run this week on purpose. Then the phone rings. The operations report becomes a glance at the bank balance, and the week runs on vibes again.

The reporter makes the intention automatic. Monday at 8 it assembles the week that was: jobs completed against scheduled, revenue against the run rate, the schedule's hit rate, the anomalies worth a question. Then the part dashboards skip — a plain-language executive summary and a short list of follow-ups the numbers imply. Reading it takes five minutes. Building it takes you nothing.

What it actually does

Trigger: Weekly — Monday 8 AM

  1. 1

    Runs Monday morningschedule_monday

    8 AM, before the week gets loud.

  2. 2

    Computes the week's numberscompute_kpis

    Jobs, revenue, completion rates, schedule performance — against prior weeks, not in a vacuum.

  3. 3

    Finds what's off-patternfind_anomalies

    The metric that moved, the territory that slipped, the job type quietly growing.

  4. 4

    Writes the executive summarywrite_summary

    Plain language, with the follow-up actions the numbers imply — not just charts.

What you get

A Monday-morning operations report with an executive summary and implied actions — five minutes to read, zero to build.

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.

Weekly report ready

Mon 8:00 AM · last week's ops

Pending

Details

Headline

Revenue +12% · completions 94%

Summary

Strong week: $48.2K revenue (+12% vs 4-week avg), 87 of 93 visits completed. Watch: Northside reschedules doubled — likely the access-notes gap. Follow-ups: review Northside booking flow; maintenance-plan renewals dip next month.

DismissOpen report

Reads and reports, unattended. The follow-up actions are recommendations for humans, not tasks it assigns itself.

By trade

Same agent, configured to how your vertical actually works.

Cleaning

Recurring-revenue retention gets its own section — churn hides in weekly numbers.

HVAC

Seasonal context built in — a slow shoulder-season week reads against the right baseline.

Questions, answered

How is this different from my dashboards?

Dashboards answer questions you ask; the reporter asks them for you. The executive summary and implied-action list are the difference between data being available and the week being reviewed.

Can I change what's in it?

Yes — the KPI set, comparisons, and delivery (in-app, email, or Slack via the standup agent) are configured during setup. Most owners start with the default and trim.

Who should get it?

Owner and ops lead, typically. Pair with the Weekly Team Performance agent if your techs should see their own numbers too.

Have an agent idea we haven’t built?

The ideas section of this library exists because customers keep asking "could it just…?" Bring yours. If it should exist, we build it — and it ships as a template like this one.

No demo deck. Just your business and ours.