> 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/end-user-and-partner-section/end-user-section/technical-support-in-docbits/support-page.md).

# Support page

The **Support** page is the single place to get unstuck: find the page or setting you are looking for, open the help for the page you just left, or send the support team a ticket. Open it from **Support** in the left sidebar.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-8c8d7be3e5d424517f2fab9baa86e4fc058417a1%2Fsupport-page-en.png?alt=media" alt="The Support page with the heading How can we help, the Find a page or setting search box and the Contact support form with E-Mail, Name, Category, Subject, Priority and Message"><figcaption><p>The Support page: find a page, get help for where you came from, or send a ticket.</p></figcaption></figure>

## Find a page or setting

Often you do not need a ticket — you need the right screen. Type what you are looking for into **Search all pages…** under **FIND A PAGE OR SETTING** and DocBits lists the matching pages and settings.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5025403234ceec9158748df9abfee12d4b903f8f%2Fsupport-page-search-en.png?alt=media" alt="The page search with the word import typed in, listing matching pages and settings such as Import and Import Log"><figcaption><p>The search covers pages and settings, not just top-level menu entries.</p></figcaption></figure>

* The search opens with **Ctrl+K** as well.
* Results open in a **new tab**, so anything you have already typed into the ticket form below is kept.
* You only see what you may use: pages from the modules your organisation has enabled, and only those your permissions allow. Administrator-only pages are not listed for other users.

This is the same search as on the "page not found" screen, so the behaviour is familiar.

## Help for the page you came from

When you open Support from another screen, DocBits adds a **HELP FOR THE PAGE YOU CAME FROM** section and names that page, for example `/settings/import`.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-6ce3a3d63ba1f3ff00e7281dae64330990bd936c%2Fsupport-help-en.png?alt=media" alt="The Support page opened from Settings Import, showing Help for the page you came from /settings/import with a Documentation tile reading Read the guide for this page"><figcaption><p>Opened from Settings → Import, Support offers the help that belongs to that page.</p></figcaption></figure>

Up to two tiles appear, depending on what exists for that page:

| Tile                     | What it does                                                                                   |
| ------------------------ | ---------------------------------------------------------------------------------------------- |
| **Watch training video** | Plays that page's training video in the **Videos & Tutorials** panel, without leaving Support. |
| **Documentation**        | Opens the docs.docbits.com article for that page in a new tab.                                 |

If a page has neither a video nor an article, the section is left out. Reaching Support directly from the sidebar — rather than from a specific screen — also leaves it out, because there is no page to offer help for.

## Send a ticket

**Contact support** sends a structured ticket to the DocBits support team, who reply by e-mail.

Fill in the main part of the form:

| Field                 | Notes                                                                                                                                                      |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **E-Mail** / **Name** | Your address and name, so the team can answer. Administrators enter them; other users see their own name and address shown as a "sending as" line instead. |
| **Category**          | **Bug**, **Question**, **Feature request** or **Other**. Choosing the right one routes the ticket faster.                                                  |
| **Subject**           | One line naming the problem.                                                                                                                               |
| **Priority**          | **Low**, **Medium** (the default), **High** or **Urgent**.                                                                                                 |
| **Message**           | What happened, in your own words.                                                                                                                          |

### Add more details

Open **More details** — *Page, document, expected vs. actual, files* — to give the team what they usually have to ask for.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-233c779bd9f1994654355800602202fd73a918d2%2Fsupport-more-details-en.png?alt=media" alt="The expanded More details section with the fields Page, Document ID, Expected, Actual and the Upload file and Screenshot buttons"><figcaption><p>More details: the context that turns a report into something reproducible.</p></figcaption></figure>

| Field           | What to put in it                                                                    |
| --------------- | ------------------------------------------------------------------------------------ |
| **Page**        | The screen where the problem happens. Prefilled with the page you came from.         |
| **Document ID** | The document the problem occurred on, when it concerns one specific document.        |
| **Expected**    | What you expected DocBits to do.                                                     |
| **Actual**      | What it did instead.                                                                 |
| **Upload file** | A file that shows the problem — for example the invoice that was not read correctly. |
| **Screenshot**  | A picture of the screen as you see it.                                               |

{% hint style="warning" %}
Never put a password, an API key or a one-time code into the message, a screenshot or an uploaded file. Support never needs them.
{% endhint %}

Select **Send** to submit the ticket, or **Cancel** to discard the draft. DocBits confirms when the ticket has been sent.


---

# 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/end-user-and-partner-section/end-user-section/technical-support-in-docbits/support-page.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.
