Keep the reservation book authoritative and use WhatsApp to make confirmations and change requests easier to handle.
1. Collect the details that affect seating
Prepare the booking name, date, arrival time, party size, and restaurant address. Use only guests who agreed to receive these messages. Check special seating requests with staff before promising them. A requested terrace table should not become a confirmed terrace table through careless wording.
2. Explain how to cancel or amend
Give guests a straightforward way to report a smaller party, a late arrival, or a cancellation. Describe any booking conditions accurately and link to the full terms if necessary. Avoid asking for payment-card details in the conversation; use your normal secure booking process.
3. Send from a current booking list
Group reservations for the relevant service and preview the message against realistic records. If preparing a campaign in Tiringo, update the export manually before launch. Replies do not automatically change table availability. Staff must reconcile the conversation with the booking system before confirming a new arrangement.
4. Review service outcomes
Compare the reservation list with confirmed parties, cancellations, and actual covers. Review whether guests repeatedly ask about parking or entrance directions. Add the missing detail to the next template. Try the workflow for one service before expanding it across the week.
5. Prepare the shift handover
Reservation replies can arrive while one team finishes and another starts. Give the next shift a clear handover of outstanding requests, confirmed changes, and guests expected late. Keep that handover in the reservation workflow rather than relying on someone remembering an inbox conversation.
- List unresolved requests before service.
- Confirm the staff contact for late arrivals.
- Reconcile table changes with the floor plan.
