# Communication Within The Remedy Platform

* **Comprehensive out-of-scope section**

  Please take time to compose a comprehensive out-of-scope section. This will help avoid low-quality reports and associated costs.
* **Always add comprehensive explanations.**

  Provide comprehensive explanations when making decisions, such as rejecting a report, changing its severity, or taking any other action. This will help prevent misunderstandings.

  Ensure that your message addresses potential questions and clarifies the reasoning behind your decision.
* **Prioritize prompt responses**

  Strive to respond promptly in report threads within the [provided timeframes](/main/bug-bounty/organizations/organization-handbook/response-times.md). Adhering to these timeframes is highly recommended, as long delays can negatively impact the community’s perception of your business.
* **Technical support by the Remedy experts** \
  You can always reach out to us in the same report thread with pretty much any question. Whether you need bug report interpretation, technical support, or follow-ups, our team will serve your interests best.
* **Conflicts and misunderstanding**\
  Minor conflicts and misunderstandings are part of human nature. If you encounter any issues, please know that the Remedy team is here to support you. Approach these situations with understanding and patience. Your prompt and considerate response is crucial and greatly appreciated.

{% hint style="info" %}
**Stay professional with us**

While you might find the rules above common sense, we also encourage you to read through [Remedy T\&C](https://docs.r.xyz/main/policies/terms-and-conditions). :heart:

Your satisfaction and positive experience are our top priorities, and while we continuously strive to improve, your cooperation is the cornerstone of our efforts.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.r.xyz/main/bug-bounty/organizations/organization-handbook/communication-within-the-remedy-platform.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.