Your FSM dispatches the jobs. Behind it, the admin piles up: double-bookings slipping past the dispatcher, utilisation reports nobody builds, after-hours roster gaps, audit trails when SLA breaches happen. Sprigr runs the back-office layer around dispatch so your ops lead sees the whole picture by Monday.
The admin around dispatch - reconciliation, conflict flags, utilisation, audit trail - runs on Sprigr.
Dispatch data reconciliation Sprigr
Schedule conflict flags to the dispatcher Sprigr
Utilisation reporting by tech & crew Sprigr
Dispatch audit trail maintained Sprigr
After-hours & roster gap flags Sprigr
Weekly back-office scheduling report Sprigr
Dispatch decisions & assignments → You
Customer notifications (via FSM) → You
Your dispatcher assigns the work. Sprigr runs the paperwork.
What Sprigr runs around your FSM
Back-office admin that simPRO, ServiceTitan, and Jobber were never built for, handled on autopilot.
Dispatch data reconciliation
Jobs created in your FSM tool matched against technician schedules, actual timesheets, and job completion records. Discrepancies (assigned but not started, overrun jobs, mis-assigned qualifications) flagged to the dispatcher. Schedule reality gets reconciled against the plan, daily.
Schedule conflict flags
Double-bookings, under-qualified assignments, travel-time violations, and after-hours roster gaps flagged to the dispatcher before the day starts. Sprigr doesn't dispatch the jobs; it surfaces the conflicts so your dispatcher can act with full visibility.
Technician utilisation reporting
Weekly utilisation per technician, per crew, and per job type compiled for the ops lead. Over-allocated crews, under-utilised specialists, and capacity gaps surface in the Monday report. Hiring and scheduling decisions get a data layer.
Dispatch audit trail & paperwork
Every dispatch decision, reassignment, and override logged with reason, timestamp, and decision-maker. When customers or auditors ask why a job was sent to Tech A instead of Tech B, the trail is there. SLA breaches have evidence, not excuses.
After-hours & emergency roster flags
On-call rosters, after-hours coverage gaps, and emergency-response thresholds tracked. Gaps flagged to the ops lead before a shift starts. Sprigr doesn't take the call; it surfaces when coverage is thin so your team can arrange it.
Weekly back-office scheduling report
Monday morning, schedule conflicts, utilisation numbers, SLA adherence, after-hours coverage, and dispatch variance land in the ops lead's inbox. You start the week already in the picture across every crew.
Set up in under an hour
Describe what to watch, reconcile, and report. Sprigr runs it.
01
Connect simPRO or your FSM
Link your simPRO or field service management tool. The AI reads your technician roster, schedules, and job types. Credentials encrypted and stored securely.
02
Define reconciliation & flagging rules
Tell Sprigr what to watch for in plain English. "Flag double-bookings. Flag jobs assigned to under-qualified techs. Flag travel time over 45 minutes. Compile weekly utilisation by crew."
03
Sprigr runs the scheduling admin
Sprigr monitors the schedule, reconciles actuals, flags conflicts, and compiles reports. Your dispatcher keeps assigning jobs in your FSM. Sprigr just makes sure nothing slips through and you can see the whole picture at a glance.
Dispatch and customer notifications stay with your FSM and your team. Sprigr runs the back office only: reconciliation, conflict flagging, utilisation reporting, audit trail. Every action is logged with a signed, hash-chained audit trail.
No. Your dispatcher (or your FSM's own scheduling logic) still assigns jobs. Sprigr runs the back-office layer around dispatch: reconciliation, conflict flagging, utilisation reporting, audit trail, roster-gap flagging. Dispatch judgement stays with humans; admin runs on autopilot.
Does Sprigr notify customers?
No. Customer notifications, appointment confirmations, and ETAs stay with your FSM tool and your team. Sprigr runs the back office only: dispatch reconciliation, utilisation reporting, audit trail. Keeping the customer-facing side out of AI hands is deliberate.
Does this work with simPRO?
Yes. Sprigr integrates with simPRO via the official API. It reads technician schedules, job assignments, and timesheets, and writes back notes and flags where needed. simPRO stays your system of record for scheduling.
How does this compare to the scheduling my FSM already does?
Your FSM handles the dispatch itself: creating the job, assigning the tech, updating the calendar. Sprigr handles the back-office layer: reconciling actuals against the plan, flagging conflicts the dispatcher might miss, reporting utilisation, keeping the audit trail. They're complementary, not competing.
How long does setup take?
Under an hour. Connect your FSM. Describe the admin you want handled in plain English. AI scaffolds the workflow. No coding, no IT team required.
Dispatchers assign the work. Sprigr runs the paperwork.
Back-office admin around your FSM scheduling. Up and running in under an hour.