> For the complete documentation index, see [llms.txt](https://docs.received.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.received.ai/partner-billing/the-referral-billing-process/set-up-referrals.md).
# Set Up Referrals
## Step 1: Create a Partner
Navigate to the **'Customers Tab'** and click on **'New Customer'**. Fill in the partner information and turn on the **'Partner'** toggle to mark it as a partner.
## Step 2: Create a Customer Contract, Attach Partner, and Define Referral Fees
Navigate to the **'Customers Tab'** and click on **'Create a Contract'.** Click on **'Search'** to add the relevant customer to the contract. Continue to add products and customize the contract (see the full contract creation process [here](/enterprise-contract-billing/the-enterprise-contract-billing-process/set-up-enterprise-contracts.md)). \
\
Once the customer contract is complete, **attach the relevant referral partner**.
Once you attach a partner, a new tab will appear - **'Partners'.** Use the partners tab to define your partner fees. You can define one fee **for the whole contract**, or define separate fees for **each product** in the contract.
##
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.received.ai/partner-billing/the-referral-billing-process/set-up-referrals.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.