> For the complete documentation index, see [llms.txt](https://help.holixa.com/holixa-tools4inventor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.holixa.com/holixa-tools4inventor/commands-overview/be.smart-t4i-labs/send-us-feedback.md).

# Send Us Feedback!

Feedback is invaluable to us as it can help us to improve the Be.Smart T4I according to your needs making it really a user-oriented productivity tool. Click the "Send feedback" button to let us know your opinions, send ideas, or simply vote for new features.

<figure><img src="/files/T01Eu7E4WSUi7Tf9D4Zh" alt=""><figcaption></figcaption></figure>

The Send feedback button will take you to the Productboard web portal, where you can:

1. Vote for proposed features, or
2. Send your own ideas.

<figure><img src="/files/CaNHOFE54euHORCIX2t2" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To submit your feedback or idea, you do not need a Productboard account; any valid email is sufficient to validate the information in the final step.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.holixa.com/holixa-tools4inventor/commands-overview/be.smart-t4i-labs/send-us-feedback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.