Technician scheduling software: from WhatsApp to a dispatch board

Short answer: what technician scheduling software should do

Technician scheduling software puts every service job on one board, lets a dispatcher assign it to the right technician in a couple of clicks, and sends the job to that technician's phone with the address, fault, parts and customer history. The customer gets an automatic confirmation and an "on the way" message.

If you have up to about fifteen field staff and standard jobs, a tool such as Jobber or Housecall Pro does this well. If scheduling depends on parts in an ERP, manufacturer warranty rules or technician skills per brand, a custom dispatcher dashboard is worth considering.

Why phone calls and WhatsApp stop working

The WhatsApp group is where most service companies start, and it is fine with three technicians. The trouble starts around the fifth. Messages scroll away, photos of job sheets get lost, and the dispatcher becomes a human switchboard.

Common symptoms:

• Technicians call the office to ask for the next address or the customer's phone number.
• Two technicians drive to the same customer, or none does.
• A job waits for a part, but nobody reschedules it when the part arrives.
• Customers ring to ask when the technician will come, and the office does not know.
• At the end of the month nobody can say how many visits each technician did.

Every one of these is a scheduling problem, not a people problem. The information exists, it is just scattered across phones.

Options: calendar, field service tool or custom dispatch board

Option	Good for	Breaks when	Typical cost
Shared Google or Outlook calendar plus WhatsApp	1–3 technicians, simple jobs	You need status, parts or job history	Already paid for
Jobber or Housecall Pro scheduling	2–15 technicians, residential work	Jobs depend on ERP stock, warranty rules or brand-specific skills	Jobber from $49/month (1 user), Grow $299/month for 5 users; Housecall Pro Essentials $189/month for 5 users (monthly billing, October 2026; see Jobber and Housecall Pro pricing)
ServiceTitan dispatch board	10+ technicians, HVAC, plumbing, electrical with call centres	Small teams, budgets under several thousand dollars a month	Quote only; third-party estimates about $250–$500 per technician per month1
simPRO scheduling	Installation and maintenance contractors	Quick-call-out residential work	Quote only2
Custom dispatcher dashboard	Repair centres, installers, multi-brand warranty work	Your process is standard and a subscription already fits	Fixed quote after discovery

Be honest about which row you are in. A custom board is not better scheduling software in general; it is better only when it can see things a generic tool cannot, such as whether the part has arrived in Business Central or whether this technician is certified for this manufacturer.

What a good dispatcher dashboard shows

Whatever you buy or build, check that the dispatcher can see all of this on one screen:

• Unassigned jobs, sorted by priority and promised date.
• Each technician's day as a timeline, with travel time between jobs.
• Job status: booked, confirmed, on the way, on site, waiting for parts, done, invoiced.
• Parts status for each job (ordered, received, reserved).
• Technician skills or brand certifications, so a warranty job goes to someone allowed to do it.
• Location of jobs on a map, so nearby visits can be grouped.
• Customer history for the address or device: previous visits, warranty status, notes.

And the technician's phone should show, for each job: address with a map link, customer contact, fault description, parts to take, a checklist, photo upload and a customer signature. If any of these lives outside the app, technicians will keep calling the office.

Step by step: moving from WhatsApp to a dispatch board

1. Agree the job statuses. Write down the six to eight statuses a job passes through and what triggers each change. This list becomes the backbone of the board, whichever tool you choose.
2. Decide who books and who dispatches. In small teams it is one person; in larger ones booking (phone, web form, email) and dispatching are separate roles.
3. Put every new job into the system first. No job exists until it is on the board. This one rule removes most of the chaos.
4. Give technicians the app and remove the alternative. Run both in parallel for a week, then stop sending job details on WhatsApp.
5. Automate customer messages. Booking confirmation, a reminder the day before, and "technician on the way" with an estimated time. This alone cuts inbound calls noticeably.
6. Handle the parts loop. When a job is waiting for parts, it should reappear on the unassigned list automatically when the part is received, not when somebody remembers.
7. Review weekly. Look at jobs per technician, first-time fix rate and jobs waiting more than three days. Adjust the rules, not just the people.

Scheduling rules that work in practice

Software only follows the rules you give it. These are the ones that make the biggest difference for repair and installation teams:

• Book time windows, not exact times. Promise the customer "between 8 and 12" or "between 12 and 16", then send a precise arrival time once the technician is on the way. Exact appointment times guarantee late arrivals after the first overrunning job.
• Estimate duration per job type. A filter clean is not a compressor replacement. Keep a default duration for each job type and adjust it every quarter from real data.
• Keep emergency capacity. Leave one slot per technician per day, or one technician per area, unassigned until the morning. Urgent jobs then go in without moving five other customers.
• Match skills and certifications. Warranty work for a given manufacturer often requires a certified technician. The board should only offer technicians who are allowed to do the job.
• Group by area. Split your region into zones and try to keep each technician in one or two zones a day. This simple rule often saves more driving than automatic route optimisation.
• Generate recurring maintenance automatically. Annual boiler services, filter changes and inspections should appear on the board as jobs weeks in advance, not depend on someone's memory or a spreadsheet.
• Confirm the day before. An automatic reminder with a reply option catches cancellations while you can still fill the slot.

Write these rules down before you configure any tool. They are also the core of the specification if you later decide to build your own.

Common mistakes we see: booking jobs into fixed hour slots when real jobs vary from 20 minutes to half a day; letting technicians change their own schedule without telling dispatch; and ignoring travel time, which makes every afternoon run late.

Manual vs automated scheduling: the hours you get back

Time a normal week and fill in your own figures. The example below is for a team of eight technicians doing about 30 visits a day in total.

Task per day	Manual (minutes)	With a dispatch board (minutes)	Saved (minutes)
Planning tomorrow's routes	60	20	40
Calling or messaging technicians with job details	45	5	40
Answering "when will the technician arrive?" calls	40	10	30
Rescheduling jobs waiting for parts	30	10	20
Collecting job sheets and typing them in	45	5	40
Total	220	50	170

Your calculation:

1. Minutes saved per day: ____ (example: 170)
2. Working days per month: ____ (example: 21)
3. Hours saved per month = minutes × days ÷ 60 = ____ (example: 170 × 21 ÷ 60 ≈ 60 hours)
4. Hourly cost of the dispatcher or office staff: ____ (example: €18)
5. Monthly value = hours × cost = ____ (example: 60 × €18 ≈ €1,080)

Add a second line for technicians: if better routing saves each of them 20 minutes of driving a day, eight technicians gain around 56 hours a month, often enough for several extra paid visits. These are illustrative numbers; your own will differ, so measure before you buy.

What does it cost?

For a subscription tool, the cost is the plan price times the number of users, plus any route optimisation or SMS add-ons. Check whether the per-user price applies to office staff as well as technicians.

For a custom dispatcher dashboard, it normally comes as part of a wider service system rather than on its own, because scheduling is only useful when it knows about jobs, parts and customers. Our estimate of market prices for a first phase covering booking, scheduling, the technician view and invoicing is €20,000–€45,000, depending on integrations. That is a range, not a quote.

At Raao the path is the same for every custom project: a free 30-minute call to see whether you need custom software at all (book it here), then a paid discovery workshop that produces a written specification and a fixed quote per phase, then a phased build starting with the core. There are no per-user licence fees, so adding technicians later adds no licence cost.

If you are still deciding between buying and building the whole system, read our comparison of field service management software for small business first.

How we did it for Transilvania Service

ServiceCore, the system we built for the appliance service company Transilvania Service, handles scheduling as part of the whole repair flow:

• A dispatcher dashboard, visit calendar and a daily view for each technician.
• Online booking and public repair tracking on the company's website, feeding jobs straight into ServiceCore through an API.
• Parts ordering, receipts and stock synced with Business Central, so the office sees whether a job can go ahead.
• Automatic email and SMS updates to the customer at every step of the repair.
• Stock and technician performance reports for management.

Customers are informed automatically, and the team works from one system from online booking to fiscal receipt.