> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/portuguese/end-user-and-partner-section/end-user-section/ressources-and-support/user-support.md).

# Supporto utenti

{% embed url="<https://youtu.be/fQUIrp-qz9c>" %}
DocBits Support Ticket Tutorial: Report Bugs, Attach Files & Get Help Faster
{% endembed %}

### Suporte ao Usuário <a href="#ikpwh4qbrq82" id="ikpwh4qbrq82"></a>

Caso enfrente desafios ou tenha dúvidas ao usar o DocBits, consulte este manual do usuário ou entre em contato com nossa equipe de suporte para obter ajuda. Nosso compromisso é proporcionar uma experiência sem problemas para todos os usuários. Basta clicar no botão de suporte em seu aplicativo DocBits e você poderá criar um ticket de suporte.

<figure><img src="https://4193417932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuAz1Yhpnxw8Gd9kza0ch%2Fuploads%2Fgit-blob-0181478c4d5833e8363b82870d52a1188f671770%2Fdocbits_docbits_image_16.png?alt=media" alt="DocBits DocBits Imagem 16"><figcaption></figcaption></figure>

<figure><img src="https://4193417932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuAz1Yhpnxw8Gd9kza0ch%2Fuploads%2Fgit-blob-f384d8992bd1d614f15e93f18d0d9ac5bb2c1059%2Fdocbits_email.png?alt=media" alt="DocBits E-mail"><figcaption></figcaption></figure>

Você também pode entrar em contato conosco por meio de nossa página FELLOWPRO:

{% embed url="<https://fellowpro.com/de/fellow/kontakt-fellowpro-ag/>" %}

Dentro da Tela de Validação, você pode criar tickets diretamente para o documento específico e incluir uma captura de tela do problema. Basta clicar no botão "Criar ticket", a janela de suporte se abre e você pode começar imediatamente.

<figure><img src="https://4193417932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuAz1Yhpnxw8Gd9kza0ch%2Fuploads%2Fgit-blob-78c86ce44fdb049446d1c259449b6af2bc7e36bd%2Fuser-support3.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4193417932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuAz1Yhpnxw8Gd9kza0ch%2Fuploads%2Fgit-blob-920bc9aad80086ebb4536fa7140ee625c8517e55%2Fuser-support4.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.docbits.com/portuguese/end-user-and-partner-section/end-user-section/ressources-and-support/user-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.