> 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/miscellaneous/i-need-to-change-the-support-email-that-displays-in-the-footer.-how-can-i-do-that.md).

# I need to change the support email that displays in the footer. How can I do that?

To update the "SUPPORT" link in the footer, follow these steps:

1. Navigate to the "[Business info](https://docs.perkville.com/features/settings/business/business-info.md)" section under "Settings."
2. Locate the following fields:
   * **Support site:** If a URL is entered here, it will take precedence, and the "SUPPORT" link will direct users to this web page.
   * **Reply to email address:** If the "Support site" field is blank, the "SUPPORT" link will instead point to the email address specified here.

Ensure to save changes after updating these fields to reflect the desired support contact information in the footer.


---

# 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/miscellaneous/i-need-to-change-the-support-email-that-displays-in-the-footer.-how-can-i-do-that.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.
