> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/help/get-support.md).

# Get support

Contact Render Network support, report a bug, or send feedback about the web app.

Open **Help & Feedback** near the bottom of the sidebar, then choose **Support** to open the support chat.

You can also open chat from **Help** at the bottom of an account page or **Need help? Contact support** in the **Duplicate this job?** window.

If chat does not open, use the [OTOY support request form](https://help.otoy.com/hc/en-us/requests/new).

## What to include

* The scene or job name and its ID. See [copy an ID](/docs/web-app/views.md) if you need help finding it.
* The exact error message or status, with a screenshot if it helps show the problem.
* What you were doing, what you expected, and what happened instead.
* For a render problem, the affected frame numbers and the application and renderer versions used to prepare the scene.
* For an upload, download, or display problem, your browser and operating system.

## Bugs, requests, and feedback

The **Help & Feedback** panel also contains these forms, each opening in a separate browser tab:

| Choose              | Use it for                                       |
| ------------------- | ------------------------------------------------ |
| **Bugs**            | Something in the app is not working as expected. |
| **Feature Request** | A capability you would like the app to offer.    |
| **Feedback**        | Other comments about using the app.              |


---

# 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://know.rendernetwork.com/docs/help/get-support.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.