> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/help-and-support/share-feedback.md).

# Share feedback

You can share your thoughts with the Marketplace Product team to help us improve. We welcome your feedback on what you liked and didn't like, and ideas for enhancements. 

When submitting feedback, you can rate your experience using any of the five emoticons, ranging from very dissatisfied to very satisfied. Additionally, you can describe your feedback and attach files. 

When writing feedback, consider the following best practices:

* **Be concise** – Limit your review to 2000 characters, including spaces.
* **Attach files** – Include images or screen recordings to help us visualize your feedback.
* **Be specific** – Share both the positive and negative aspects. For new features and enhancements, explain your use case and how it benefits you.
* **Focus on actions, not individuals** – Describe your experience with the platform, its features, and workflows, instead of naming individuals.

{% hint style="info" %}
Do not use the feedback form to request assistance. If you encounter an issue with Marketplace or SoftwareOne FinOps for Cloud, [contact support](/help-and-support/contact-support.md). 
{% endhint %}

### Share feedback <a href="#share-feedback" id="share-feedback"></a>

To submit feedback:

1. Select the help icon <i class="fa-circle-question">:circle-question:</i> in the header.
2. Select **Share feedback**.

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FshufLExFjAl3wm5fC5EA%2Fimage.png?alt=media&amp;token=a164ec9f-ef08-4ee8-9b50-18e8aabf6e78" alt=""><figcaption><p>Select Share feedback to share your feedback.</p></figcaption></figure></div>

3. In the **feedback** form, do the following:&#x20;
   1. Choose an appropriate rating for your experience.
   2. Enter a subject line for the feedback.
   3. Describe your feedback with as much detail as possible.
   4. Choose whether to keep the automatic screenshot or replace it with another file. Only one file can be attached, but you can add more files by editing your feedback after submission. For details, see [Edit or delete feedback](/modules-and-features/helpdesk/feedback/edit-or-delete-feedback.md).
   5. Select **Submit**.
   6. Select **View details** to view your feedback or select **Close**.

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FQ7ix46VDl5Sh7qmUE0Og%2Fimage.png?alt=media&amp;token=d4b08756-8345-4581-bfdb-3453d6d9cc7b" alt=""><figcaption><p>Rate your experience and describe your feedback.</p></figcaption></figure></div>


---

# 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.platform.softwareone.com/help-and-support/share-feedback.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.