Pending / Confirmed

When setting up a shift or event, you have the option to specify whether a booking should automatically receive a 'Confirmed' status or be marked as 'Pending'.

A booking marked as 'Pending' requires your confirmation later, either through your dashboard or via an email notification containing the booking details.

Several criteria can be applied to determine if a booking should be placed in 'Pending' status:

Set a Threshold for Automatic Confirmation: You might have a total capacity of 100 seats but prefer to automatically confirm only the first 60 reservations, leaving the remainder as 'Pending'. This approach allows for greater flexibility in managing your space based on phone inquiries or other factors.

Pending Status for Large Group Reservations: Decide on a specific number (like 6 seats) beyond which reservations will always be marked as 'Pending'. This helps in manually reviewing and confirming reservations for larger groups instead of auto-confirming them.

Time Slot-Based Pending Status: Use this rule if your establishment operates in multiple dining slots within the same shift. For instance, you might choose to auto-confirm bookings for a later dining slot while marking earlier ones as 'Pending'. This strategy can be beneficial if the earlier slot tends to have higher demand, allowing you to manage seating capacity more effectively.

Automatically set reservations to 'Pending' for customers with specific tags: Utilize customer tags to identify those whose bookings should always be marked as Pending. This can be particularly useful for customers with a history of no-shows, allowing you to hold off on auto-confirmation and ensure their attendance before manually confirming the reservation.

Set All Reservations as Pending on Specific Days: Apply this rule to make all bookings for certain days 'Pending'.

Designate Specific Tables' Bookings as Pending: This is useful if you wish to always mark bookings for particular tables as Pending.