Status
BetaBookings
From a qualified inquiry to a confirmed booking with logistics and completion.
Product presentation — fictional data
Booking · Palermo Walk
Friday · 10:00
- Tour
- Palermo Walk
- Duration
- 3 hours
- Guests
- 2
- Inquiry code
- #A184
In practice
What problem it solves
Confirmation lives in a message — without date, payment and status in one place.
What you see
A booking card: tour, guests, payment, client and next steps.
What you do
Confirm, mark payment, reschedule or complete the tour.
What happens next
The event lands on the calendar; after the tour you can request a review.
How it connects
Inquiry → Booking → Payment → Calendar → Today.
What is available now
Booking lifecycle and payment statuses — in closed beta.
Why it beats the manual process
One object instead of “chat + Google Calendar + payment note”.
Learn how it works →
A proposal captures terms. A confirmed booking drives calendar, payment status and the work plan. Reschedule, cancel, complete and request a review in the same lifecycle.