> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/faq/support-system-how-to-create-a-ticket.md).

# Support System: How to create a ticket?

When you are facing an unexpected behaviour in GUIBO or the GUIBO App, the best way to notify us is by creating a ticket in the support system.

Open the page[ https://schneidergeo.atlassian.net/servicedesk](https://schneidergeo.atlassian.net/servicedesk)

1. **Select your issue type**\
   Select whether the error is in the "GUIBO ISSUE" system or on your "APP ISSUE" app. 

2. **Send your documetation via text or video**\
   Now add all relevant information. This can be done via text description or video-screenrecording.&#x20;

   1. **Text:** Please make sure that you describe the problem as precisely as possible. This means a step-by-step explanation of the previous steps until the problem occurs.&#x20;
   2. **Screenrecording:** \
      In the ticket form, you will find the "click here" screen recording button at the bottom of the screen, above the "send" button. Click on it to start the screen recording. Select the GUIBO tab for the recording and demonstrate the problem behavior.&#x20;

   <figure><img src="https://4249329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE2a888ltdx6dUekSgs4U%2Fuploads%2FpVgBHT9iNZqPlTFTKzyZ%2FBildschirmfoto%202024-04-03%20um%2011.13.47.png?alt=media&amp;token=943327f1-a509-495e-b008-ee518af76e54" alt=""><figcaption><p>"click here"-Button for screenrecording</p></figcaption></figure>

3. **Send us all required information**\
   Make sure you have filled out all the form fields. If information is missing, we cannot process your request.

4. **Attach screenshots**\
   For illustration you have the option to insert a picture (screenshot) here. Info: You must have created this before creating the ticket.

![](https://4249329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE2a888ltdx6dUekSgs4U%2Fuploads%2FXwWLWgzyqXAzgQ6nKqkP%2FVideoaufnahme%20einf%C3%BCgen.JPG?alt=media\&token=2b1aa788-029d-41ff-9a26-ee89944b8ca0)


---

# 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.guibo.travel/faq/support-system-how-to-create-a-ticket.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.
