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

# Finding Support

Rechat provides you with various means to get support regarding issues you might face while working with your Rechat product.

{% embed url="<https://rechatq.wistia.com/medias/b7q3jpw4on>" %}

### Unexpected server error (500)

You may see: “Unexpected server error (status 500). Contact support if the problem persists.”

Status 500 means the server could not complete your request while processing it. The message does not identify the exact cause. Investigating requires request context and server-side diagnostics that you cannot access.

1. Retry the action once.
2. Refresh the page or reopen the affected workflow. Then try again once, if appropriate.
3. If the action might have created, sent, submitted, or changed something, check the relevant record or workflow first. Do not repeatedly submit the action. It may have partially completed.
4. If the problem continues, contact Rechat Support through one of the methods below.

#### What to send Support

* The affected feature or page URL.
* The approximate error time, including your time zone.
* The exact error message and steps that led to it.
* Your device and browser, or app version.
* A screenshot, only if it contains no sensitive information.

{% hint style="warning" %}
Never send passwords, MFA codes, API keys, or other secrets to Support.
{% endhint %}

### 💻 Rechat Support on Web

From anywhere in Rechat, open the sidebar navigation and hover over Support and click Customer Support. This will open a live chat with a member of our support team.

### 📱 Rechat Support on Mobile

From the Today page in the Rechat mobile app tap the question mark icon in the upper-right corner of your screen, then tap "Need Help? Chat with us!". This will open a live chat with a member of our support team.

### 📧 Rechat Support via Email

Members can always email **<support@rechat.com>** and a member of our support team will get back to you as quickly as possible. Rechat's median response time is under one (1) minute, so stay close to your email! We love supporting our members.

### ⌚️ Rechat Support Hours

Support is available Weekdays (M-F) from 7 am to 7 pm Central and Saturdays from 8 am to 4 pm.

{% hint style="info" %}
Download your [**Support**](https://drive.google.com/file/d/12096vf6OAlOWgmMGIXB-xD1LM_JNDK-Z/view?usp=drive_link) guide today!
{% endhint %}


---

# 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://help.rechat.com/appendix/contacting-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.