Most trade businesses that have bought job management software are getting real value from it. Scheduling is visible, invoices go out faster, nobody is chasing a docket book in a glovebox. The software is not the problem.
The problem is what it can see. ServiceM8, simPRO, Fergus, AroFlo and Tradify are all excellent at managing work that is already inside them. None of them has any idea about the job that came in while you were under a house, because nothing put it there.
The gap, stated plainly
There is a moment between “the phone rings” and “a record exists in the system”. In most trade businesses that moment is a human being, usually the owner, usually holding something. Everything that falls out of that moment — the call not answered, the note written on a hand, the address heard wrong, the callback that never happened — is invisible to the software forever.
Which means the pipeline you look at on Sunday night is not your pipeline. It is the subset of your pipeline that survived contact with your week.
What the software can and cannot do about it
Every one of these platforms has an API, and they differ more than the marketing suggests. Worth knowing before you assume something can be automated:
| Software | How you connect | Practical limit |
|---|---|---|
| ServiceM8 | API key per account, or an OAuth add-on | ServiceM8’s own documentation flags that creating jobs via the API may incur account charges — worth checking against your plan |
| simPRO | OAuth2, and the customer creates the API user in their own build | No dependable schedule write, so a job can be created but not slotted |
| Fergus | Personal access token or OAuth2, public OpenAPI | Has a native enquiry concept, so enquiries and jobs stay distinct |
| AroFlo | HMAC-signed REST, per-account credentials | Custom fields can be populated from the call, which most cannot |
| Tradify | Partner-gated — access is requested from Tradify | You cannot simply start; approval is theirs to give |
The point of the table is not that one is better. It is that “we’ll just connect it” is a sentence with a lot hiding behind it, and anyone who tells you otherwise has not read the docs.
Three rules if you close the gap
If you do put something in front of the phone — a person, a service, an AI receptionist — and wire it into the job software, three rules keep it from becoming a new problem.
- Create, never edit. Whatever answers the phone should be able to create a new record. It should never touch an existing one. The worst outcome is not a missed job; it is a customer record quietly corrupted by something that misheard.
- Have a floor. A rule about what is complete enough to become a job — name, contactable number, address, what is wrong. Below the floor it becomes a note for a human, not a job. Otherwise you have automated the creation of junk.
- Audit month one. Every record created, against the call that created it. Not a sample. All of them, for the first month. It is boring and it is the only way you will trust the thing by month two.
The test
Open your job software right now and look at last week. Then open your phone’s call log for the same week. If there are numbers in the call log that have no matching record and no matching outgoing call, that is the gap, measured, in your own business.
How you close it is a separate question. Whether it is open is not.
We write about each of these platforms in more detail on the integrations pages, including what we deliberately do not do in each one.