Antylogic
DemoApp login

399 operational guides

Docs sections
DocsOnline reservations
Device

Create Public Reservation

Guide operators through the Harbor Soho public booking flow, where a visitor submits contact details and receives either a confirmed web reservation for an available slot or a waitlist entry when availability succeeds with no slots.

In this article

Visitors can use the public booking page to choose a public automatic service, select a party size, add contact details and submit without an Antylogic staff session.

Antylogic rechecks availability at submission time, creates or reuses the customer by phone, and returns either a confirmed booking or a waitlist result.

Before you start

  • Public booking is enabled for Harbor Soho in the documentation runtime and the location has reservation-automatic:use enabled.
  • The booking page is opened through /:orgId/:locationId/reservar or /:orgId/:locationId/booking.
  • The selected service is a future public automatic service occurrence with open acceptance state.
  • The guest has selected a date, service and party size greater than zero.
  • For a confirmed booking, an available time slot is selected. For a waitlist entry, availability has succeeded with zero slots.
  • Full name and phone number are required. Email and guest note are optional.

Instructions

  1. 1.

    Open the public booking page

    Open the Harbor Soho public booking link. The page loads only when the URL organisation and location match an active public-booking-enabled location allowed to use automatic reservations.

  2. 2.

    Choose booking details

    Select a public automatic service, enter the party size and complete any visible preference step. Manual services are contact-only and do not submit this reservation action.

  3. 3.

    Select a time or waitlist path

    Choose an available slot when slots are returned. If the availability check succeeds with zero slots, continue through the waitlist path instead of selecting a time.

  4. 4.

    Enter contact details

    Fill in full name and phone number, then optionally add email and a guest note. The form submits the selected occurrence, party size, status, contact details, locale and supported preferences.

  5. 5.

    Confirm the result

    After submission, Antylogic creates or reuses the customer by location and phone, then creates the web-channel booking or waitlist entry. The guest sees the confirmed booking state or the waitlist success state.

Validations and limits

  • No staff login is required for the public visitor.
  • Unavailable, disabled, deleted, billing-blocked or wrongly scoped locations are hidden as not found.
  • Internal services are not exposed in public booking, and manual services stop at the contact-the-venue branch.
  • A booked reservation requires the selected starts_at to still be available when the backend recalculates availability.
  • A waitlist reservation is sent without starts_at and does not create table assignments.
  • Repeating the same unchanged submission returns the existing reservation instead of creating a duplicate.
  • Changing details while reusing the same idempotency key returns a conflict.
  • If a selected slot is no longer available, availability is refreshed and the guest is told the slot is no longer available.

Expected result

The public visitor receives either Booking confirmed for a web-channel booked reservation or a waitlist success result for a zero-slot automatic public service.

Related articles