Restaurant CRM
In a restaurant the evening service is a one-off capacity; when nobody turns up to the table that was held, that table cannot be sold again that evening. A guest's complaint is settled at the table and stays there, and when they never come back nobody knows why.
A booking is a record with date, time, party size and table fields, attached to the guest card. The no-show is a field, so repeated cancellations are read from the history.
- Take the booking onto the record with date, time, party size and table fields, and schedule the confirmation message from that record
- Mark the guest who did not turn up on the record and see repeated cancellations in the history on the guest card
- Send a satisfaction survey after service, turn a negative reply into a case record and drop it to the person responsible
- Gather corporate guests on an account record, build up the bills over the month and produce the month-end invoice from there
| Booking Record | A booking is a record with date, time, party size and table fields; it is attached to the guest card, and the evening's list comes out of it. |
|---|---|
| No-Show Information | A guest who does not turn up is marked in a field on the record; repeated cancellations are visible in the history on the guest card. |
| Satisfaction and Complaints | The survey after service is sent to the guest; a negative reply opens a case record and stays in the list until its owner closes it. |
| Corporate Account | A company is an account record; the bills over the month accumulate under the account, and the month-end invoice is compiled from those records. |
A restaurant's evening is made up of a limited number of tables and a limited number of sittings. When the reservation book is kept next to the telephone, it is not visible who has already failed to turn up without warning before; when that table stays empty, the loss is that evening's takings, directly. Something similar happens on the guest's side: a problem with the food is mentioned to the waiter at the table, the waiter apologises, and the matter closes there. That guest never comes back, and their not coming back is not noticed either, because their name appears nowhere.
In Rapitek CRM a booking is a record with date, time, party size and table fields, and it is attached to the guest card. Because the no-show is a field on the record, repeated cancellations are read from the guest's history, and the confirmation message is scheduled from the booking record. The satisfaction survey after service is sent to that same guest; a negative reply opens a case record and drops to the person responsible, so the complaint is closed on the record rather than at the table. Corporate guests are account records; their bills over the month accumulate under the account and the month-end invoice is compiled from those records.
What the plans cover and which items are priced separately are set out on the pricing page.
