> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/subscriptions-klaviyo-integration/subscription-created-email-flow.md).

# Subscription created email flow

Confirm every new subscription: what they subscribed to, the frequency, and when the first renewal lands.

The subscription confirmation is the first email of the relationship and the cheapest churn prevention you have: subscribers who understand exactly what they signed up for don't cancel in surprise at renewal one.

### Klaviyo event name

* `Roadmap: Subscription created`: fires when a new contract is created, at checkout or from the admin.

### Event properties

The full [contract snapshot](/subscriptions/subscriptions-klaviyo-integration.md), plus:

| Extra property      | What it holds                |
| ------------------- | ---------------------------- |
| `next_billing_date` | when the first renewal bills |

### Recommended flow structure

1. **Trigger:** `Roadmap: Subscription created`
2. **Email, immediately:** confirm the contract in plain terms:

```liquid
You're subscribed to {{ event.product_titles.0|default:'' }}, delivered {{ event.delivery_frequencies.0|default:'' }}.
Your next order bills on {{ event.next_billing_date|default:'' }}.
```

Include the product image (`event.product_images.0`) and the order total, and point them to their account page to manage the subscription.

### Strategy

* **Set expectations hard.** Frequency, next billing date, and how to pause or change: subscribers who know they're in control stay longer.
* **Introduce the perks once.** If subscribers earn loyalty points, receive special perks or can add one-time products to a delivery, this email is where they learn it.

### Related guides

* [Upcoming order reminders](/subscriptions/subscriptions-klaviyo-integration/upcoming-order-reminders.md)
* [The customer subscription dashboard: a tour](/subscriptions/storefront-and-accounts/the-customer-subscription-dashboard-a-tour.md)


---

# 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://docs.roadmap.so/subscriptions/subscriptions-klaviyo-integration/subscription-created-email-flow.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.