01 · Guest care and bookings
Your house voice, with no robot behind it
Official Meta WhatsApp Business API. Real bookings on CoverManager. No grey bots.
Why it exists
Your floor does not take calls at eleven at night. The Concierge does, and leaves the booking made.
Because the guest writes when it suits them, not when your floor is open. And because 80% of those messages are the same five questions, answered by hand, one by one, by someone who should be on the floor.
The problem it takes
After-hours messages answered the next day, when the guest has already booked elsewhere
The same block of repeated questions eating team hours every week
Bookings lost between WhatsApp, the phone and the notebook
Unofficial WhatsApp putting the restaurant's account at risk of a ban
What it does
What it does not do yet
What it works on
Real availability, creation, modification and cancellation of the booking. The employee does not leave a note for someone to key in later, the booking is made.
Official Meta API, with the house's verified number. No grey bots, no accounts at risk of being blocked.
Bulk campaigns depend on Meta-approved templates, and that approval is not ours to control.
The reasoning engine behind every employee. A provider with a no-training policy on your data.
Requesting the car linked to the booking so it waits when the guest leaves.
In integration, not available yet. Requires a business account with the VTC provider.
When it comes on duty