Appointment booking
Every appointment is offered against an estimate
Every appointment you offer is a promise. Now you can see the capacity behind it before you make it.
The challenge
Every appointment is offered against an estimate
When a customer is offered an appointment window, a commitment has been made. Someone will rearrange their day around it. In many markets, a regulator is counting.
For years, that commitment was made against a booking grid. A fixed number of appointments per slot, per day, set in advance by someone doing their best with the information available. It was an estimate, written down weeks before the day it governed, and nobody found out whether it was right until the day arrived.
That single fact produces two opposite failures, and they have the same cause.
Promise more than the day can hold, and the appointment cannot be kept. A customer waits for a technician who was never going to arrive. A visit is rebooked, a truck roll is wasted, a complaint is filed, and in a regulated market the exposure is measurable.
Promise less than the day can hold, and slots sit empty. Technicians finish early with hours nobody can account for. Customers were turned away for capacity the operation actually had, and no one ever knew.
What that costs, every week:
- Appointments are offered against estimated capacity rather than real capacity, so the promise is only as good as the estimate
- Missed and rebooked visits generate a second truck roll, a customer complaint, and regulatory exposure
Unused technician time is invisible, so under-used capacity is never recovered and revenue is quietly left on the table - Adjusting a grid means rebuilding it, so planners tolerate a grid they know is wrong rather than face the work of changing it
- Nobody can see the coming week’s saturation until it becomes this week’s problem
The deeper issue is that the plan and the promise were never the same thing. The booking grid described what someone hoped the operation could absorb. The daily plan described what it was actually doing. Between those two sits every broken appointment.
The solution
Every appointment backed by real crew capacity
Booking capacity is now derived from the resources you actually have. Instead of a fixed number entered in advance, the grid reflects the technicians available in that zone, on that day, with the right skills, in the shifts they are working. When a slot is offered to a customer, it has already been checked against the real plan, the real people, and the travel time required to get there.
Booking is exposed through APIs, so the request comes from wherever your customer already is, your contact center, your CRM, or your self-service channel. There is no new portal for anyone to adopt. The window your customer hears is validated by your operation before it is offered.
And for the first time, the planner can see the capacity before committing to it.
What makes it work:
- The booking capacity, built from real resources rather than fixed numbers entered in advance, so it reflects the operation rather than an estimate of it
- Slot validation before the offer, against the technicians available, their skills, their calendars, and the travel time to reach the site
- The saturation monitor, showing what is taken and what remains at slot level, by zone or across the whole operation center
- The resource utilization view, showing technician availability, work time, travel time and, critically, unused time, so capacity going to waste becomes visible and recoverable
- Forward booking simulation, running often on the same logic as live booking, so the picture a planner works from is what the engine will actually encounter rather than a projection
- Day-level adjustment without rebuilding the grid, and the ability to duplicate a working period rather than recreating it
- Territory and zone awareness, so capacity is planned where the work actually is
- API-first delivery, so booking fits the channel your customers already use
Purpose-built for the scale and complexity of linear asset industries
Electric utilities
A meter replacement program runs across a metropolitan area with different technician density in every zone. Capacity is calculated per zone from the crews actually assigned there, so the appointments offered in a dense district and a sparse one both reflect what can genuinely be delivered.
Gas and water distribution
A safety inspection requires access to the property, which means the customer has to be home. Every window offered is checked against a technician who can reach the address in time, so the visits that are booked are the visits that happen.
Telecommunication
Installation appointments compete with fault response for the same engineers. Saturation and utilization are visible together, so the planner can see where the week is genuinely full and where there is room, before the contact center offers a slot that cannot be met.
New connections and planned access
The two appointment types behave differently. A new connection is a milestone the customer is waiting on, often with a contractual date attached. Planned access is routine, high volume, and depends entirely on the customer being home. Capacity for both is calculated from the same real resources, so a surge in connection work is visible in the access capacity before it becomes a wave of missed visits.
Benefits
Fewer missed visits, more capacity recovered
Fewer broken appointments
A slot is offered only when the capacity behind it has been validated, which reduces missed visits, second truck rolls, and the complaints and regulatory exposure that follow them
Recovered capacity
Unused technician time becomes visible for the first time, so under-used days can be filled rather than quietly absorbed
Problems seen before they arrive
Saturation is visible for the days ahead, so the coming week’s bottleneck is a planning decision rather than next week’s escalation
Less effort to plan and maintain
Days can be adjusted and working periods duplicated without rebuilding the grid, so planners spend their time on the exceptions
No new channel to adopt
Booking works through the systems your customers already use, so the improvement reaches them without a migration
One version of the truth
The capacity the customer is promised and the plan the operation runs on are the same picture