A field service business sends people to customers' premises. A heating engineer, an electrician, a lift maintenance firm or a drainage team may take a call in the morning, quote in the afternoon and return to the same site weeks later for a planned service. The work is local, practical and repeated, and the customer usually cares most about one thing: that someone arrives when promised and fixes the problem properly.
Trades firms often run on a diary, a mobile phone, paper job sheets and a shared inbox. That works for a small team with a steady flow of work. As the number of engineers, contracts and sites grows, the gaps show up as missed reminders, repeat visits for the same fault and engineers arriving without the history they need. A CRM for field service businesses brings the customer, the site and the job history into one record.
This article covers enquiry triage, the move from enquiry to job, quotes for on-site work, service contracts and planned maintenance, reminders, engineer notes and the measures that show whether the system is working. It is written for owners and office managers who want fewer dropped jobs and more repeat work from customers they already serve.
Field service triage: sorting enquiries into the right kind of job
The first reply a customer gets often decides whether the job is booked. Sorting each enquiry at once means the right person responds in the right time frame.
Emergency, urgent, planned or quote
Not every enquiry needs the same response. An emergency callout, an urgent repair, a planned service and a request for a quote each need a different timeline, a different level of detail and a different owner. Build a short triage step into the first contact, so the office can classify each enquiry straight away. That classification drives the first reply the customer receives and the time it is due.
A simple triage set looks like this:
- Emergency: a safety risk or a loss of essential service that needs attention now
- Urgent: a fault that stops the premises working, without an immediate risk
- Planned: an agreed service, inspection or renewal already on the calendar
- Quote: work the customer wants priced before anything is booked
Capturing what the engineer will need
A good enquiry record saves a second phone call. Capture the site address and any access arrangements, such as a key holder, a gate code or a parking restriction. Record the fault in the customer's own words, along with any photographs they can send. Store access details against the site rather than in general notes, and limit who can see them.
Ask, too, whether the customer needs notice before a visit or has pets on site. Those details change how the engineer arrives, and they belong on the job rather than in the engineer's memory.
From enquiry to booked job
An enquiry is a conversation, and a job is a commitment. Keeping them as separate records makes it clear which requests have turned into work.
The office should also be able to see which jobs are waiting for a date, and why, so that nothing sits in limbo for longer than it should.
Turning an enquiry into a job record
The job should be a record of its own, linked to the customer and the site, with a status, an owner, a required date and the type of work. The enquiry stays linked for history. That separation matters because one customer may raise several jobs over the years, and each job needs its own time, parts and sign-off. Avoid turning every phone call into a job, which fills the diary with requests nobody has confirmed.
A job record should carry:
- Customer, site and access notes
- Type of work and urgency level
- Assigned engineer and arrival window
- Parts required and their status
Booking, confirming and rebooking
A booked job should show the engineer, the arrival window, the customer's confirmation and any change made since. If a visit moves, record the reason and tell the customer the same day. Jobs that cannot be booked within the agreed time should go onto a short list for the office to chase, rather than sit unnoticed in a spreadsheet.
Quotes for on-site work that get approved
Quoting on site is where small firms can lose work without noticing. A quote needs a home in the record from the moment it is written.
Writing the quote while the problem is still in view
Quotes are often prepared after a visit, once the engineer has seen the problem. The CRM should let the engineer or the office record the scope, the materials, the approach and any options in a structured way, then send the quote with the job linked. A quote that sits in a van or a notebook is a lost sale. Once the customer approves, the quoted work carries across to the job, along with the parts list.
Photographs taken during the visit make a quote easier to approve, because the customer can see the problem being fixed and the reason for each line.
Approval, follow-up and declined quotes
Set a clear next step for every quote: the date it was sent, the date a reply is expected and the person who will follow up. Record the reason when a quote is declined. Repeated reasons, such as timing or scope, point to a problem in how quotes are presented. Approved quotes should be easy to find when the engineer returns to site.
Reasons for a declined quote worth recording each time:
- Timing, with the customer wanting the work later or not at all
- Scope, where the customer wanted less or something different
- A comparison with another supplier
- No response after the agreed follow-up
Field service contracts and planned maintenance
A service contract turns a one-off job into a relationship with a known rhythm. The record needs to show what was agreed and what is due next.
It also changes the conversation with the customer. Instead of a call only when something breaks, the office can talk about the next planned visit, which tends to be a calmer and more useful conversation for both sides.
Recording what the contract covers
A service contract is an agreement to visit a site at set intervals, often with cover for certain repairs or a faster response. The CRM should record which equipment the contract covers, the visit frequency, what is included and what is charged separately. Keep the terms on the record, so the office does not rely on memory for what was agreed.
Building the visit schedule from the contract
Each contract should generate planned visits automatically, with the next due date visible on the customer and the site. The schedule shows what is due in the coming weeks, which engineer is best placed to attend and where visits cluster geographically. When a visit is missed or deferred, record the reason so the contract history stays accurate.
What a contract record should show:
- Customer, site and the equipment covered
- Visit frequency and the next due date
- Work included, and work charged separately
- Start, renewal and end dates
- Account owner and the engineer who usually attends
Reminders that customers and engineers can rely on
Reminders are simple, but they are where repeat work is most often won or lost. Each one should be specific, timely and owned by someone.
Reminders for service, renewal and follow-up
A reminder can prompt a planned service, a contract renewal, a follow-up on a declined quote or a check that a repair has held. Each reminder needs a named owner and a due date, and its text should be specific enough to be useful. A message that names the equipment and the last visit does far more than a general note to book a service.
A reminder sent on the day of a visit, with the engineer's name and the arrival window, does more to reassure a customer than one sent a month earlier.
Reminders that do not become a nuisance
Customers tire of messages quickly, especially when a reminder repeats after the job is booked. Stop reminders once the job is in the diary, and leave a sensible gap between prompts. Use the channel the customer has chosen and make it easy to reply. The same discipline applies to engineers: an arrival reminder should show the job that matters, not a list of everything on the day.
Engineer notes that help the next visit
Engineer notes are often the most valuable and most neglected part of a field service record. A little structure makes them useful to whoever attends next, including the engineer who wrote them.
Structured notes, not only free text
Free text is fine for the story, but the next engineer needs the structured parts first: what was found, what was done, which parts were used, what was left for later and whether the customer signed off. Give the job sheet a few fixed fields, then leave room for the narrative.
A job close-out note should cover:
- The fault found and its likely cause
- Work completed and any work still outstanding
- Parts fitted, and parts ordered for a return visit
- Safety checks carried out, where the job requires them
- Customer sign-off and any follow-up they asked for
Photos, access changes and personal details
Photographs of the installation, the meter or the fault often help the next visit more than a paragraph of text. Store them on the job or the site, and check that they show equipment rather than people or personal belongings. If an engineer learns that access has changed, such as a new key holder, update the site record straight away rather than leaving it in the job notes.
A short note written at the end of the job, while the details are still fresh, is worth more than a longer one written the next day from memory.
FAQ
What is a CRM for field service businesses?
It is a customer and job system for firms that send engineers or technicians to customers' premises. It holds the enquiry, customer, site, job, quote and service history in one record. Office staff and engineers see the same information, which cuts down on repeat calls and missed follow-up.
Can a CRM schedule engineers?
Some CRMs include a scheduling view, but the depth varies a great deal. Check whether the system shows engineer availability, arrival windows and travel between jobs, and whether it can send confirmations to customers. If scheduling is complex, a dedicated field service tool may sit alongside the CRM.
How are service contracts recorded in a CRM?
The contract sits against the customer and the site, with the covered equipment, visit frequency, renewal date and what is included. The CRM generates planned visits from the contract and shows what is due. Missed or deferred visits are logged with a reason, so the history stays accurate.
What should an engineer's job note include?
Keep a few fixed fields: fault found, work done, parts used, outstanding work and customer sign-off. Add a short narrative for anything the fields miss, and photographs where they help the next visit. Access changes belong on the site record, not only in the job.
How can a field service firm reduce repeat visits?
Record the fault, the work done and the parts fitted in a structured way, so the next engineer can see what happened before. Review repeat callouts for the same equipment at the same site, because they often point to a recurring cause. Bring the engineers into that review, since they usually see the problem first.
Is a CRM worth it for a small trades business?
It can be, once enquiries, quotes and repeat work are being lost or handled inconsistently. A small firm may start with enquiries, jobs and reminders, then add contracts and scheduling later. The cost depends on the number of users, the level of scheduling needed and how many systems must connect.
Final thought
A CRM for field service businesses earns its place when it keeps the customer, the site and the job history together. Enquiries are sorted at once, quotes are followed up, contracts generate visits, reminders go out at the right time and engineers arrive knowing what happened last time.
Start with the enquiry, job and reminder basics, then add service contracts and scheduling once the team trusts the record. Agree who owns each reminder and each set of notes before the system goes live, because unowned tasks are the ones that get lost.
In London, Mirex Agency is a senior-led digital agency that builds CRM solutions for UK trades and maintenance firms that want fewer missed jobs and more repeat work. The CRM solutions page at mirexagency.com/services/crm-solutions outlines how we approach it, and hello@mirexagency.com is a sensible first contact.
