> 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/loyalty-and-rewards/loyalty-klaviyo-integration/referral-invitation-emails.md).

# Referral invitation emails

Deliver the referral invitation to the friend with the Roadmap: Loyalty Referral Share metric.

When a member shares a referral, this flow delivers the invitation to their **friend** — the first email your brand ever sends that person, arriving with borrowed trust.

### Klaviyo event name

* `Roadmap: Loyalty Referral Share` — fires when a customer shares their referral. The event is attached to the **friend's** email address.

### Event properties

| Data point                                         | Event property   |
| -------------------------------------------------- | ---------------- |
| Referral link                                      | `referral_link`  |
| Friend's email                                     | `referral_email` |
| Referrer's name                                    | `referrer_name`  |
| The friend's reward                                | `reward_name`    |
| Coupon code (when the friend reward is a discount) | `coupon_code`    |
| Customer ID                                        | `customer_id`    |

### The pre-built flow

1. **Trigger:** `Roadmap: Loyalty Referral Share`
2. **Email — immediately:** "Someone thinks you'll love \[insert brand name]" — delivering `{{ event.coupon_code|default:'' }}` for their first order

Fill the *\[insert brand name]* placeholder.

### Strategy

* **Lead with the referrer.** `{{ event.referrer_name }} thought you'd love us` converts far better than an anonymous discount — the recommendation is the product.
* **Make the reward unmissable**: `{{ event.reward_name }}` and the code above the fold.
* Remember this is a cold inbox — keep it short, one CTA, no navigation maze.

### Related guides

* [Referral completed emails](/loyalty-and-rewards/loyalty-klaviyo-integration/referral-completed-emails.md) — the other half of the pair
* [Manage referrals](/loyalty-and-rewards/membership-tiers-and-referrals/manage-referrals.md) — configuring the rewards themselves


---

# 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/loyalty-and-rewards/loyalty-klaviyo-integration/referral-invitation-emails.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.