Scheduling
Turn a callback into a booked site visit
Turn a requested callback into a confirmed site visit. Check the address, assign the crew, allow for travel and test what happens after a booking moves.

Put the right promise in the diary
A customer asks for a call before ten tomorrow. At 8.45 your apprentice sees their name in the run sheet and starts loading the ute. The customer is at work. Nobody has agreed on a visit. Both people followed what the diary appeared to say.
Give the callback an owner, a number and a due time. Create a visit once the customer agrees to a date or arrival window and the business can supply a crew. Keep the job reference on both records so the dispatcher can see what the customer has actually agreed to.
Give the morning crew one usable record
Consider Alex’s Marrickville patch. The plaster is still damp, the ceiling height is unknown and painting is excluded. Alex can take a call tomorrow morning before ten. The address and exact inspection time are outstanding. A plasterer picking up this enquiry at 7.30 needs the preferred number, the window in Sydney time, the reason for calling and who is taking it. They don’t need to read twenty lines of conversation before discovering why there’s no price.
- Callback requestedOwner and deadline assigned. Crew diary is free.
- Inspection offeredCheck the address, duration, travel and who can let you in.
- Visit confirmedSave the agreed window against the job and assigned person.
- Reminder dueUse the current booking and the customer’s chosen contact channel.
An HVAC contractor can take a call about a unit at a shopping centre straight away. Before booking the service, the dispatcher may still need the tenancy, the building manager’s access window and a technician with the required skills. Put those details on that site’s job. The same facilities manager may ring about a different address next week.
Book the drive as well as the inspection
A thirty-minute inspection can use a full hour once you allow for parking and getting there. Suppose the first job ends at 9.00 and the drive normally takes twenty minutes. An inspection at 9.30 leaves ten minutes for parking and getting in. If the first job regularly runs fifteen minutes late, an arrival window or a later slot is easier to keep. Check that the person with the keys can make that window before putting it in a confirmation.
If you use Google Calendar appointment schedules, check the duration, booking window, buffers and the calendars checked for conflicts. Some functions depend on your account. If your team works in ServiceM8, review which job bookings trigger confirmations and how closely the reminder precedes the visit. Pick one system to send customer messages so a calendar invite and job system don’t both chase the same person. Google Calendar appointment settings · ServiceM8 reminder settings.
Test a changed booking before trusting the reminders
Move a fictional visit from Tuesday to Thursday after the first confirmation. Check the owner’s phone, the field worker’s diary and the customer message. The old reminder should disappear. Then disconnect the handset, change the booking again and reconnect. If an old notification opens the job, the screen should show the current arrangement. Use a test customer and your own devices for this rehearsal.
Reassign a test visit to a colleague. Open both diaries, check who now owns the visit and see which handset still has a reminder. Then mute notifications and check that the work remains visible in the day’s list. If a customer message fails, give a named person the follow-up. An office can recover from a missed alert when the underlying booking is still clear.
For two weeks count callbacks requested, callbacks made within the requested window, visits actually agreed and appointments that had to be rebooked. Read the reason on each rebooking. A common “no access” means the confirmation needs a question about keys. Adding another reminder to the night before won’t get a locked gate open.