MILabs
Integrations

Job dispatch automation with Fergus for field service teams

How job dispatch automation can read incoming requests and suggest crew assignments alongside Fergus, with a person approving each one.

Updated 2026-04-07

Job dispatch automation with Fergus

A dispatcher's morning often starts with the same question: which requests arrived overnight, and who is free to take them. At a trades or cleaning business using Fergus the answer is split between the platform's job records and an email thread, a voicemail note or a web form nobody has keyed in yet. Job dispatch automation closes that gap. It reads each incoming request, pulls out job type, site and timing, and places it in a queue for the office. Where Fergus holds the schedule and customer history, the automation can compare a new request with open jobs and crew availability before anyone reviews it. How far that goes depends on what Fergus exposes for reading and writing records, so the first conversation is about data access. Each assignment should still pass a dispatcher's eye, since a wrong address or a double-booked van costs more to fix than the minutes saved.

How it works

  1. Pick the Fergus records the automation works with, such as job, customer and schedule data, and the fields it fills in, so each dispatch lands on the right job.

  2. Set up one intake point that collects requests from email, web forms and phone notes, and extracts job type, site address, timing and urgency.

  3. Compare each request with open jobs and crew availability held in Fergus, and produce a suggested assignment with the reasons for it.

  4. Route every suggestion to a dispatcher review queue, where a person confirms or changes the crew before anything is written back or sent.

  5. After confirmation, record the assignment against the job in Fergus where the platform allows it, and notify the crew with the site details they need.

  6. Review the queue rules with the owner once the first requests have been handled, so suggestions match how the business allocates work.

good questions, straight answers

Frequently asked questions

How does a job dispatch automation stay in step with Fergus?
The automation reads Fergus through whatever access the platform and your plan provide, so the first decision is which records it needs, usually schedule and customer data. The team then agrees whether changes made in Fergus should flow back into the dispatch queue, and how often that check runs. A single agreed list of fields and owners stops the two systems drifting apart.
How do I know a job dispatch automation works with Fergus?
Test the build against a sample of past requests before it touches live bookings. Check that each request is read correctly, that the suggested crew was genuinely free at the time, and that nothing reaches a technician without a dispatcher's confirmation. Where Fergus's documentation does not confirm a step, MILabs treats that step as unproven until the owner has seen it work with the business's own records.
Can I start with a part of a job dispatch automation on Fergus?
Yes. Many businesses begin with intake alone, collecting requests from email and web forms into one queue with extracted job details, and leave assignment suggestions for later. Another starting point is the suggestion step on its own, run in parallel with the current manual process so the office can compare results. Each part can be scoped and checked separately, and the later parts such as live crew updates depend on what Fergus allows.
How does MILabs test a job dispatch automation against Fergus?
MILabs checks the build against the business's own records and rules, not a generic template. The test set covers ordinary requests, unclear addresses, after-hours messages and overlapping jobs, and each result is compared with the decision a dispatcher would have made. Failures are logged with a reason, so the owner can see whether the fault lies in reading the request, in availability data or in the rules.
What does MILabs do after delivering a job dispatch automation for Fergus?
MILabs hands over the rule set, the queue configuration and a short written account of which Fergus records the build reads and writes, so the owner's team can maintain it. Support after handover can be discussed as a separate arrangement, and any change to how suggestions are made should go through the same review as the original. The owner stays responsible for approving what reaches customers and crews.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.