Klaviyo wiring guide

Hollow Reserve journey metrics, event properties, and sample Klaviyo flows for client lifecycle email.

Hollow Reserve sends track events to Klaviyo when journey sync is enabled. Each event identifies the client by email and client ledger ID. Build flows in Klaviyo triggered by these metrics — Reserve does not email clients directly except optional Resend confirmations.

How it works

  1. Connect Klaviyo in Reserve Settings and enable journey sync (Professional+).
  2. Complete a real booking or status change on your storefront or Calendar.
  3. In Klaviyo Analytics → Metrics, confirm the Hollow Reserve metric appears.
  4. Create a flow with a Metric trigger using the exact metric name below.
  5. Use event properties in email templates (for example blueprintName and startsAt).

Journey metrics

Reserve eventKlaviyo metricWhen it fires
Appointment bookedHollow Reserve: Appointment BookedBooking confirmed without a pending deposit checkout
Deposit paidHollow Reserve: Deposit PaidShopify checkout completes for a deposit-linked booking
Appointment completedHollow Reserve: Appointment CompletedStaff marks appointment completed in Calendar
Appointment cancelledHollow Reserve: Appointment CancelledStaff cancels an appointment
Appointment no-showHollow Reserve: Appointment No-ShowStaff marks appointment as no-show
Journey completedHollow Reserve: Journey CompletedClient finishes every stage of an Experience Blueprint

Appointment Booked flow

Trigger: Hollow Reserve: Appointment Booked. Properties: blueprintName, startsAt (ISO datetime), appointmentId, instanceId, blueprintId.

  1. Create flow → Metric → Hollow Reserve: Appointment Booked.
  2. Optional: Wait 5–15 minutes if Resend also sends an instant confirmation.
  3. Email 1: Branded confirmation with experience name and formatted startsAt.
  4. Email 2 (−24h before appointment): Prep or what-to-expect reminder.

Deposit Paid flow

Trigger: Hollow Reserve: Deposit Paid. Properties: externalOrderId, totalCents.

  1. Create flow → Metric → Hollow Reserve: Deposit Paid.
  2. Email 1: Deposit received — booking is confirmed.
  3. Follow with the same reminder sequence you use for Appointment Booked.

Appointment Completed flow

Trigger: Hollow Reserve: Appointment Completed. Properties: blueprintName, appointmentId.

  1. Create flow → Metric → Hollow Reserve: Appointment Completed.
  2. Wait 1–4 hours, then send thank-you and aftercare content.
  3. Optional: Link to retail add-ons or rebook.

Appointment Cancelled flow

Trigger: Hollow Reserve: Appointment Cancelled. Properties: blueprintName, appointmentId, startsAt.

  1. Create flow → Metric → Hollow Reserve: Appointment Cancelled.
  2. Email 1: Cancellation notice with an easy rebook link.

Appointment No-Show flow

Trigger: Hollow Reserve: Appointment No-Show. Properties: blueprintName, appointmentId, startsAt.

  1. Create flow → Metric → Hollow Reserve: Appointment No-Show.
  2. Wait 2–4 hours, then send a reschedule offer.
  3. Email 2 (+3d): Final rebook nudge if no new booking.

Journey Completed flow

Trigger: Hollow Reserve: Journey Completed. Properties: blueprintName, instanceId, blueprintId. Fires when the client completes every stage of an Experience Blueprint.

  1. Create flow → Metric → Hollow Reserve: Journey Completed.
  2. Email 1: Journey complete — thank you and rebook CTA.
  3. Email 2 (+7d): Invite to the next experience, package, or membership.
  4. Optional: Create a List (no conditions) and Add to list in the flow for future nurture campaigns — see Engine Klaviyo wiring Lists vs segments.

Arcanum Engine commerce metrics

For abandoned checkout, VIP orders, and review requests, use Arcanum Engine playbooks — not Reserve journey events. Engine metrics use the Arcanum Engine - prefix.

Engine Klaviyo wiring guide

Connect Klaviyo

Was this page helpful?