What the approval queue does
For large parties, holidays, or tight capacity, instant confirmation is risky. The queue holds requests as pending until a host approves or declines.
Guests see "request received" until decision. Confirmed bookings trigger SMS or email.
Defining policy
Under Settings → Reservations → Approval Policy, pick days and hours for manual approval. Minimum party size can also trigger the queue.
All channels outside auto-approve. Widget, QR, Google, follow the same rules.
How does the host work the approval queue?
Operations → Approval Queue lists pending requests with date, covers, and source. Approve or Decline in one click; optional decline reason goes to the guest.
Enable mobile push so peak-hour requests are not missed. Bulk-approve matching service slices when appropriate. The notes field on each card shows allergies and special requests.
Timeout and auto-cancel
If hosts do not respond in time, the request cancels automatically, default 24 hours, reducible to 4 in peak seasons.
Cancelled guests get a notice with a link to book again.
Using with guest CRM
Set auto-approve exceptions for VIP or repeat guests via profile flag Skip queue.
Guests with problematic history can require manual approval every time.