PR-3689 · Live
Demand Pulse
Demand Pulse forecasts service demand one to two weeks out using weather data, historical trends, and current booking velocity, and tells the Dispatcher how much schedule space to hold for service versus maintenance. When the schedule has room left, maintenance outreach goes out to eligible customers automatically to fill it. As bookings land and conditions shift, the forecast updates and the outreach adjusts so service and maintenance capacity stay in balance. The Dispatcher comes into each planning cycle with the split already worked out, by geography, instead of a blank board.
The promise
The Dispatcher stops guessing how much capacity to hold and stops scrambling to fill the gaps at the last minute. The forecast is already there when they open the board. The maintenance outreach has already gone out for the open slots, so they review what came back. When the spike comes in, the capacity is ready, and the schedule holds through the week.
How it works
The path from input to value.
- 01
Demand is forecast one to two weeks out
Demand Pulse pulls weather data, historical service trends, and current booking velocity to build a demand forecast for the upcoming one-to-two-week window.
- 02
Capacity guidance is provided
Based on the forecast, the Dispatcher sees clear guidance on how much schedule space to reserve for service calls versus maintenance visits, segmented by geography.
- 03
Maintenance outreach goes out automatically
Where the schedule has room for maintenance bookings, Demand Pulse sends outreach to eligible customers on its own.
- 04
The schedule stays balanced
As bookings come in and conditions change, the forecast updates and the outreach cadence adjusts, keeping service and maintenance capacity in the right balance.
The day before. The day after.
Same moments. Lived differently.
Reviews next week's schedule. Holds back slots for emergency service based on last week's volume. No data to back the call.
8:00 AMOpens the forecast. Demand Pulse shows projected service demand for the next two weeks, by geography, with the recommended capacity split.
8:00 AMBefore
Reviews next week's schedule. Holds back slots for emergency service based on last week's volume. No data to back the call.
After
Opens the forecast. Demand Pulse shows projected service demand for the next two weeks, by geography, with the recommended capacity split.
Maintenance customers need to be contacted to fill the remaining slots. The Dispatcher manually identifies eligible customers and sends outreach.
10:00 AMMaintenance outreach already went to eligible customers for the open slots. The Dispatcher reviews what came back, not what still needs to go out.
10:00 AMBefore
Maintenance customers need to be contacted to fill the remaining slots. The Dispatcher manually identifies eligible customers and sends outreach.
After
Maintenance outreach already went to eligible customers for the open slots. The Dispatcher reviews what came back, not what still needs to go out.
Higher-than-expected service demand this week. Maintenance slots double-booked to cover. Several maintenance visits rescheduled.
2:00 PMA service demand spike lands within the forecast window. The capacity was already held. No rescheduling needed.
2:00 PMBefore
Higher-than-expected service demand this week. Maintenance slots double-booked to cover. Several maintenance visits rescheduled.
After
A service demand spike lands within the forecast window. The capacity was already held. No rescheduling needed.
Schedule ran ragged all week. Too much maintenance held early, too little service capacity for the mid-week spike.
4:30 PMSchedule held all week. Service and maintenance ran in balance. The forecast was right.
4:30 PMBefore
Schedule ran ragged all week. Too much maintenance held early, too little service capacity for the mid-week spike.
After
Schedule held all week. Service and maintenance ran in balance. The forecast was right.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Does not assign technicians to jobs or manage the dispatch board directly.
- ×Does not handle inbound responses to maintenance outreach.
- ×Does not forecast beyond the configured forecast window.
- ×Does not replace the Dispatcher's judgment on capacity decisions that fall outside normal patterns.