Use case · Now
LiveStop answering the same WhatsApp questions every night.
It is eleven at night. Someone asks if there is a table for four on Friday and whether one of them can eat gluten-free. Your floor is serving desserts.
It exists and can be demonstrated.
Who does it
What it does
The Host replies in the house voice, checks real availability in CoverManager, leaves the booking made with the allergy note and hands off to a person only if the conversation calls for it.
Result
Your floor does not touch the phone. The booking is made, not noted for later.
A restaurant gets the same twenty questions every week: hours, whether there is a terrace, how to get there, whether the lunch menu is served on Saturday, whether a pram fits, whether there is a gluten-free option. Each arrives over WhatsApp at an hour when the person who could answer is on the floor, and each one waits. The ones that wait too long go somewhere else.
The Host answers those questions with the house's own information, not a button menu. When the question is a booking, it checks real availability, creates, changes or cancels it in CoverManager and writes down what the guest asked for: the table by the window, the allergy, the birthday. If they have been before, it recognises them.
What it cannot do, it says so and hands over: a last-minute cancellation for twelve, a complaint, a request outside the ordinary. The conversation reaches a person with the full context, not from scratch.