> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/system/technical-support.md).

# Technical Support

## **Bug report**

To ensure the effectiveness of reports, the conditions of this procedure must be met. The following reporting channels are available:

1. email address: **<center@btc.com.pl>,**
2. telephone contact – available in selected technical support options.

<details>

<summary><strong>Bug report</strong></summary>

To ensure the effectiveness of reports, the conditions of this procedure must be met.

1. The following reporting channels are available:
   1. email address: **<center@btc.com.pl>,**
   2. telephone numbers available on business days (option),
2. When making a report, the following must be provided:
   1. contact details of the person designated on the reporting side for contact within the report,
   2. a possibly detailed description of the problem, including any actions already taken to resolve the problem, if any have been taken,
   3. the name of the application to which the problem relates,
   4. specification of the report category and/or business impact,
   5. the date and time the problem occurred.
3. A report sent to the monitored inbox “**<center@btc.com.pl>**” is acknowledged by confirmation of receipt of this report. Lack of confirmation means that the report did not reach the Contractor.

</details>

<details>

<summary><strong>Report processing</strong></summary>

1. Report verification: the report is verified in terms of type and assigned to the appropriate consultant.
2. If verification or handling of the report requires remote or direct access to the Software, the reporter must ensure such access.
3. If configuration files, logs, or other additional information are needed for proper handling of the report, the reporter should provide access to them.
4. The consultant dedicated to handling the report begins work as soon as possible, in accordance with report priorities and within the service hours.

</details>

<details>

<summary><strong>Report status</strong></summary>

Reports may have the following statuses:

* **OPEN** – report registered in the system,
* **IN PROGRESS** – report under work,
* **PENDING** – completed reports, not verified by the Reporter,
* **CLOSED/RESOLVED** – report completed, verified by the Reporter and confirmed,
* **REOPENED** – closed report in which the same bug was detected later (not revealed during testing).

</details>

<details>

<summary><strong>Report acceptance</strong></summary>

1. The Reporter is informed about the work performed and the status of the report by the consultant via email.
2. The consultant marks the report as “closed / resolved”.
3. If the Reporter later detects previously undisclosed defects related to this report, they shall report this fact immediately, and the report will be reopened and verified.
4. If there is no response to the information about the completed report acceptance for 7 days, the report acquires the status of resolved.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://bluurdoc.bluur.ai/en/system/technical-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.