Industry 09
Field & Home Services
Jobs are assigned in a WhatsApp group, nobody knows which technician is free, and a customer from ten days ago was never called back.
- Systems typically built
- 3
- Shipped in this sector
- Yes
- Mapping session
- Free
Every enquiry has a named owner and a next action, and an AMC renewal surfaces weeks before it lapses instead of after the customer complains.
A job assigned in a WhatsApp group has no owner once the message scrolls past — that is why a customer from ten days ago never gets called back. We build an enquiry pipeline where every job has an owner and a next action, area-based assignment that shows which technician is actually free, and a technician app built to work offline in a basement or a lift shaft, because that's where the job usually is.
What we build
The services this usually draws on
Field services FAQ
Before you ask
Including where the honest answer is 'that's a separate service' or 'ask during discovery'.
Our technicians have basic Android phones with patchy signal. Will the app work?
That's the specific condition it's built for — the technician app queues photo proof and job updates locally and syncs when signal returns, rather than requiring a live connection to function.
Can it auto-assign jobs by area without a dispatcher manually deciding every time?
Yes — area-based auto-assignment against technician availability is standard, with a dispatch view for the cases that need manual override.
How does this help renewals we currently track in a diary?
AMC and warranty dates are attached to the job record at completion, and reminders escalate weeks ahead — the diary is where renewals get missed; this is built specifically so they don't.