What should I check two days before go-live?
Before you take your first real booking, you want confidence that technical setup and content settings are complete. Checking now leaves enough time to fix surprises before service day.
Start by confirming your booking form works. Submit a test from the website widget or QR code on your own phone. The confirmation should appear in the panel. Then open Settings → Channels → Web Widget and verify your domain list is current and privacy notice links open correctly on the form.
Make sure table count on the floor map matches physical capacity, extra tables on the map increase double-booking risk. Finally, under Settings → Notifications, confirm reminder SMS and email templates are active, and that your team understands approval queue and waitlist policy for the week.
What does the manager check on service morning?
A few minutes in the panel on service morning helps the evening run smoothly. First, check whether today has special hours or closed areas, holidays, events, or maintenance days may override the normal schedule.
Confirm at least one host account has accepted their invite and is active. If Settings → Users shows pending invites, nudge those teammates before doors open. Review Reports → Usage to ensure SMS quota will cover the day; busy evenings burn through reminder messages quickly.
Delete test bookings created during setup before service starts. Otherwise occupancy reports keep ghost records and the host team misreads real capacity.
What should the host team prepare before service?
Your host team should open Operations → Live Floor about thirty minutes before service. That screen is the visual home for table status and incoming bookings through the shift.
Clear any pending items on the approval queue before guests arrive, or assign them to the right host. Decide whether the waitlist is on or off today. Many venues enable it for busy dinners and turn it off for quiet lunches.
Review guest notes and VIP tags on today's reservation cards. Allergy, birthday, or table preference details read after service starts hurt the guest experience.
What matters during service?
Make marking Seated a habit when guests arrive. Late bookings show an orange flag. If fifteen minutes pass, call to confirm they are still coming.
Before seating walk-ins, add them to the waitlist with the correct party size when the list is enabled. Fair queue order keeps the floor calm.
Do not mark no-show until the service window ends, early marks create bad history. If the panel shows a double-booking warning, pause walk-in seating and call the manager.
What should I do after service?
At close, review the occupancy summary under Reports → Occupancy. Export CSV if you compare weeks. The occupancy reports article explains the metrics.
Release merged tables on the map; tomorrow's bookings can conflict if blocks stay merged. Add tomorrow's special hours or closures to the calendar now if needed.
Log technical issues or operational notes in a support ticket or team note. Small problems that repeat next service are easier to fix when they are documented.