Mark Booking (no-show / completed)

Finalise this conversation's appointment as completed, a no-show or canceled — the same move the Bookings page's own buttons make, done automatically.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Mark Booking (no-show / completed).
  2. Choose No show, Completed or Canceled — the default is No show, so pick carefully.
  3. Leave Booking id blank for this conversation's own booking, or name one from its URL on the Bookings page.
  4. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • Only a confirmed booking can be marked. One already marked completed, no-show or canceled cannot be marked again.
  • With Booking id blank and two or more confirmed bookings, it picks the latest start time — maybe a future one, not the one just finished.
The Add Steps menu open on the canvas, with Mark Booking (no-show / completed) highlighted.
The step panel set to Completed, using this conversation's own open booking.
The step panel set to No show, with Booking id left blank.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Mark Booking (no-show / completed) under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
  • Building and running workflows depends on your plan; see pricing.
  • This conversation (or the booking id you name) needs a confirmed booking to finalise — nothing else moves.

Set up

  1. Open the workflow and click + where the record belongs.
  2. Pick Mark Booking (no-show / completed).
  3. Choose No show, Completed or Canceled.
  4. Leave Booking id blank to use this conversation's own open booking, or name one with a placeholder.
  5. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Status
No show, Completed or Canceled.
Default: No show
Booking id
A specific booking to finalise, as a placeholder or literal id.
Default: This conversation's own open booking
Limits: Left blank, only this conversation's confirmed booking is eligible — never another contact's.

How it works

  • Left with no Booking id, the step finds this conversation's own confirmed booking, ordered by start time with the LATEST one first.
  • So if this conversation somehow has two confirmed bookings — a past one and a future one — this step finalises the future one, not necessarily the appointment that already happened.
  • Only a booking in confirmed status can move. If this step and a person on the Bookings page change the same booking at the same moment, only the first change is saved. The other gets “already finalized” rather than finalising it a second time.
  • This step uses the same function the Bookings page's own status buttons call — labelled Done, No-show and Cancel there, where this step's own dropdown uses the fuller words above.
  • So a booking finalised by a workflow behaves identically to one a person finalised by hand.
  • On success it fires this workspace's Booking Status Changed trigger for follow-up flows — a re-engagement message after a no-show, for example. This is best-effort: if starting that follow-up fails for any reason, the booking's status change already happened and is not undone.

When it fails

  • No booking id was given and this conversation has no confirmed booking: the step fails with this conversation has no open booking to mark. A database error looking up that booking fails with the same message, so the run log cannot tell the two apart.
  • The named booking id does not exist in this workspace, or is not currently confirmed (already finalised, or raced by something else): the step fails with Booking not found. or Booking not found or already finalized.
  • A database error reading or updating a named booking fails the step with Could not read the booking. or Could not update the booking.
  • A failed record does not stop the run: the step shows as failed in the run's Activity tab and the flow moves straight to the next one, with the booking left exactly as it was.

Limits

  • It cannot move a booking that is not confirmed — a booking already marked completed, no-show or canceled cannot be re-marked, in either direction, by this step or by the page.
  • Left with no booking id, and with more than one confirmed booking on this conversation, it finalises whichever one starts latest — not necessarily the one that just happened. Name the booking id explicitly when that matters.
  • It does not message the customer. Whatever should follow a no-show or a completion is a separate step, or the workflow the Booking Status Changed trigger starts.
  • The follow-up trigger only fires when the booking is linked to a conversation; a booking with none records the status change but starts no flow.

Use cases

  • Mark Completed after a calendar webhook posts that the appointment finished, then move the contact's lifecycle stage forward.
  • Ask "Did you make it to your appointment?" and mark No show on a "no" answer, triggering a reschedule flow.

Reading this with an AI assistant? Plain Markdown version.