Use cases / Booking & reminders

Use case

The diary runs the business. Nobody runs the diary.

Bookings arrive by phone, text and email, and land in a shared calendar held together by one person's memory. When it works, nobody notices. When it slips, it's a double-booking — or a 2pm that simply doesn't turn up.

The no-show you paid for.

The customer rings while you're on a job. Voicemail. They text instead. Someone writes it in the calendar that evening — usually. Three weeks later the slot arrives, nobody's reminded them, and they've forgotten: an afternoon held open for a no-show, while the person who'd have taken that slot was told you were booked out. It's what happens when the diary is really a calendar plus somebody's memory.

If your diary is simple — one person, one kind of appointment, bookings that stand alone — a free tool is the answer. Square Appointments, SumUp Bookings and Calendly are good at exactly this, and most small firms should use one of them. We'd tell you so. The gap opens when a booking isn't just a calendar entry — when it's the start of a job that needs a deposit taken, the right person briefed, materials ordered and a follow-up triggered. A stitched-on booking tool knows none of that. It holds the slot and stops.

How it actually works.

  1. Your customers could book against real availability. Not a generic calendar — we'd build a booking page that knows your actual capacity: who's qualified for which work, how long each job type really takes, what's already promised. The phone stops being the only door in.
  2. Reminders go out on their own. Text or email, at the moments that suit the appointment — booked, day before, morning of. This part is bread and butter: the platform we run for a UK firm sends its reminders overnight, every night, without anyone remembering to.
  3. The booking becomes the record. The moment a slot is taken, the job, visit or appointment exists in your system — customer details, address, notes — instead of being retyped from the calendar into wherever the work is tracked.
  4. Deposits and questions attach where they fit. If your trade needs a deposit to make a booking real, or three questions answered before anyone travels, we'd build that into the same flow — paid and answered before the slot is confirmed.

Where we've done it

The reminders already run every night.

Automatic chasing and reminding is the pattern we've built most often: in one UK firm's platform, customer and meeting reminders go out as part of roughly eighty automated jobs that run overnight. The booking front door — availability, deposits, intake questions — is the part we'd shape to your firm, and it's the same pattern we've shipped again and again: a form that creates a record that triggers the work.

~80nightly automations
20+systems integrated

Read the full case study →

What module one looks like.

We don't build the whole front door at once. Module one is usually the reminders — the smallest piece with the most obvious payback.

What the empty slot costs.

There's no off-the-shelf statistic worth printing here — the real number depends on your diary. It's the slot held open for someone who forgot. It's the skilled person who stops mid-job to answer the phone and take a booking by hand. It's the customer who rang, got voicemail, and booked with whoever answered.

That's exactly the kind of number a process audit puts a figure on: how many bookings arrive by interruption, how many slots die to silence, and what an hour of your diary is actually worth.

Not sure this is the one to fix first? The 20-question self-audit ranks your processes — free, two minutes, no email →

Start here

Bring us your diary.

A free process audit is thirty minutes. Walk us through how a booking gets from first phone call to finished job, and you'll leave with a written map of which parts could run themselves — whether or not we ever work together.

No pitch deck, no obligation. The map is yours either way.