Scheduling
Reading real availability is what separates a booking from a lead. Service Setpoint works against the calendar you already run on and writes the appointment back where your crew will see it.
Can someone come look at it this week?
Let me check the calendar. Thursday I have 8am or 2pm, and Friday morning is open.
Live availability, filtered by crew and drive time
Thursday afternoon.
Thursday at 2pm. Is 812 Ridge Road the right address for the visit?
Yes.
Booked. Ryan will be out Thursday at 2, and you'll get a text confirmation now and a reminder Wednesday.
Written back as a real appointment, assigned to a crew
The hard part
Field-service platforms are good at recording work that’s booked. Very few expose an endpoint that answers the opposite question — what’s open on Thursday.
So we derive it. Your booked jobs, your working hours, your buffers and drive-time rules combine into genuine open slots. Where a platform does publish real availability, we read it directly and skip the arithmetic.
Either way the agent offers times it can actually keep — which is the only version of this feature worth having.
What it can do
Filtered by job type, crew, working hours, buffer and travel — not a generic nine-to-five grid.
Written back to your calendar or CRM as a real, assigned job with the address and the notes attached.
Confirms who’s calling, moves the booking, and re-sends the confirmation.
Releases the slot, records the reason, and flags it if the reason is worth someone seeing.
An outbound call or text that checks someone will be home — and reschedules on the spot if not.
Stops offering slots when the day is genuinely full instead of overbooking your crew.
Works with
If your team won't see the booking where they already look, the feature is worse than useless. So we write where you work.
Clients, properties, scheduled assessments
Open slots and confirmed bookings
For shops with no CRM at all
Enterprise field service
Field service management
Roofing CRM
Roofing CRM
Webhooks both directions
Questions
Most don't — which is why we don't rely on one. We read your booked work and your working hours and compute what's genuinely open, then write the booking back through whatever endpoint the platform does expose. Jobber works exactly this way.
Yes. Set a buffer and a drive-time rule and it stops offering slots that would put two jobs an hour apart in opposite directions.
The write is the source of truth, not a cached copy. If a slot is taken between the agent offering it and the caller accepting, it re-checks, apologises, and offers the next one.
An inspection, a repair visit and a full estimate can each carry their own duration and their own crew, and the agent picks based on what the caller described.
Cancel and reschedule are separate capabilities you switch on per agent. Both confirm who's calling before touching an existing booking.
A shared Google Calendar is enough. A lot of shops run that way and the agent works fine against it.
We'll link a test calendar and call you, so you can hear it offer a real slot and watch the booking appear.
