> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/support-and-community/roc-support.md).
# Rewst support
{% hint style="warning" %}
These instructions apply only to the Rewst Classic product, not our new Rewst product. For support info for new Rewst, see our guidance [here](https://docs.rewst.help/rewst-documentation/support-and-community/roc-support).
{% endhint %}
Our support team is here to assist with all Rewst Classic platform-related questions and technical guidance. They're not a fit to talk about account issues or commercial needs such as contract, billing, or general relationship questions. For those, please contact your Customer Success Advisor (CSA).
{% hint style="info" %}
**Other resources who help**
During your onboarding process, you'll be working with one of our onboarding partners to help you get set up. If you're experiencing issues during your onboarding process, reach out to the onboarding partner as your first step.
Once you're through onboarding, you'll be assigned a *customer success advisor*, or *CSA,* for all your account needs. Reach out to your CSA for all your strategic, but not necessarily technical, questions and concerns.
{% endhint %}
## Rewst support operating hours
Our support team provides **24-hour coverage from Monday to Friday**, ensuring uninterrupted assistance across the globe. Due to our global presence, our actual coverage runs as follows:
**Note:** Between **October and March**, there is a brief daily support gap from **5:00 AM to 7:00 AM UTC** due to daylight saving time differences between regions.
| Region | Time Zone | Support Start | Support End |
|---|
| Americas | ET | Sunday 4:00 PM | Friday 7:00 PM |
| Europe | CET | Sunday 10:00 PM | Saturday 1:00 AM |
| Australia | AET | Monday 6:00 AM | Saturday 9:00 AM |
Learn more about our support priority levels [here](/support-and-community/roc-support/support-priorities.md).
## How to log a support ticket
To create a support request, you have several options.
* Email: Send your request to
* Self-Service Portal: Log in and submit a ticket at
* Discord: You can send a message to our team via your private customer channel in Discord. We aim to respond to these messages within 60 minutes.
* [Create a ticket via Discord](/support-and-community/roc-support/create-a-ticket-via-discord.md). This will alert our support team and they'll respond as quickly as possible.
## Our commitment
We're committed to providing you with an excellent support experience. If you would like to speak with a member of the support leadership team, please submit a ticket and we'll be in touch.
---
# 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.rewst.help/support-and-community/roc-support.md?ask=&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.