← All systems
System 02

Scheduling and dispatch admin.

Booking, confirming, reminding, rescheduling, and the phone tag around all of it, against your real calendar and your real crew availability, in the software you already use.

30–40%is the reduction in no-shows that reminders are generally credited with.
1calendar. Not a new one, the one your crew already looks at.
0double bookings from two people editing the same day.

Industry figures, not a promise about your business. The free hour replaces them with your numbers.

The same job, both ways

Nothing here is complicated. That is the problem.

Every step is easy. There are just too many of them, they are spread across three or four systems, and every one depends on somebody remembering.

How it runs now

Today

Customer rings to book. You check the calendar from memory, or promise to call back.

You

Slot written into the job software, then into the shared calendar, then into your head.

You · retype

Crew told by text, separately, and hopefully before they set off.

You

No reminder goes out, or one does because you happened to think of it.

You · if remembered

Customer cancels. The slot sits empty because nobody fills it.

Nobody

Reschedule means the whole conversation again, from the top.

You
6steps on you
1retype
1slot lost per cancellation

How it runs after

With the system

Request arrives and is checked against real availability before anything is offered.

System

Times proposed that actually work for the crew, the travel and the job length.

System

You approve anything unusual: a tight turnaround, an awkward site, a new customer.

You · gate

Booked once, and it lands in the job software and the calendar together.

System

Crew notified with the details, not just the time.

System

Reminders go out on the schedule you set, and cancellations free the slot immediately.

System
1step on you
0retypes
0slots quietly lost

Scheduling is the one people underestimate. It is not the booking that costs you. It is the twenty minutes of phone tag around every change, and the empty afternoon nobody noticed until it was already empty.

The approvals

It asks before anything reaches a customer.

Every gate is on your phone and every one is a single tap. They exist at the moments where getting it wrong costs you a relationship or money.

Approval 1

Before an unusual booking is confirmed

Routine jobs in a normal slot go through on their own. Anything tight, far, out of hours or from someone new comes to you first, because those are the ones where the calendar does not tell the whole story.

Approval 2

Before a customer is told no

If the system cannot find a slot, it does not turn work away. It asks you, because you know when a job is worth rearranging the week for.

Be honest about fit

When this is worth doing, and when it isn't.

Worth doing if
  • You book more than a few jobs a week and the calendar is a shared source of truth.
  • No-shows or late cancellations cost you real money.
  • Crew find out about changes later than they should.
  • You are the bottleneck on every reschedule.
Probably not, if
  • Work arrives in long projects rather than appointments. There is not much scheduling to automate.
  • One person books everything and it genuinely is not a burden.
  • Your availability depends on judgement no calendar reflects, and you would override it constantly.

Find out whether this one is your first system.

An hour, no charge. I ask how the work moves through your business and tell you straight whether this is the piece worth doing first, and if it is, a price before I leave.

Book the free hour