Skip to content

Booking

A lead is homework. A booking is a job.

Most systems hand you a name and a number and call it a win. The work is still all in front of you — ring back, find out what they want, check the calendar, offer a time, hope they pick up.

The callback loop is where jobs die

Getting a lead is the easy half. The half that loses money is the loop afterwards: you ring back, they are busy, they ring you, you are under a house, and two days later everyone has quietly given up.

Every hop in that loop is a chance for the customer to hire somebody who answered first. And the loop happens after they were ready to book — you had them, and then the scheduling took too long.

Closing it in the original conversation removes the entire failure mode.

How a slot actually gets taken

Booking straight onto a live calendar comes with Growth and above. Below that it sends your real booking page and confirms once it is used.

  1. 1

    It works out what the job is

    Not just that they want an appointment — what kind, so the right length of slot is offered.

  2. 2

    It checks the service area

    Their street either is or is not somewhere you go. Answered before it costs you a truck roll.

  3. 3

    It reads your real calendar

    Actual free slots. It never offers a time that is already taken or outside your hours.

  4. 4

    It offers times

    A small number of real options, the way a person would, rather than a link and a shrug.

  5. 5

    It takes the slot

    Booked while they are still in the conversation, with a confirmation to them.

  6. 6

    It lands on your calendar

    A normal calendar event with the name, the number and what they actually said.

Why it will not double-book you

It books against your real calendar, not a copy of it. If a slot filled ten minutes ago it is not offered, and if you block out an afternoon it disappears from what the customer can take.

It also will not stretch a slot to fit. Job types are set up with the time they actually need, so a quick call-out and a full replacement are not offered the same window.

When it is not certain the slot is right, it stops rather than guessing. An appointment made wrongly costs you a wasted drive and a customer's morning, which is worse than a lead you had to ring back.

What it needs to know before it can book anything

Your hours, your service area, the job types you take and roughly how long each one runs, and the calendar it should be writing to. That is set up once during onboarding, in about 45 minutes of your time.

Pricing rules go in at the same time. It answers from your list and never invents a number, which matters more on a booking call than anywhere else — a customer who was quoted something imaginary is a customer you lose at the door.

You still see everything

Every booking sends you an email with the name, the number, the job and what the customer said, and the calendar event carries the same detail. Nothing is booked quietly.

If you never log into anything, this still works completely. The dashboard exists for owners who want to look, not because the product needs you to.

Questions on this

Which calendar does it use?

The one you already run on. It is connected during setup, and the appointments appear as ordinary events you can move or cancel like any other.

What if I need to approve bookings before they are final?

Then it is set up to send your booking page and confirm rather than take the slot itself, which keeps you in the loop on every appointment. Which behaviour you want is a setup decision, not a limitation.

What happens if it cannot work out what to book?

It asks one clarifying question. If that does not resolve it, it stops, tells the customer a person will follow up, and emails you the conversation. It would rather hand you a lead than put the wrong thing in your diary.

Not sure this is the one that fits? How it works walks the whole thing end to end.

15 minutes. Bring your call log.

We'll count what you actually missed last month and tell you what it cost. If it's not worth fixing, we'll say so.

Or go break the demo first. It costs you nothing to test.