How to manage a field service team: work orders, routes, and reports

Example scenario: Picture a pool installation and maintenance company in Antalya. All summer the crew goes to villas, hotels, and residential complex pools. One customer writes on WhatsApp that the pump is making noise, a hotel is waiting for its scheduled maintenance, and the handover of a new villa pool is near. It is all in the same crew's day.

Field service management gathers these jobs into one list. The request comes in, a work order opens, a technician is assigned, the job is done, the report is entered, and the customer record is updated. If one link stays on paper or on a phone, the whole chain slows down.

Service work also repeats. The same address comes back every season, sometimes every month. Each visit builds on the one before; without a record of the last visit, every job starts from scratch.

This is where sales and service meet. The team that sold the pool hands the customer to service after handover; if the service record stays where sales cannot see it, renewal and add-on opportunities stay there too.

• Customer and address: taken from the customer card, not typed again.
• Job description: repair, maintenance, or installation, in the customer's own words.
• Owner: the technician or crew doing the job.
• Date: the planned day and the promised completion.
• History: records of earlier service at the same address.
• Materials: the parts and equipment to load in the van.

When the Antalya customer's message lands on the card, the technician sees last summer's maintenance note for that pool before setting off. If the same pump was replaced before, that fact sits on the card, not in someone's head on the road.

The wording of the work order matters too. A work order that says pump fault tells the technician little; the customer's own sentence saying it rattles when it runs at night tells much more. Recording the customer's own words keeps the crew from setting off with the wrong part. A second trip to the same address always costs more than writing the work order properly.

A service route breaks faster than a sales route. At noon a breakdown drops in between the maintenance jobs planned that morning. If the breakdown is urgent, a maintenance visit is postponed, and that customer has to be told.

What gets lost most often here is telling people. The technician changes the order, the office does not know; the customer waits, calls, and gets annoyed. When the order changes, recording the change matters more than the order itself.

For the Antalya crew a summer day goes like this: the field lead checks the day's list, moves a maintenance visit to the next day to fit in the noon breakdown, and leaves a note so the postponed customer is told. The order changes, but the record knows about the change. Map tools can be used to work out the driving order; what counts here is not the calculation itself but getting the change on record.

When the day ends, the technician comes back to the office and writes up every job from memory. Which valve was changed, what the customer said, the reading that was taken; some of it is forgotten. The photos stay in the phone's gallery among other pictures. A report written on site also helps with the customer. When the technician finishes and takes the photo, the work is documented; if a dispute comes up later on the same matter, the answer is on record.

In Corex360 the report is entered on site, from the phone. The technician adds the photo and note from the iOS or Android app; the report is tied to the project and the customer card, and the photo is kept inside the record in Corex Drive. We tell the whole day hour by hour on the field and operations page.

The maintenance contract is signed, the first service is done, and then the calendar is left to one employee's memory. When that employee leaves, the service dates leave too. Nobody remembers until the customer calls.

The question to ask when writing a rule is simple: whose head is this job living in? If the hotel pool's service date is in the diary of someone in accounting, that diary entry should become a rule.

The maintenance calendar is born with the contract. If the service interval is written into a rule on the day of signing, each visit opens as a task when its time comes, and remembering the calendar stops being anyone's personal job.

In Corex360 X AI follows rule-bound work. If a delivery date nears and the step is still open, a task opens for the owner and the matter goes into the morning briefing. The maintenance contract's start and end dates sit on the contract card; an example with seasonal maintenance is in service at pool and spa firms.

The service manager does not ring the crew one by one in the morning. Yesterday's closed jobs, the missing reports, and projects near handover are on one list. Sales sees the same progress on the customer card and does not call service to ask how the job is going. As general good practice, a good schedule for the service manager should also show which technician's week is full and at which address the same fault keeps coming back.

This visibility also changes the conversation with the customer. Whoever picks up the phone sees what was done at the pool's last service, with the photo, and the customer does not have to explain everything again on every call. We gathered what field crews ask most on the mobile app questions page.

In Corex360 the service report is entered on site, from the phone: the technician adds the photo and note from the iOS or Android app, the report is linked to the project and the customer card, and the photo is stored inside the record in Corex Drive. The maintenance contract's start and end dates sit on the contract card; if the due date approaches and a step is still open, X AI opens a task for the owner and brings the issue to the morning briefing.

The vehicle tracking system connects to the Corex360 core, and vehicles are kept with their make definitions. Task management counts open, overdue and completed tasks and warns about tasks at risk; a task can wait for approval and gets an automatic code. Customer support tickets are tracked on their own screen in the CRM. Product warranty periods are tracked. The field team connects to the same core through the iOS and Android apps.