> 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/configure-the-referral-form-layout.md).

# Configure the referral form layout

Choose how you want customers to share the referral offer:

* **Share Offer Layout (Recommended)**: This layout allows customers to share the referral offer through their own communication channels, such as text or email. It does not request the friend’s name or email, ensuring that the message is sent directly by the customer. This option supports CASL compliance best practices.
* **Share Offer and Enter Friend's Information Layout**: This layout enables customers to enter their friend’s name and email address so that Perkville can send the referral offer on your behalf. You can also specify whether the friend's first and last name are required. The referring member’s name is automatically included in the subject line and body of the email for transparency.


---

# 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/configure-the-referral-form-layout.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.
