Booking Days in Advance is a field derived from the difference (in days) between the start of the meal and the time the reservations was created. It represents the number of days in advance that a reservation was booked. It can take the following categorical values:
- After (if the reservation was created after the start of the meal. Usually for walk-ins)
- 0-1/2d (created between 0 and 12 hours before the start of the meal)
- 1/2-1d (created between 12 and 24 hours before the start of the meal)
- 1-2d (created between 24 and 48 hours before the start of the meal)
- 2-3d (created between 48 and 72 hours before the start of the meal)
- 3-5d (created between 3 and 5 days before the start of the meal)
- 5-7d (created between 5 and 7 days before the start of the meal)
- 7-14d (created between 7 and 14 days before the start of the meal)
- 14-31d (created between 14 and 31 days before the start of the meal)
- 31d+ (created more than 31 days before the start of the meal)
Cancelled Status is a derived field that can take the following values: No-Show, After (if the reservation was cancelled after the start of the meal - usually for no-shows), 0-1d (cancelled within 0 to 24 hours of start of meal), 1-2d (cancelled within 24 to 48 hours of the meal), 2-3d (cancelled within 48-72 hours before the start of the meal), 3-7d (cancelled within 72 hours to 1 week before the start of the meal), and 7d+ (cancelled more than one week before the start of the meal).
Cancel Reason is the enumerated reason for cancelling a reservation (from a fixed list of values). It is therefore only meaningful for cancellations.
Day of Week is the day of the week for the start of the meal or the time the reservation was created (based on user selection) and can only take the following values: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday.
Day Type is the type of day based on either the day of the meal or the day the reservation was created (depending on user selection). It can only take the following values: Weekday, Weekend, Holiday, and Pre-Holiday.
Time of Day is the hour of the day for the start of the meal or the time the reservation was created (depending on user selection). It takes values like 7:00, 12:00, and 23:00 (11pm).
Meal is the meal in which the reservation starts. It can only take the following values: Breakfast, Lunch, Tea, Dinner, and Night.
Channel is the referrer by which the diner made a reservation at the restaurant. This is typically a third-party marketing company (OTA), social network, hotel concierge, staff intro, etc. Channel is primarily manually determined by staff but can also take values automatically.
Method is similar to Source in that it’s the way/channel by which the reservation was made, but the values are automatically determined by the system. It can only take five values: OTA, TC, Miseban, Walk-in, and Manual. The value is TC if the reservation came from TableCheck, Miseban if the reservation came from voice concierge, OTA if the reservation came from a third-party marketing site, walk-in if the reservation was flagged by staff as walk-in or the diner arrived within 15 minutes of the meal, and manual otherwise.
Pax is the total number of guests in the reservation including adults, children, and babies. It is also referred to as the pax and can only take whole number values of 1 or more.
Purpose is the purpose of the reservation as manually entered by staff. Typical values include Birthday, Business, Family Celebration, Group Date, etc.
Provider is similar to Channel in that it is the referrer by which the diner made a reservation, but it is automatically determined by the system and cannot be manually overridden by users. Typically values include TableCheck, OpenTable, Tabelog, Miseban, etc.
Source is the way/channel by which the reservation was made. It is typically set manually, but there are cases where it is automatically set. Typical values include walk-in, phone, web, in-person, and email.
Status is the status of the reservation that is both manually and automatically determined. Typical values include accepted, no-show, cancelled, arrived, paid, etc.
There are two types of visit history metrics:
- Absolute Visit History counts the number of times the primary customer of the reservation has ever visited the restaurant.
- Relative Visit History counts the number of times within the date range that the primary customer of the reservation visited the restaurant.
These metrics can only take the following values: 1v, 2v, 3v, etc. Visit histories correctly account for customer records that have been previously merged. The first active reservation by a customer is assigned a visit history of 1v even if the meal is at some point in the future. Visit history is counted differently depending on whether the metric is active or not. For active metrics visits are counted only for active reservations (cancellations and no-shows are excluded from the count). However, for any other metrics cancellations and no-shows are counted as visits, and therefore, if a cancelled or no-show reservation was the first time the customer made a reservation, but the customer has no prior active reservations, the visit will count as v1.