Availability gets gated by crew skill, job duration, travel zone, and daily load caps, so the board stays realistic.
Yes. Deposit rules can vary by service type, ticket size, distance, or customer history.
Slots write into ServiceTitan, Jobber, Housecall Pro, or Google Calendar, so the field crew keeps the app already on their phone.
Severity triage routes urgent work to on-call capacity and pushes flexible jobs, with the customer notified and offered an alternate window.
Reactivation and maintenance campaigns target the gap weeks in advance using service history and last visit date.
Scope sets the price inside a 500 to 10,000 dollar one-time range. A booking flow tied to one calendar sits low in that band. Capacity rules across multiple crews, deposit logic, waitlist backfill, and route awareness sit higher.
Slots write into ServiceTitan, Jobber, Housecall Pro, or Google Calendar, so technicians keep the app on their phone. Payment processing, phone systems, and the CRM connect to the same flow rather than running in parallel.
Availability gets gated by real constraints, so the board never promises work dispatch cannot deliver. Booking accuracy gets reviewed against completed jobs, and any pattern of overbooked days becomes a tightened rule.
Multi-crew projects, permit-dependent work, and jobs outside the standard travel zone stop before confirmation and route to dispatch with the details attached. Emergency calls follow severity rules and reach on-call capacity directly.
Two to four weeks from discovery to live booking. Mapping real capacity rules, job durations by service line, and travel zones takes longer than the software connection itself.