> 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/emails/invitations.md).

# Invitations

Invitation emails encourage your clients to register for the rewards program. These emails are automatically triggered when a customer performs an activity that would normally earn points, ensuring they have a reason to sign up.

{% hint style="warning" %}
If a customer does not perform a point-earning action, they will not receive an invitation email.
{% endhint %}

## **Invitation Limit**

To prevent excessive emails, a maximum of one invitation is sent every 7 days per customer. A customer will only receive up to 10 invitation emails before we stop sending.

## **Types of Invitation Emails**

Perkville sends one of two types of invitation emails, depending on whether your business allows customers to earn points before joining the loyalty program:

### **1. For Businesses That Allow Customers to Earn Points Before Joining**

If your business allows customers to earn points before they officially join the loyalty program, the invitation email will prompt them to **accept the points they have already earned**. This ensures that they recognize the value of the program and feel motivated to continue engaging with your business.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FEyOOIaNMZXjQ7RBnnD0U%2FPerkville_invitation_email1.png?alt=media&amp;token=5b21eb3a-6268-43e8-b399-193880465e51" alt="Email invitation if customer earns points before joining" width="315"><figcaption></figcaption></figure>

### **2. For Businesses That Require Customers to Join Before Earning Points**

If your business requires customers to join the loyalty program before they can earn points, the invitation email will prompt them to **accept the registration bonus points** they receive for signing up. This provides an immediate incentive for them to participate.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FV3cOrQar72J2Tlx8qxdO%2FPerkville_invitation_email2.png?alt=media&amp;token=8a666cf7-ced8-4399-8c8f-b05ae16e2f05" alt="Email invitation if customer does not earn points before joining" width="311"><figcaption></figcaption></figure>

## Disabling point earning notifications

Within an earning activity's setting, you can disable invitations and point-earning notifications by toggling **Prevent Email** on.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FDxGkq0btfXIS1snLxr8m%2FScreenshot%202025-03-26%20at%2012.06.17%E2%80%AFPM.png?alt=media&amp;token=c448503e-bffb-44ef-a8f0-4f27895d095c" alt=""><figcaption><p>Earning activity with Prevent Email turned on</p></figcaption></figure>


---

# 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/emails/invitations.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.
