Skip to content
ERP & systems 15 min read

Field service management software in the UAE: from the customer’s call to the invoice

By Manager & CEO, SmartTech Studio

A UAE maintenance company’s day often starts like this: an AC that will not cool in a Dubai apartment, a lift stuck in an Abu Dhabi building and a WhatsApp photo of a leak from a kitchen ceiling. The receptionist logs the calls in a notebook, the supervisor hands them out in a WhatsApp group, technicians return with handwritten job sheets, and the invoice goes out days later, if at all. Meanwhile a preventive visit due under an annual contract slips, and nobody knows which part went into which unit. The problem is rarely the people; it is scattered channels with no single record.

This guide is for owners and managers of AC and MEP maintenance, facility management, pest control, cleaning, lift maintenance and field IT support companies. It explains what field service management software should do, from the moment a request arrives to the moment the invoice is paid. It is not fleet management software, which is built around the vehicle, its trips, fuel and fines. This system is built around the job, the technician, the customer and the equipment being serviced.

SmartTech Studio builds internal systems for companies in the UAE, Oman and Egypt. We do not sell a packaged product in this category, so this is the checklist we use when we specify such a system with a client. Official sources are listed at the end.

Why WhatsApp groups and spreadsheets stop working

WhatsApp groups and spreadsheets work when a company has five technicians and twenty customers the owner knows by name. As it grows, the same gaps appear: a request lost in the messages, a repeat visit because nobody noted the fault needed a part, a dispute over what was done with no evidence, an annual contract that lapsed, cash collected by a technician and never reconciled. And the owner cannot answer a simple question: which contracts make money, and which consume technicians’ time and parts without enough in return?

The details differ by sector, and the system should reflect them. AC and MEP companies face a summer peak of emergency calls and need a record of every unit and what was fitted to it. Facility management firms run many sites and trades under contracts with service levels and KPIs. Pest control runs on recurring visits, and many customers, food businesses especially, want a report of areas treated and products used. Cleaning runs on teams, shifts, recurring schedules and checklists. Lift maintenance combines periodic visits with breakdown calls that may involve someone trapped inside. Field IT support handles serial-numbered devices under strict SLAs, often resolving requests remotely first.

The life of a job: what the system records at each stage

The heart of any field service system is the job, or work order. Everything else, from the customer, the site and the equipment to the technician, the part and the invoice, hangs off it. The table sets out the stages a job passes through and what the system should keep at each one.

The stages of a field service job and the data each one should leave behind
StageWhat happensWhat the system keeps
IntakeThe request arrives by WhatsApp, a call, the portal or emailCustomer, site, equipment, fault, photos, channel and time received, which starts the SLA clock
TriageSet type and priority, check contract cover, quote if neededJob type, priority, cover, quote and approval
SchedulingChoose the technician or team and the timeTechnician, skill, area and the promised time window
En routeThe technician sets off and the customer is notifiedDeparture and arrival times, check-in location
On siteInspection, repair or maintenanceChecklist, readings, before and after photos, parts and time
Sign-offThe customer reviews the work and signsSignature, name and service report, or why the job stays open, such as waiting for a part
InvoiceThe invoice is issued and payment collectedInvoice lines, VAT, payment method, cash held per technician
Follow-upAsk for feedback and schedule the next visitRating, any repeat of the fault, next preventive visit

Under the job sits a simple but decisive structure: the customer, their sites, and the equipment at each site. A property management company may have many buildings, each with AC units, pumps and lifts, and each unit has a model, a serial number and a location. When every job is linked to the equipment, not just the customer, each unit gets a full history: when it was serviced, which faults recur, which parts were fitted and whether it is under warranty.

Job intake: WhatsApp, calls and the portal in one record

Most UAE customers prefer WhatsApp, and the common mistake is leaving it as a phone in one employee’s hand. Messages should reach the system through the WhatsApp Business API: the job is created from the conversation, the photos are saved on it, the customer gets an instant reply with the job number, and later updates come from the same number using approved templates. The thread stays on the customer’s record.

Calls remain a main channel, especially for emergencies. The receptionist needs a screen that recognises the caller and shows their contracts, sites, equipment and recent visits, then a form that asks the right questions for each job type: which unit, where, is it leaking, is anyone inside the lift. The answers set priority and skill, and spare a wasted visit without the right part.

Corporate customers and facility and property managers prefer the portal, because they raise requests for many sites and want to follow them without calling. Whatever the channel, a request should become one job with the same fields, and the system should flag duplicates when two residents report the same fault in one building.

Scheduling and dispatch by skill and area

An AC technician is not an electrician, lift work needs specific qualifications, and pest control needs trained applicators. So the system starts with a skills matrix per technician, service areas and an estimated duration per job type. The supervisor then gets a drag-and-drop board of technicians and slots, with suggestions for the best fit: who has the skill, who is nearest, who has time inside the window promised to the customer.

Avoid fully automatic dispatch in a first release: the supervisor knows which customer wants the same technician, which site needs a permit, which job needs two people. Let the system suggest and the supervisor decide. Emergencies must fit too: insert the urgent call, reshuffle the day, notify affected customers.

Summer brings a rule the scheduler must know. Under Ministerial Resolution No. 44 of 2022, as published on the official UAE Government portal, work under direct sunlight and in open places is not allowed between 12:30 pm and 3:00 pm from 15 June to 15 September every year, with specific exemptions for work that cannot be postponed. Tag each job type as indoor or outdoor (rooftop outdoor units, outdoor pest treatments and facade cleaning are outdoor), and the system blocks outdoor jobs in those hours during that period while indoor jobs stay available. Check the exemptions with the Ministry of Human Resources and Emiratisation before turning them into a rule.

If you already track your vehicles, the van’s location is a useful dispatch input. Its costs, fuel and fines belong in the fleet system.

The technician app: works offline and proves what happened on site

Technicians spend much of the day where the signal is weak or gone: basement pump rooms, lift machine rooms, underground car parks, service risers. An app that stops when the connection drops sends them back to paper. So the app should hold the day’s jobs, checklists, equipment history and van stock on the phone, save every entry locally, and sync when the connection returns, with clear rules for conflicts if the office changed the job meanwhile.

Photos are the strongest evidence in any dispute: before and after, time-stamped, linked to the job and the equipment. Checklists vary by job type and should be structured fields, not free text: filter cleaned, yes or no; current draw as a number; refrigerant pressure as a number within a range, with a warning outside it. “Unit working fine” tells you nothing six months later.

At the end, the customer reviews a summary and signs on screen with their name, and the service report goes to them at once by email or WhatsApp. If the tenant is out, a link or confirmation code lets them approve it later. The app also records departure, arrival and finish times and the check-in location, so hours and service levels come from data, not memory. Offer it in the language your technicians read best.

Spare parts and van stock

A van is a small warehouse, and the system should treat it as a stock location with its own balance. A part recorded on a job is deducted from the van and added to the invoice if the contract does not cover it. That closes the industry’s biggest gap: parts that leave the store and never appear on an invoice.

When a van part falls below its minimum, the system raises a transfer request from the main store. Valuable parts such as compressors and control boards are tracked by serial number: which unit, which warranty end date, which faulty parts went back to the supplier. If the fault needs a part the technician does not carry, the job moves to “waiting for part” instead of closing, and the second visit is scheduled from the same record. If you already run an inventory system, connect to it rather than duplicate it; see our guide to inventory management software.

AMCs, preventive maintenance and SLAs

The annual maintenance contract (AMC) is a maintenance company’s most stable income and the thing most often run on paper. In the system, a contract holds the sites and equipment covered, preventive visits per year, what the price includes and excludes in labour and parts, the billing schedule and the renewal date. From that, the system generates the year’s preventive visits, which appear on the schedule ahead of time and are dispatched like any job.

When a contracted customer reports a breakdown, the system checks at once whether the equipment is covered and whether the repair is included or chargeable, so the office does not learn after the visit that unquoted work was outside the contract. A set period before expiry, it alerts sales and prepares the renewal offer with the history of faults and visits, the strongest argument for renewal.

Service levels are usually two times per priority: response (arrival or start of work) and resolution. The clock starts when the request is logged, pauses in agreed cases such as waiting for access, and the supervisor is warned before a breach, not after. At month-end the system produces a compliance report per contract.

Invoicing on completion, VAT and e-invoicing readiness

Late invoices delay collection and invite disputes. Build the invoice from the job: call-out fee, labour and parts, less what the contract covers, then VAT at the standard 5% rate. Payment on site, by card, payment link or cash, is recorded on the job, and each technician’s cash is reconciled with what he hands in.

One design decision matters here. The app should not issue a numbered tax invoice while offline, because invoice numbering must be central. The technician closes the job and records what was used, and the invoice is issued by the system on sync, or by the connected accounting system.

Corporate customers add one more step: the UAE is moving to business-to-business e-invoicing. The Ministry of Finance states that PDFs, images, scans and emails are not e-invoices, and e-invoices are exchanged through Accredited Service Providers. Under the current timetable, businesses with revenue of AED 50 million or more go live on 1 January 2027 and smaller ones on 1 July 2027; check your date with our e-invoicing deadline checker. So invoice data must be structured from day one: the customer’s tax registration number, clear lines, tax per line, and a link to accounting or the provider. Our e-invoicing integration guide covers the steps.

The customer portal and notifications

The call a receptionist gets most is “when will the technician arrive?”. Automatic notifications answer it first: request received with its number, the technician’s name and time window, “on the way”, the service report on completion, then the invoice and payment link, by WhatsApp, SMS or email, in Arabic or English as the customer prefers.

The portal matters most to corporate, property and facility management clients. They raise requests for all their sites, follow status, see the history of every site and unit, download reports and invoices, and view upcoming preventive visits and SLA compliance. Follow-up messages drop, and the monthly report becomes a formality.

The reports an owner actually needs

With all this on the job, reports come free. Operationally: open and closed jobs by type and area, first-time fix rate, how often the same fault returns to the same unit within a period you set, SLA compliance per contract, and each technician’s working time against travel and waiting.

Financially: revenue and margin by job type, contract and technician; parts issued against parts invoiced; completed jobs not yet invoiced; amounts not yet collected; and contracts due for renewal in the coming months. These figures answer the owner’s opening question: which contracts make money, and which drain the team.

Build or buy?

Packaged field service systems sell as per-user monthly subscriptions, and some are good. The question is which fits the way you work. Here is how the options compare.

Off-the-shelf versus custom field service software
FactorOff-the-shelf subscriptionCustom system
Time to startDays or weeksTypically 8 to 16 weeks for a focused first release
Fit to your workflowThe company adapts to the systemBuilt around your contracts, checklists and service levels
Arabic and right-to-leftVaries; often partly translatedFull Arabic and English throughout
IntegrationWhatever APIs the vendor offersDirect links to accounting, ERP, WhatsApp and e-invoicing
CostA per-user subscription that grows with your teamAn upfront build from AED 25,000 excl. VAT, then hosting and support
DataHeld by the vendor; export on its termsYours, on servers you choose

Our rule: if your operations follow the general pattern and your team is small, start with an off-the-shelf system. If your contracts, service levels and reports are what set you apart, or a packaged system forces side spreadsheets to fill its gaps, consider custom. See our comparison of custom and off-the-shelf systems.

When we build an internal system like this, our custom systems start from AED 25,000 excl. VAT, and a focused system typically takes 8 to 16 weeks. We recommend a first release covering the backbone: intake, dispatch, the technician app and invoicing on completion. AMCs, the portal, van stock and the e-invoicing link follow in later phases, with e-invoicing brought forward if your date is close. The price depends on modules, integrations and data migration.

Sources

FAQ

Does the technician app work without an internet connection?

It should. A good app carries the day’s jobs, checklists and equipment history on the phone, saves photos, readings and signatures locally, and syncs them when the connection returns. The tax invoice number is issued centrally after the sync, not by the phone while it is offline.

What is the difference between an AMC and preventive maintenance in the system?

The AMC is the commercial agreement: the equipment covered, the price, the cover and the renewal date. Preventive maintenance is the scheduled visits the system generates from that contract over the year. The system also uses the contract to decide whether a breakdown call is covered or chargeable.

How should the scheduler handle the summer midday work ban?

Tag each job type as indoor or outdoor, and the system blocks outdoor jobs between 12:30 pm and 3:00 pm from 15 June to 15 September, under Ministerial Resolution No. 44 of 2022. Indoor jobs stay available, and exemptions should be checked with the Ministry of Human Resources and Emiratisation.

How much does a custom field service management system cost in the UAE?

At SmartTech Studio, custom systems start from AED 25,000 excl. VAT, and a focused system typically takes 8 to 16 weeks. The price depends on the modules, the integrations with accounting, WhatsApp and e-invoicing, and the data to be migrated.

Can it connect to the accounting software we already use?

Usually, yes, if the software offers an API or a reliable import method. Invoices, payments and customers flow into it, while the job stays in the field service system. We confirm this during analysis, before we fix the price.

العربية