> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-use-the-supplier-feedback-inbox.md).

# How to use the supplier feedback inbox

A guide to answering supplier questions and starting conversations with suppliers

Feedback threads are conversations between you and your suppliers. A supplier can ask about a product or a single field directly from the portal, and you can start a conversation the same way. All threads are collected in one inbox.

The inbox is found under **Settings > Data onboarding > Feedback**.

## How to find threads that need an answer

Threads are sorted into tabs:

* **Needs reply**: the supplier wrote last
* **Waiting on supplier**: your side wrote last
* **Resolved**: threads marked as resolved
* **All**: every thread

Use the search field or the **Supplier** filter to narrow the list. Click a thread to read it.

## How to reply

Write your answer under **Reply** and click **Reply**.

* Type **@** to mention a colleague or one of the supplier's users. They are notified.
* Click **Attach** or paste a screenshot to add images (PNG, JPEG, GIF or WebP, up to 10 MB each).

When the question is answered, click **Mark resolved**. Click **Reopen** to continue a resolved thread.

## How to start a conversation with a supplier

1. Click **New comment**.
2. Choose the **Supplier**.
3. Optionally, choose the product, variant group or variant the comment is about, and the field.
4. Write your message and click **Create comment**.

The supplier's users are notified in the portal and by email.

## How to get notified

The people marked as **Responsible** on a supplier are notified when the supplier writes. You are also notified when someone mentions you.

To choose how you are notified, open your user settings, go to **Notifications**, and find **Supplier feedback**. You can choose between the notification center only, the notification center and email, or the notification center and a digest.


---

# 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.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-use-the-supplier-feedback-inbox.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.
