Antylogic
DemoApp login

399 operational guides

Docs sections
DocsReservations
Device

Call a Waitlist Customer

Open the device phone handler from the Waitlist modal for a customer attached to a waitlisted reservation. The action hands the phone number to `tel:` and does not change the reservation, customer, service occurrence, or waitlist state.

In this article

Use this guide when a front-of-house operator needs to contact a guest who is waiting for a reservation slot. The action lives inside the Waitlist modal on a waiting-list service occurrence, so the operator stays in the reservation context until they confirm the phone handoff.

Antylogic only starts the external phone flow. It does not record whether the call was answered, and it does not promote, edit, or otherwise update the waitlisted reservation.

Before you start

  • An organisation and location are selected in the app context.
  • The operator is viewing a valid reservation occurrence at `reservations/:occurrenceId`.
  • The occurrence is in waiting-list booking mode, so the primary action opens `Lista de espera` in the current GB capture runtime.
  • The waitlist analysis contains a reservation linked to a customer record.
  • The customer record is loaded and has a non-empty `phone_e164` value.
  • The device or browser can handle `tel:` URLs.
  • The operator has access to view the reservation page, load the waitlist analysis, use reservation automation, and view customer phone data.

Instructions

  1. 1.

    Open the waitlisted occurrence

    From the reservations calendar or deep link, open the Harbor Soho waiting-list occurrence. In the GB demo runtime this uses `BOOKING_WAITLIST_OCCURRENCE_ID` and shows Sara Molina as the waitlisted reservation.

  2. 2.

    Open the Waitlist modal

    Select the primary `Lista de espera` action. The modal opens and loads the current waitlist analysis for the occurrence.

  3. 3.

    Find a row with a phone number

    Locate the waitlisted customer row. When the linked customer has a non-empty `phone_e164`, the row shows a phone action with the trimmed number.

  4. 4.

    Start the call action

    Select the phone action on the row. Antylogic shows the native confirmation alert titled `Llamar al cliente`, with `Cancelar` and `Llamar` actions before leaving the app.

  5. 5.

    Confirm only when ready to call

    Choose `Llamar` only when the operator intends to hand the number to the operating system phone handler. Choosing `Cancelar` leaves the waitlist unchanged and does not open `tel:`.

Validations and limits

  • Rows without a linked customer, without a loaded customer record, or without `phone_e164` do not show the phone action.
  • The phone number used is `customers.phone_e164` after trimming surrounding spaces; no other format validation is applied before building `tel:{customerPhone}`.
  • Selecting the phone action does not expand or collapse the waitlist row.
  • No HTTP mutation is sent by this action.
  • If the operating system cannot open the `tel:` URL, Antylogic shows a waitlist toast explaining that the call could not be opened.
  • The backend only serves waitlist analysis for occurrences still in waiting-list mode and with the required reservation, optimisation, customer, and `reservation-automatic:use` access.

Expected result

The operator can start a controlled external phone handoff from the waitlist row while Antylogic keeps the reservation, customer, service occurrence, and waitlist data unchanged.

Related articles