> 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/features/referrals/configuring-your-referral-program/referral-eligibility-explanation.md).

# Referral eligibility explanation

The **Referral eligibility explanation** field lets you add an optional customer-facing message that explains when a referral is eligible to earn a reward.

This message appears on the customer-facing referral page and should clearly explain any requirements the referred friend must meet for the referrer to qualify for a reward.

To update this field:

1. Go to **Settings**.
2. Under **Business**, select **Loyalty Program**.
3. Open the **Refer a Friend** section.
4. Find **Referral eligibility explanation (shown to customers)**.
5. Enter the message you want customers to see.
6. Click **Save**.

Use this field with the [**Referral reward eligibility window (days)**](/features/referrals/configuring-your-referral-program/referral-reward-eligibility-window.md) setting if you want to explain how long the referred friend has to complete the required action.

For example, if the eligibility window is set to 90 days, you could enter:

> Your referred friend must sign up for a qualifying membership within 90 days for your referral to qualify for a reward.

This helps customers understand the referral rules before they share their referral link.


---

# 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/features/referrals/configuring-your-referral-program/referral-eligibility-explanation.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.
