> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/getting-started/faq/technical-support-workhours.md).

# Technical Support Workhours

Technical Support is provided on days that are not weekends or holidays in the Republic of Lithuania from 8 a.m. to 5 p.m. Eastern European Time (11 a.m. – 8 p.m. Central Standard Time \[North America], 2 p.m. – 10 p.m. China Standard Time)

Technical Support services will be provided within the period of the paid License Agreement (i.e., during your active Maintenance or active annual subscription contract period)

Technical Support includes assistance with downloading, installation, and activation, as well as quick tips and fixes for any software issues

{% hint style="info" %}
Technical Support does not include customization of Revit families and configurations, training, or consultation for the User.

The latter services are available to purchase upon your needs.
{% endhint %}

Technical Support includes assistance by e-mail or phone. The Technical Support team can be contacted by filling out the [**support request form**](https://emea.support.arkance.world/hc/en-gb/requests/new)

{% hint style="success" %}
The Technical Support team will respond within 24 hours for minor problems and 48 hours for problems of a more complex nature
{% 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://docs.besmart.software/getting-started/faq/technical-support-workhours.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.