Antylogic
DemoApp login

399 operational guides

Docs sections
DocsReservations
Device

Create a Manual Reservation

Record a phone reservation for Harbor Soho from a public service occurrence. The app creates the customer first, then saves the party size, start time, duration and optional table handling before refreshing the occurrence.

In this article

Use this guide when front-of-house staff take a booking by phone and need to add it from the Harbor Soho occurrence detail screen.

This workflow is for eligible public service occurrences. Waiting-list-only occurrences, completed booked reservations and internal services follow different rules.

Before you start

  • You are signed in to Harbor Demo Group and working in the Harbor Soho location.
  • The target occurrence is a public service occurrence, such as BOOKING_MANUAL_OCCURRENCE_ID in the GB demo runtime.
  • You can view and manage reservations, and you can view and create customers for the location.
  • A layout with tables is loaded if you plan to use preferred, required or assigned table handling.

Instructions

  1. 1.

    Open The Service Occurrence

    Open the Harbor Soho reservation occurrence and wait for the occurrence, existing reservations, table assignments, customers and layout context to load.

  2. 2.

    Start A New Reservation

    Select New reservation. On the manual path, the editor opens with empty customer fields, two guests, booked status, a snapped start time and a default duration.

  3. 3.

    Enter Guest Details

    Enter the caller's name and phone number, then set the party size, start time and duration requested for the booking.

  4. 4.

    Choose Table Handling

    Leave the table mode as indifferent when no table choice is needed. Choose preferred, required or assign to select real tables such as T2 and B1 from the Harbor Soho layout.

  5. 5.

    Save The Reservation

    Save the editor. Antylogic creates the customer first, then creates a phone-channel reservation for the selected occurrence with the timing, party size and table payload.

  6. 6.

    Confirm The Result

    Check that the refreshed occurrence shows the new guest in the reservation list and, when tables were selected, on the table assignment board.

Validations and limits

  • The occurrence must be public, belong to Harbor Soho and not be an internal service.
  • reservation:view is needed to load the occurrence; reservation:manage is needed to create the reservation.
  • customer:view and customer:manage are needed because the create path creates a customer before the reservation.
  • Customer name and customer phone are required in the frontend before submit.
  • Party size must be greater than zero; the UI picker supports 1 to 99 guests.
  • Start time and duration are snapped to the configured slot interval; duration is capped at 480 minutes in the picker.
  • A non-indifferent table mode requires at least one selected table from the loaded layout.
  • The backend rejects non-waitlist reservation creation on completed or waiting-list booking-mode occurrences.
  • The current create-mode path creates a new customer; do not document this as customer reuse.

Expected result

The new customer and phone-channel reservation are saved against the occurrence. Selected tables are stored as manual fixed assignments, with preferred or restricted metadata when that table mode is used, and the occurrence optimisation state is marked stale.

Related articles