Booking site visits without a back-and-forth

The assistant does not push for a booking on the first message, and it does not wait to be asked. It offers a visit once the conversation has established enough to make one worth having — which in practice means the person has told it something real about what they want.

Wanting a visit is also the single strongest buying signal there is, which is why it is worth a flat fifteen points in the lead score.

Nothing is booked on a vague yes. “Sometime this weekend” and “yeah I'm interested” do not produce an appointment — the assistant treats them as interest and asks for a specific day and time.

This is deliberate. A calendar full of appointments nobody actually committed to is worse than an empty one, because your team drives to them.

Relative dates are resolved against a dated weekday table rather than left to the model to work out, so “Saturday” and “tomorrow” map to real dates. Date arithmetic is something language models are reliably bad at, and a booking on the wrong Saturday is a wasted journey.

When someone clearly wants a visit but has not named a time, WhatsApp customers get a native slot picker rather than a request to type one. They tap a date and a time inside WhatsApp itself.

Typing “how about Saturday around 11 maybe 11.30” is exactly where bookings get lost in transcription. Tapping a slot is not.

Connecting Google Calendar is optional, and it does two things: it stops the assistant offering a slot you are already busy in, and it puts the booking in the calendar your team actually looks at rather than only in Vesma.

Without it everything still works — the appointment is recorded and visible in the product. You simply lose the clash checking, which is the part that matters once more than one person is taking visits.

Automatic booking is on by default. If you would rather confirm every appointment yourself, turn it off in your AI settings and the behaviour changes honestly: the assistant still captures the day and time the customer agreed, but it tells them your team will confirm the slot shortly rather than stating it as booked.

That distinction is the whole point of the setting. It never tells a customer something is confirmed when it is waiting on you.

The booking cancels the rest of the follow-up sequence immediately — chasing someone who has already agreed to come in is the fastest way to undo the work. The lead moves to booked, and if you are running the outcome loop this is the kind of event worth reporting back to the ad platform that produced it.