> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/apps-integrations/klaviyo.md).

# Klaviyo

Klaviyo is a marketing automation platform for email and SMS. Sesami and Klaviyo are strategic partners: send your Sesami bookings to Klaviyo and use them to power confirmations, reminders, follow-ups and segments, alongside the order and marketing messages you already send there.

## What You Can Do

* **Booking confirmations and updates** — email or SMS when a booking is made, rescheduled or cancelled
* **Reminders** — before the visit, at the timing you choose
* **Follow-ups after a visit** — review requests, product recommendations or a rebooking offer
* **Win-backs** — reach out after a cancellation or a no-show
* **Segments** — group customers by how they book
* **Revenue reporting** — attribute revenue in Klaviyo to the bookings your flows drive

## Two Ways to Connect

|                                | **Klaviyo App**                                                       | **Sesami Flows with Klaviyo**                                                      |
| ------------------------------ | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Setup**                      | Install the app and connect Klaviyo in a few clicks. No API key.      | Create a Flow per event from the Klaviyo presets, using your own Klaviyo API key   |
| **Install from**               | Sesami Admin Portal, or the Klaviyo App Marketplace                   | Sesami Admin Portal > Flows                                                        |
| **Events**                     | Booking Created, Updated, Cancelled, Rescheduled, Checked In, No-Show | Appointment Created, Rescheduled, Customer Checked In, Started, Cancelled, No-Show |
| **Timing**                     | The moment each event happens                                         | The moment it happens, or a set time before or after it                            |
| **Reminders before the visit** | Use Sesami Flows                                                      | Yes, with the reminder preset                                                      |
| **Booking details**            | Filled in for you, the same on every event                            | Defined by each Flow's template, which you can edit                                |
| **Revenue in Klaviyo**         | Booking Created carries the booking value                             | Not included by default                                                            |
| **Status**                     | Each event shows when it was last sent, or why it failed              | —                                                                                  |
| **Plan**                       | Sesami Pro and higher                                                 | Sesami Pro and higher (webhook Flows)                                              |

See [sesami.co/pricing](https://sesami.co/pricing) for plans.

## When to Use Which

* **Start with the Klaviyo app** for confirmations, change notices, follow-ups, win-backs, segments and revenue. It's the quickest setup, needs no API key, and every event carries the same booking details.
* **Use Sesami Flows for reminders** before the visit, such as 24 hours or 2 hours ahead, and for the **Appointment Started** event. Flows can run at a set time relative to the booking.
* **Use Sesami Flows** when you need a **custom payload**, for example extra fields or a different structure for a specific flow.
* **Combine them:** the app for booking events, plus the Sesami Flows Klaviyo reminder preset for reminders. Turn off any Flow that sends the same event as the app, so customers don't get messages twice.

{% hint style="success" %}
**Mark booking messages as transactional in Klaviyo.** Confirmations, reminders and change notices are transactional, not marketing. Setting them as **Transactional**, with **Smart Sending** off, makes sure every customer receives them.
{% endhint %}

## Set It Up

* [**Klaviyo App**](https://help.sesami.co/apps-integrations/klaviyo/klaviyo-app.md) — install the app, choose events, build flows, and the booking details you can use
* [**Sesami Flows and Klaviyo**](https://help.sesami.co/automations/sesami-flows-and-klaviyo.md) — the Flow presets, your Klaviyo API key, and reminders

## Related

* [Klaviyo Transactional SMS](https://help.sesami.co/automations/sesami-flows-and-klaviyo/klaviyo-transactional-sms.md) — send booking SMS through Klaviyo
* [Sesami Flows](https://help.sesami.co/automations/sesami-flows.md) — Sesami's built-in automations
* [Notification Emails](https://help.sesami.co/notifications/notification-emails.md) — Sesami's built-in email notifications
* [Customers](https://help.sesami.co/apps-integrations/shopify/customers.md) — how customer data flows between Sesami, Shopify and Klaviyo


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sesami.co/apps-integrations/klaviyo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
