No automatic confirmation. Kim takes the name, time, party size and what it is about, emails it to you, and tells the guest it is a request.
The request lands under Bookings as unconfirmed and is emailed to the address you chose. The guest hears that someone will get back to them, not that the time is booked. That is the point, not a shortcoming.
It fits where availability depends on things Kim cannot see: how much there is to move, whether the job is even one you take, whether a van can get in. You read it and decide.
Kim still handles everything else. Prices, opening hours, what is included, how long it takes. Only the yes to a specific time stays with you.
We spell this out because it is cheaper for everyone to know up front than to find out with a guest on the phone.
Why would we pick this over a real booking?
Because a wrong confirmation costs more than a request. If the time depends on how much there is to move or how broken the bike is, it is cheaper for you to look first.
How fast do we have to answer?
As fast as you can manage, but the guest has been told it is not settled, so you have air. Unconfirmed requests stay under Bookings until someone touches them.
Can we start here and move to real bookings later?
Yes, and many do. You run requests for a couple of weeks, see what actually comes in, and then switch on Native or connect your booking system.