Booking page is not loading

Confirm the page you are opening

Start from the active restaurant in the panel, not from an old email, QR code, social profile, or test page. Open Settings / Portal / Portal settings / Install and compare the destination that guests are using with the current Booking page URL.

The public booking page should use the clean restaurant page route, such as /p/main-street-bistro. Do not share a staff preview URL that contains /access?launch=...; that route is created for panel launches while access is restricted and is not a durable guest link.

If the copied URL points to a different portal domain, staging environment, restaurant slug, or old website redirect, replace it with a fresh Booking page URL from the active restaurant.

Check portal access

Open Settings / Portal and review Portal access:

1. Public lets guests open the standalone page and use embed installs directly.
2. Restricted is for staff-only preview launches from the panel. Public visitors see not found when they use the direct page URL or widget.
3. Disabled blocks standalone page, embed, and designer launches.

If the page should be live for guests, set Portal access mode to Public, choose Save access mode, and wait for Portal access mode saved. Only owners and admins can change this mode; staff users can preview but cannot make a restricted or disabled page public.

Test again in an incognito window after saving. A signed-in panel session or a recent staff preview launch can hide an access problem during troubleshooting.

Compare page, embed, and website behavior

Use the panel actions to isolate where the failure starts:

1. Choose Open portal. If the standalone page does not load, keep troubleshooting URL and portal access before checking the website.
2. Choose Open embed preview in the Install tab. If the standalone page loads but the embed preview does not, check portal access and the embed route.
3. Open the restaurant website where the widget is installed. If the panel page and embed preview both load but the website widget fails, the problem is in the website install, CMS, origin, or page layering.

This separation matters because the public page and the website widget use related but different routes. The Booking page URL opens the standalone page; the Raw embed URL opens the iframe route; the modal, drawer, and inline snippets load booking-widget.js and mount that iframe inside the restaurant website.

Fix widget install problems

If only the restaurant website fails, open Settings / Portal / Portal settings / Install and compare the live website code with the current snippet.

Check these items:

1. Portal access mode is Public. Public install copy buttons are disabled while access is Restricted or Disabled.
2. The website still contains the script tag and data-reslify-merchant. Some website builders remove scripts or strip custom attributes.
3. The snippet mode matches the intended install: Modal embed script, Drawer embed script, or Inline embed script.
4. For inline installs, the page still has the target container and matching data-reslify-target="#reslify-booking".
5. Allowed origins in Portal settings / General is intentionally empty or includes the exact website origin, including the correct https, www, staging, preview, or production host.
6. The browser console on the restaurant website does not show an origin, iframe, failed config load, or Reslify embed error.
7. The widget launcher, modal, drawer, or inline frame is not hidden behind website navigation, cookie banners, chat widgets, or other high z-index elements.

After changing Button text, Z-index, Modal width, Drawer side, Launcher placement, Drawer width, Offset, or Inline min height, choose Save portal settings and copy a fresh snippet if that setting is written into the website code.

Check browser and network causes

Ask the affected guest, or test from a clean browser session:

1. Refresh the page.
2. Open the link in an incognito or private window.
3. Turn off script-blocking, privacy, ad-blocking, or translation extensions.
4. Switch between mobile data and Wi-Fi.
5. Try another browser or device.

If only one guest or one device is affected, the issue is usually local to their browser, extension, DNS, or network. If the same URL fails for every guest and every network, treat it as a portal access, URL, embed install, or service issue.

If the browser shows Failed to load available slots., the page loaded but the availability request failed. Retry once, then compare whether the same search works in another browser and whether the panel can load the affected restaurant.

If the page loads but shows no times

Messages such as No available slots found., a date-specific no-slots message, or no time cards after choosing party size and date usually point to availability configuration, not page loading.

Reproduce the exact guest search: party size, location or area, date, and experience. Then check:

1. Experiences: the experience is active and accepts the selected party size.
2. Shifts: the date has bookable service hours.
3. Table Plan: tables or combinations fit the party size.
4. Special Days: the date is not closed or replaced by an incomplete special shift calendar.
5. Settings / General / Reservation Settings / Booking Interval: the expected start time matches the restaurant's generated slot interval.
6. Bookings: existing reservations, requests, or temporary holds have not consumed the relevant tables.
7. Payment, card guarantee, or request rules are complete for any experience that requires them.