> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/mindbody/referral-lead-sync.md).

# Referral lead sync

Perkville can send referred friends to Mindbody after they claim a [referral offer](https://docs.perkville.com/features/referrals/configuring-your-referral-program/referral-offer.md). Their contact details and referral information appear on a Mindbody client profile, giving your team a starting point for follow-up.

{% hint style="info" icon="gear" %}
This feature must be enabled for your business and participating sites. Contact your Perkville Customer Success Representative or [Perkville Support](https://docs.perkville.com/overview/support.md) to get started.
{% endhint %}

## How it works

1. **A customer refers a friend.** The customer shares a referral link or sends an invitation through Perkville.
2. **The friend claims the referral offer.** Perkville creates a voucher for the [referral offer](https://docs.perkville.com/features/referrals/configuring-your-referral-program/referral-offer.md). Sending an invitation alone does not send the lead to Mindbody.
3. **The lead sync runs.** For a site included in your setup, the integration creates or updates the friend's client profile in the connected Mindbody site.
4. **Your team follows up.** Use the profile to help the friend book a visit or take the next step with your business.

The sync processes referral offer vouchers automatically, including updates to those vouchers. It does not require the friend to use the voucher first.

{% hint style="warning" icon="timer" %}
Expect leads to end up in Mindbody 5-30 minutes after claiming the referral offer
{% endhint %}

## What appears in Mindbody

| Information        | What is sent                                                                                                        |
| ------------------ | ------------------------------------------------------------------------------------------------------------------- |
| Name               | The friend's first and last name from Perkville.                                                                    |
| Email              | The friend's primary email address in Perkville.                                                                    |
| Mobile phone       | The phone number available in Perkville.                                                                            |
| Referral source    | The **Referred By** text is set to `Perkville`.                                                                     |
| Referring customer | A **Referred By** client relationship is sent using the referring customer's linked Mindbody profile for that site. |
| Lead channel       | `Referral`, when a lead channel with that name exists in the connected Mindbody site.                               |

{% hint style="info" icon="phone" %}
If phone follow-up is part of your process, you can require a phone number through [Referral offer claim options](https://docs.perkville.com/features/settings/advanced/referral-offer-claim-options.md).
{% endhint %}

{% hint style="warning" icon="people-pants" %}
The referring-customer relationship depends on Perkville being able to identify that customer's Mindbody profile for the relevant site.
{% endhint %}

## What if the friend already has a Mindbody profile?

When Perkville already has a linked Mindbody client ID for the friend at that location, the integration updates that profile.

Otherwise, it attempts to create a profile. If Mindbody reports an exact duplicate, the integration checks the referred friend's first name, last name, and email address. It updates the existing profile only when Mindbody returns one matching client. If the match is unclear, the sync stops for review rather than choosing a profile.

Existing profiles may receive updated contact and referral information from Perkville. A first name, last name, and email address are required when creating a new profile.

## Common questions

### Does this award the referring customer points?

The lead sync creates or updates the Mindbody profile. Referral rewards follow your Perkville program's completion rules. See [Completing a referral](https://docs.perkville.com/features/referrals/completing-a-referral.md).

### Does this add the offer, a free class, or a membership in Mindbody?

This sync sends the client's contact and referral information. It does not add a class, service credit, or membership, or mark the voucher as used. Follow your offer's redemption instructions to fulfill the offer.

### Does this start a marketing campaign?

Your team manages follow-up in Mindbody or your connected marketing tools. The lead sync does not configure campaigns or set email or SMS marketing opt-in preferences.

### A claimed offer is missing from Mindbody. What should we check?

Confirm that the friend claimed the offer, that the chosen location is included in your setup, and that their name and email are complete. Search Mindbody for an existing profile, since the sync may have updated one.


---

# 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.perkville.com/integrations/integration-reference/mindbody/referral-lead-sync.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.
