The Restaurants pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Restaurants page.

Restaurants — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Party size, date and timeRoom or main floorSet menu and price per headDietary requests, word for wordName, company and mobileConfirmation and Thursday reminder

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Restaurants.

Inquiry→Booked→Day-before check→Seated→Next booking
PipelinePipelineInquiry4Booked3Day-befor2Seated1Next book1

What it will not do

Not a setting you switch on and off. These are blocked when the Restaurants answering is built; anything that touches them goes to a person instead of being answered.

  • It never answers for the kitchen on allergens or origin.Whether the set menu has shrimp in it, or nuts, is for the kitchen to confirm. The question is written down word for word and the owner answers it.
  • It never creates a table that is not there.It books from the registered tables and rooms only. A double-booked room means turning twenty people away at the door.
  • It never promises a menu change.Swapping a course or an ingredient is the owner’s decision. The request is logged, not granted.
  • It never makes up a discount.The only group rates it mentions are the ones on the function sheet.

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.