Field Service Requests: Automating the Dispatch Loop
Maintenance requests arrive by phone, WhatsApp and email, and get assigned by whoever answers. Automating the dispatch loop makes every job visible from first call to final invoice.

A building manager calls to report that the air conditioning on the third floor has stopped. The dispatcher writes it on a pad, calls a technician, and the technician fixes it that afternoon. Two weeks later, accounts asks why the job was never invoiced, and the customer asks why nobody told them the technician had been. The repair was fine. The loop around it was broken.
Where the dispatch loop usually breaks
Field service work, whether it is lift maintenance, air conditioning, IT support visits, medical equipment servicing or facility repairs, follows the same basic loop. A request comes in, it is assessed, someone is assigned, they travel and do the work, the job is closed, the customer is informed and the work is invoiced. Each step is simple. The trouble is in the handovers.
Picture a maintenance contractor in Amman with twenty-five technicians covering residential towers, offices and a few hospitals. Requests arrive by phone, by WhatsApp to the dispatcher’s mobile, by email and sometimes directly to a technician the customer knows. The dispatcher keeps a whiteboard and a spreadsheet. On a normal day it works. On a busy day, jobs fall between the board and the spreadsheet, urgent requests wait behind routine ones, and nobody can say how many jobs are open at any moment.
The typical failures are predictable:
- Requests that never become jobs, because they arrived on a channel nobody was watching.
- Wrong technician sent, without the skill or the part needed, leading to a second visit.
- No priority logic, so a hospital chiller waits behind a residential thermostat.
- Jobs finished but not closed, so they are not invoiced and contract response times cannot be shown.
- Customers left guessing, calling repeatedly to ask when someone will arrive.
Automating the loop, one stage at a time
The dispatcher stays. What changes is that they work with a system that captures every request and applies the routine rules, leaving them free to handle the exceptions. Each stage of the loop has a clear automation opportunity.
- Capture every request in one place. Give customers a few clear channels, such as a web form, a dedicated email address and a WhatsApp business number, and route all of them into one job list. Phone calls are logged by the dispatcher directly into the same list. Every request receives a job number and an automatic acknowledgement.
- Classify and prioritise by rule. Use the customer, site, equipment type and reported problem to set the priority automatically. A customer with a contract that promises a four-hour response for critical equipment gets that priority without anyone having to remember it.
- Suggest the right technician. Assignment rules consider skills, certifications, the area the technician is covering that day and their current workload. The system proposes; the dispatcher confirms or overrides. Over time, most routine jobs are confirmed with one click.
- Keep the customer informed automatically. Messages at key points, such as job received, technician assigned with an expected arrival window, and job completed, cut most of the “where is the technician?” calls.
- Close the job on site. The technician records work done, parts used, time spent and a customer confirmation on a phone or tablet. The job closes when they leave the site, not when they remember to call the office.
- Trigger billing and follow-up. Closed jobs that are chargeable flow to invoicing with parts and hours attached. Jobs covered by a contract update the contract record. A short satisfaction question can follow the next day.
Choosing the rules that drive priority and assignment
The rules are where the value is, and they should be written by operations, not by whoever builds the system. Sit the dispatcher, a senior technician and the service manager together and agree, in writing:
- Priority levels, usually three or four, each with a clear definition and a target response time. Critical might mean safety risk or full loss of service at a hospital; routine might mean a fault that can wait for the next scheduled visit.
- Which contracts promise what. Response and resolution commitments per customer, so the system knows when the clock is running.
- Skill and certification requirements per equipment type, so a technician is never sent to work they are not qualified for.
- Escalation steps when a target is at risk: who is notified, and at what point before the deadline.
Keep the first version simple. A few clear rules that cover most jobs are better than a complicated scheme that nobody trusts. Review them after a month with real data on how often the dispatcher overrides the system’s suggestion, and why.
Tools: what you actually need
Many companies assume this requires a large field service management platform. For bigger operations, dedicated software may well be the right choice, and several ERP (enterprise resource planning) systems include field service modules. For smaller teams, a combination of a ticketing or job management tool, a simple mobile form for technicians and a workflow tool to connect the steps can deliver most of the benefit.
Whatever you choose, check three things: that it works on the phones your technicians already carry, including with weak mobile coverage in basements and plant rooms; that it can send messages through the channels your customers use; and that closed jobs can flow into your accounting system without retyping.
What the loop shows you once it is running
Once every job passes through one system, the operation becomes visible. You can see open jobs by priority at any moment, response times against contract commitments, first-time fix rates (jobs solved on the first visit) by equipment type, and which sites generate repeat calls. Repeat calls are especially telling: a site that keeps reporting the same fault may need a proper repair, a replacement recommendation or a conversation about the contract.
The contractor in our example would also finally be able to answer the question every service business should be able to answer: how many jobs did we finish last month, how quickly, and did we invoice all of them?
A dispatch loop that closes every time
Automating field service dispatch comes down to a few guarantees: every request becomes a job, every job reaches the right person, and every finished job is closed, reported and billed.
Our Intelligent Automation service designs and builds these workflows around your existing tools where possible, including request capture, assignment rules, customer updates and the link to invoicing. In line with the Know stage of the KEMLAT Method, we first map how jobs really flow today before deciding what to automate.



