Why generic booking tools fail in field service
A slot is not free because the office is open. It is free only if someone who covers that postcode, does that job type, is working that day and is not already booked, with enough travel time to get there.
Publish a calendar that ignores any of those and the office spends its morning undoing bookings.
What availability has to know
- Postcode or region to crew coverage
- Skills and certifications matched to job type
- Travel time between jobs, not just the location list
- Existing jobs from the planner, consumed in near real time
- Job duration by type and property size, not a fixed hour
Two-way, not one-way
Jobs the office creates in the planner must consume website capacity too, or you will double-book. That is more work than a one-way push and it is the difference between a system people trust and one they work around.
In the Danish ventilation-cleaning build we delivered, a change made in the route planner appears on the website within about five minutes. Anything slower and the office stops trusting the calendar.
A real deployment
We built a custom WordPress plugin for a Danish field-service company on the site they already had. The customer's address resolves to the crews who actually cover it, the calendar offers only slots those crews can serve, and the confirmed job appears on the right route without anyone touching a keyboard.
Booking moved from office hours to round the clock, two manual entries per booking became zero, and the live planner account with 5,400+ jobs stays in step.
Letting customers change their own appointments
A signed link in the confirmation email that lets a customer move or cancel within your rules removes a surprising volume of inbound calls, and captures the change in the system rather than on a sticky note.
The rules should mirror what you already do informally rather than inventing new policy.