> 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/automated-redemptions.md).

# Automated redemptions

Perkville's integration with Mindbody allows for the automatic credit of full services and account credits. This means that upon redemption the service or credit will be automatically applied to the client's account in Mindbody.

## Service credits

The application of service credits is facilitated by a legacy native integration in Perkville. To set up the automated distribution of service credits, please follow the below steps:

1. Go to the **Integration** page in your Perkville dashboard
2. If your Mindbody sites are already connected, click edit next to each location
3. If you have not already connected your Mindbody sites, select Mindbody from the dropdown and click connect. You'll need to enter your Mindbody site ID. Once connected, select the relevant location in **Step 2** of the integration page.
4. Scroll to **Step 4** on the integration page and click connect next to any of the rewards you want to automatically distribute credits for. You'll then have a list of services to select from.

{% hint style="danger" %}
Most Perkville-Mindbody integrations are now handled by Middle, our integration platform. Please do not connect any of your earning activities on the integration page without consulting your Perkville representative. Connecting earning activities can risk duplicate points being awarded.
{% endhint %}

## Account credits

Automated account credit rewards apply a balance to a client's account. This can be used for purchases in MINDBODY, including a client's autopay.

Please refer to the below doc to apply an account balance to an autopay:

{% embed url="<https://support.mindbodyonline.com/s/article/How-can-I-apply-a-client-s-account-credit-to-their-autopay?language=en_US>" %}

### Initial voucher status

When setting up a reward for an account credit, you must set the initial voucher status as **Pending further processing**. This status triggers the integration to process the redemption and apply the account credit in MINDBODY.

{% hint style="info" %}
This initial status is not needed for service credits
{% endhint %}

## Other rewards

Rewards that are not connected to automatic service or account-credit fulfillment can use a Perkville voucher. The customer presents the voucher to staff, who fulfill it according to the reward terms—for example, with a coupon or a [Perkville payment type](https://docs.perkville.com/integrations/integration-reference/mindbody/creating-a-perkville-payment-type.md) in MINDBODY. Staff then mark the voucher used in Perkville. Printed voucher barcodes can be scanned in Perkville to mark them used.

Confirm the expected processing time for your connected reward with your CSR. Do not repeatedly redeem or manually apply another credit while an earlier fulfillment is being investigated.


---

# 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/automated-redemptions.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.
