> 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-limits-and-follow-up.md).

# Referral limits and follow-up

## Referral submission limit

Perkville applies an anti-abuse limit of **500 referrals per referring customer, per business, in a rolling 24-hour period**.

This is a system-level safeguard rather than a business-configurable referral-program setting. When the limit is reached, additional referral submissions are rejected until earlier referrals fall outside the rolling 24-hour window.

For API integrations, this condition is returned as `pv_referral_max_limit`.

{% hint style="info" %}
This limit is based on a rolling 24-hour period, not a calendar day.
{% endhint %}

## Referral emails and reminders

When a customer enters a friend's information in Perkville, Perkville can send the initial referral email containing the referral offer. Perkville can also send transactional referral emails associated with events such as an offer being claimed.

Perkville does **not** send an automated follow-up reminder cadence to referral prospects who have not claimed an offer or who have claimed an offer but have not yet completed the referral.

## Following up through a CRM

Perkville can integrate referred prospects with supported CRM and sales systems. Those systems can typically be used to configure your own follow-up workflows, email or text sequences, task reminders, and sales cadences.

See [Integrations](https://docs.perkville.com/integrations/overview.md) for an overview of Perkville's CRM and marketing integration capabilities.

{% hint style="info" %}
The availability and behavior of CRM follow-up automation depends on the CRM, the integration, and your configuration in that system.
{% endhint %}


---

# 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-limits-and-follow-up.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.
