Skip to content
FSM

Keeping customers happy starts with optimising your planning

•

9 min leestijd

Customers stay happy when the technician arrives within the agreed time window and within the response time in their contract. That takes appointments your schedule can support, fixed rules for emergencies and service level agreements (SLAs), and an honest arrival time.

For an installation or service company with maintenance contracts, the rules decide: how SLA deadlines count, which appointments you offer and who may deviate.

Why doesn’t the day plan hold?

Usually because it rests on assumptions that turn out wrong in the field. Planners will recognise these problems:

  • The previous job overruns, and the next time window slips.
  • An urgent breakdown comes in, and the rest of the day has to change.
  • An SLA deadline passes unnoticed, and a penalty or an unhappy customer follows.
  • Customers phone to ask when the technician will arrive.
  • Only one planner knows what takes priority. When they are away, things go wrong.

Our article on service staff productivity explains what field service management (FSM) changes for a technician who searches on site or has to come back.

How far ahead do you plan service work?

Across four horizons that build on each other, as IFS explains in its piece on multi-time horizon planning. The strategic (3 to 12 months) and tactical (0 to 6 months) horizons cover capacity, shift patterns, skills and contractors.

For your customer promise, the other two count. Preventive visits under a maintenance contract belong on the operational horizon, 0 to 4 weeks ahead. A phone promise after a breakdown rests on the real-time horizon (0 to 14 days).

If you run IFS Cloud with IFS Planning & Scheduling Optimization (PSO), each scheduling dataset sets how many working days the engine schedules in detail. Later days are scheduled faster but less precisely; IFS’s example is five detailed days, then ten more. You choose those limits, and they set how far ahead an offered window rests on a detailed schedule.

How do SLA deadlines decide which job goes first?

Through the latest start and finish time of each work task. According to IFS, a service contract sets a response time and a resolution time per priority, criticality or both. From these, IFS Cloud calculates an SLA Latest Start and SLA Latest Finish for each work task under that contract.

If you handle requests in IFS Cloud (Request Management), an SLA template is applied automatically to each new request. It comes from the warranty, the request contract line or the service. The urgency your service desk selects can therefore decide which deadline starts running.

With those SLAs, check the calendar. IFS Cloud counts hours and minutes only within the working hours of the SLA calendar. A cut-off also excludes the end of the working day.

In IFS’s example, the working day ends at 17:00 with a one-hour cut-off. A call logged at 16:02 then counts from the next working day. If you promise out-of-hours breakdown cover, check that the SLA calendar counts those hours as working time.

For each SLA template you set whether it drives automatic scheduling, and whether only the start or the whole job must fall within the deadline. People decide: you choose which priorities, deadlines and calendars go into your contracts.

How do you book an appointment you can keep?

By offering only time windows the schedule has checked. With PSO, the planner books through the Appointment Booking Engine. Based on the technicians available, it decides for each window whether it can be offered.

For each offer, the planner sees whether it meets the SLA. If they still pick a window outside the SLA, IFS Cloud asks for a reason code and logs it.

Two choices are yours, starting with the type of appointment. With ‘Appointment to Start’, only the start has to fall within the window; with ‘Appointment to Complete’, the whole job must fit. That decides what a customer can expect from ‘between 8 and 12’.

The second is who may enter an appointment by hand. An Override Appointment bypasses the engine, so the system does not check whether a technician is free then.

What do you do when an emergency comes in?

Decide in advance what takes priority, so the planner does not have to choose again with every breakdown. In IFS Cloud you weight the work task’s priority, the equipment’s criticality and the service contract type. With continuous scheduling, IFS says the engine reshuffles the rest of the day as soon as a critical job comes in.

A booked appointment stays within its chosen window, because IFS restricts the job to that window once it is booked. PSO leaves work already committed to a technician as it is. If a window slips anyway, agree who phones the customer, and after how many minutes.

The engine proposes; your planners decide when an exception, contract or customer promise outweighs the maths. Eqeep sets up these planning rules and priorities with your planners. That puts them in the system, not just in one planner’s head.

Our article on AI in operational planning and our IFS PSO page explain how an optimisation engine makes that trade-off.

How does the customer know when the technician will arrive?

Because the technician shares an expected arrival time and the planner sees it. In IFS Cloud, technicians set their assignment to On Route when they leave. If the action is enabled in the workflow configuration, they can also send an expected arrival time.

The planner sees that time in the Dispatch Console, and with PSO the scheduling engine moves the start of the job to match. The planner can then call the customer before the customer calls. With omni-channel customer service, customers can also see order information themselves.

What data does a reliable schedule need?

For your customer promise, two things above all: the location of the job and the times your technicians report. Without valid coordinates on the task, and on the technician’s or company address, you cannot book an appointment through the engine.

Ask technicians to report start and completion straight away, because the schedule builds on those times. If this data is unreliable, optimisation only makes poor decisions faster.

A technician with twenty addresses in a day only keeps to the time windows with a realistic route. Our article on AI in operational planning covers the data a scheduling engine needs for that, such as durations, skills and travel times.

A technician without the right part has to come back. Our guide to parts and inventory management covers service stock.

Where should you start?

With one measurable issue, such as missed windows or expired SLA deadlines. Eqeep agrees the priority and baseline with your team before choosing the first process to change. A sensible order:

  1. Measure for a while how often you miss windows and deadlines, and why.
  2. Set the rules: priorities, the calendar for each SLA and who may enter appointments by hand.
  3. Clean up durations, skills, coordinates and shifts.
  4. Then let a scheduling engine make proposals, and compare them with your baseline.

Engine-checked appointments and arrival times in the schedule both need IFS PSO.

Want to know where your schedule misses appointments today? Start with an analysis.

Questions about service planning and SLAs

What is the difference between response time and resolution time?

Response time runs until the work must start; resolution time until it must be finished. In an IFS service contract, both count from when the task is entered or, for consecutive tasks, from when the previous one is finished.

What happens to the SLA deadline if the customer is unavailable?

The deadline can be paused, but not with a single button. For SLA commitments in Request Management, IFS Cloud has APIs to pause and restart the clock for an unplanned interruption, such as an absent customer. For a planned interruption, you extend the due date. Agree in the contract when that is allowed, and how your service desk does it.

What should you look for in the scheduling functions of FSM software?

An installation or service company with maintenance contracts should test three scheduling points in FSM software. They are how it calculates an SLA deadline, whether appointments are checked against available technicians, and how an emergency re-plans the day. Ask to see all three in a demo with your own work. Our IFS Field Service Management page shows how IFS connects the chain from customer call to invoice.

Tell us where you stand with IFS. After one conversation you will have a clear next step. Mention the customer promise you miss most often today. Discuss your IFS question.