FOR THE DISPATCHER
Demand Pulse
Demand forecast that fills the schedule itself.
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.
- Time back
- 15 min
- per job
- Cost
- 50¢
- 100 Rivets per job
How it works.
4 steps, and your team only touches the ones that need a person.
- 1.
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.
- 2.
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.
- 3.
Maintenance outreach goes out automatically
Where the schedule has room for maintenance bookings, Demand Pulse sends outreach to eligible customers on its own.
- 4.
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.
Try it.
A small working model of Demand Pulse. Nothing here touches a real customer.
Pick a weather outlook and see how next week's calls split between repairs and maintenance.
A day for the Dispatcher.
- 8:00 AM
Reviews next week's schedule. Holds back slots for emergency service based on last week's volume. No data to back the call.
- 10:00 AM
Maintenance customers need to be contacted to fill the remaining slots. The Dispatcher manually identifies eligible customers and sends outreach.
- 2:00 PM
Higher-than-expected service demand this week. Maintenance slots double-booked to cover. Several maintenance visits rescheduled.
- 4:30 PM
Schedule ran ragged all week. Too much maintenance held early, too little service capacity for the mid-week spike.
- 8:00 AM
Opens the forecast. Demand Pulse shows projected service demand for the next two weeks, by geography, with the recommended capacity split.
- 10:00 AM
Maintenance outreach already went to eligible customers for the open slots. The Dispatcher reviews what came back, not what still needs to go out.
- 2:00 PM
A service demand spike lands within the forecast window. The capacity was already held. No rescheduling needed.
- 4:30 PM
Schedule held all week. Service and maintenance ran in balance. The forecast was right.
What it won't do.
So nobody's surprised later.
- 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.
- About 220,000 calls a month analyzed across 31 shops
- 139 shops use Graphite Lab tools
- 108 ServiceTitan data types synced, including for multi-location operators
- 66 to 93 mobile PageSpeed, from a contractor's old site to the preview we built in under 10 days
Let’s talk about your shop.
No slide deck. Tell us how your team runs today and we'll show you what we'd build first. If it's a fit, we send you a quote.
