> 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/faqs/referrals/i-dont-want-customers-to-automatically-get-referral-points.-i-want-to-manually-complete-referrals..md).

# I don't want customers to automatically get referral points. I want to manually complete referrals.

To manage referrals manually and ensure that customers do not automatically receive referral points, follow these steps:

1. **Adjust point earning rules**: Ensure that the setting for "[Completes Referrals](/features/referrals/completing-a-referral.md)" is toggled to off for all your existing [earning rules](/features/earning-rules.md). This action prevents customers from automatically earning points when a referral is completed.
2. **Create a progress activity**: Create a new [progress activity](/features/earning-rules/activities.md). Name it something relevant to the action that should complete a referral, such as "Qualifying Membership that Completes Referral." Make sure that "Completes Referrals" is toggled to on for the activity. 
3. **Manually complete referrals**: When a referred prospect completes the required activity (e.g., purchasing a qualifying membership) you will need to give the referred prospect the progress activity on their [customer profile](broken://pages/lbkFpUWedwL4VjsAIwfe) which will trigger a [completed referral](/features/referrals/completing-a-referral.md) for the original referrer.


---

# 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/faqs/referrals/i-dont-want-customers-to-automatically-get-referral-points.-i-want-to-manually-complete-referrals..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.