> 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/whats-new/readme/power-users-program.md).

# Power Users Program

GUIBO Power Users: Early access program for tour operators and agencies to test new features, provide prioritized feedback, and improve travel experiences through collaborative app development.

### What Are Power Users?

Power Users are select users who gain early access to the latest GUIBO features before general release. This exclusive program allows you to test new functionalities, provide valuable feedback, and directly influence the app's development.

### Becoming a Power User

Power Users are typically experienced partners from tour operators who:

* Have regular interaction with the GUIBO platform
* Are interested in innovative travel technology
* Want to shape better travel experiences for their customers
* Can provide consistent, quality feedback

If you're interested in becoming a Power User and gaining early access to new features, please open a ticket through our support system.

### Providing Valuable Feedback

The quality of feedback significantly impacts how effectively we can address issues. While we review all submissions, our ability to implement improvements depends on the information provided.

### Feedback Prioritization

When submitting feedback, please use this prioritization scale:

* **Highest**: Critical bug blocking core functionality
* **High**: Significant issue that substantially limits usage
* **Medium**: Relevant problem with acceptable workarounds
* **Low**: Minor issues with minimal impact
* **Lowest**: Cosmetic bugs or improvement suggestions

A realistic classification from your end customers' perspective helps us understand the true impact of issues.

### Effective Bug Reporting

The most actionable feedback includes:

* Exact steps to reproduce the bug
* Detailed description in the ticket
* A video demonstrating the bug (when possible)

Bugs that can be consistently reproduced receive priority attention. While non-reproducible issues may be reported, they are considerably more challenging to investigate and resolve.


---

# 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/whats-new/readme/power-users-program.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.
