Trades and field services
Field service software for firms that outgrew the box
Off-the-shelf platforms cover the common path well. The trouble starts at the workflow that makes you money and that nobody else runs.
Four things to settle before you commission anything
4 things that decide this
- 01Integrating with a major field service platform is usually an approval problem, not a coding problem. Credentials are issued per tenant, and each customer's admin has to connect your app before a single call succeeds.
- 02Adding new data later means every one of those admins approves again. That queue, not the API, sets your timeline.
- 03The incumbent may already sell what you are commissioning. Voice answering and automated dispatch are paid add-ons on the big platforms, so check whether you are building a competitor to your own vendor.
- 04Anything assuming connectivity fails in a basement or a plant room. Offline is the normal operating condition, not an edge case.
Buy the platform. Build the part that is yours.
Most trades businesses should not replace their field service platform. Scheduling, invoicing and payments are solved, and rebuilding them buys you nothing except a maintenance burden.
What justifies a custom build is the workflow the box refuses to model. Parts procurement across branches. A dispute process with money held in the middle. A rule about who may take which job that only exists in your business.
We start by asking which of those you actually have. If the honest answer is none, the right advice is to configure what you own and keep your money.
The field service work we take
Three production systems, in two countries, each starting at a different leak.
AI call answering that books
ZhoopZhoop runs inbound agents that answer, collect booking details and confirm appointments across branches. Outbound agents call suppliers for parts availability and return a quote comparison.
Parts procurement
The unglamorous workflow nobody sells off the shelf. Calling round suppliers, capturing prices and putting them side by side is real work that a platform will not do for you.
Operations platforms
Scheduling, routing, invoicing and messaging in one place instead of four. Maidily runs this for residential cleaning companies with travel-time-aware recurring jobs.
Marketplace trust and payments
WorkMateAI holds funds between customers and tradespeople, freezes them on dispute, and generates chargeback evidence from the record.
Provider verification
Checking business numbers, trade licences, insurance and identity before someone can accept a job. Expiry tracking matters more than the initial check.
Offline-first mobile
Field apps that fully work with no signal and reconcile later, keeping the time the work happened rather than the time it synced.
- RegisterYour own developer org, not the client's.
- Per-tenant keysEach customer gets its own pair.
- Admin approvesA person clicks. You wait.
- ConfigureA setting only an office admin can make.
- LiveWorking, for that one tenant.
- New scopeEvery admin approves again.
Only the first box is engineering. Sharing a client's application key to skip the rest is banned by the platforms, and it is the shortcut that ends an integration partnership.
A missing setting looks exactly like a bug
Booking integrations on the larger platforms can require a tag to be configured in the customer's own settings and selected when the app connects. Until a non-technical office administrator creates it, bookings fail.
Nothing about the error says so. Your team reads it as a defect, spends a week on it, and the fix turns out to be a five-minute change by someone who was never in the project.
We treat customer-side configuration as part of the build. It goes in the runbook, the onboarding checklist and the error message itself, so the next failure names the missing setting.
- Write the customer-side setup steps before you write the integration.
- Make errors name the setting, not the status code.
- Assume approvals are the schedule, and plan the sequence around them.
Systems running in trades businesses
ZhoopZhoop
AI receptionist and parts procurement for a multi-branch auto repair business.
Read the case study →
Maidily
Integrated operations platform for residential cleaning businesses.
Read the case study →
WorkMateAI
Dispute resolution, payments, and compliance for Australia's on-demand trades.
Read the case study →
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
What these builds run on
Application
Voice and messaging
Data
Payments
Questions trades operators ask
01How long does it take to get access to a major platform's API?
Longer than the engineering, and the delay is not in your control. You need your own registered developer organisation, then each customer's administrator has to connect and approve your app before any call works for that tenant. Adding a new data scope later restarts approval with every tenant. Plan the rollout around that queue rather than around sprint length.
02Can you build on our existing platform login?
No, and any agency offering to is telling you something useful about how they work. Registering an application on behalf of a customer and sharing its key is a security violation under the platforms' own rules, and the customers are instructed not to grant developers admin access. We register as ourselves, and you connect our app.
03Should an AI receptionist take emergency calls?
Not without a defined path to a human, and the escalation rule matters more than the voice quality. An agent that books a routine appointment is doing safe work. A caller with a burst pipe or a gas smell needs a person, and the system should recognise that class of call and hand it over rather than continue a booking script.
04What does the parts side of the job actually need?
Parts work needs someone to make the calls and somewhere to put the answers. ZhoopZhoop runs outbound agents that ring suppliers for availability and pricing, then return a quote comparison rather than a transcript. The comparison is the product. A recording of six phone calls is just more work for the person who made them.
05Do we need our own app, or a mobile view of the platform?
A mobile view is enough until connectivity or a custom workflow breaks it. Technicians in basements, plant rooms and rural properties lose signal routinely, and a web view that degrades to read-only stops the job. If your crews work in those places, or follow a process the platform cannot model, that is when a dedicated app earns its cost.
Go deeper
- Field service software in practice →The missed call, the offline job and the money held in between.
- Field service case studies →Three systems in production across two countries.
- AI agent development →Agents that answer, book and act on your systems.
- AI agents vs RPA →Which one suits a workflow that changes shape.
