On Saturday at six the phone rings and WhatsApp fills up just as you're setting up the dining room. You answer halfway, jot the table down on a sheet of paper, and the high chair or the allergy you remember only if you're lucky. The table of four that doesn't show up, you find out at nine, when it's too late to give it to someone else.
What you check
Gruppi e serate private sono tuoi. Da 8 persone in su il sistema raccoglie i dati e ti passa la richiesta.
L'allergia la ricorda, non la garantisce. Al tavolo il cameriere la chiede di nuovo.
Decidi tu quanto lasciargli fare. All'inizio puoi approvare ogni conferma, poi solo i casi fuori regola.
Si presenta come assistente del locale. Il cliente sa che sta scrivendo a un sistema automatico.
Similar cases
The same automation logic applied to other kinds of business:
Frequently asked questions
Does it work with TheFork or my table management software?
With a shared sheet or Google Calendar it works right away. TheFork Manager and other table management systems don't all have an open connection for writing reservations: we check yours before starting.
What if it confirms a table that doesn't exist?
It only confirms what it finds free in the calendar. If the time written in the message doesn't match the calendar, the message stops and comes to you. At first you can approve every confirmation yourself and loosen the rules as you come to trust it.
Does it handle allergies?
It remembers them and passes them to the kitchen as a note, but on a new allergy it never reassures the customer: that request comes to you. At the table the waiter asks anyway.
Does it answer the phone too?
A voice assistant can be added that answers and transcribes the request, but it has to be tested on your restaurant's number before we promise it. WhatsApp, on the other hand, works from day one.