> 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/supplier-portal-guide/talking-to-your-customer.md).

# Talking to your customer

How to ask your customer questions, answer theirs, and choose your notifications

Questions and answers between you and your customer are kept in threads under **Feedback**. A thread can be about a single field, a product, or something general.

## Answering a question

When your customer writes to you, the bell in the top bar shows a notification, and the item is marked **Needs attention**.

1. Click the notification, or open **Feedback** in the menu.
2. Open the thread, write your answer, and click **Reply**.
3. When the question is settled, click **Mark resolved**.

Type **@** to mention a colleague, or someone from your customer who has written in the thread. To add an image, click the attach button or paste a screenshot (PNG, JPG, GIF or WebP, up to 10 MB).

## Asking a question

1. Open **Feedback** and click **New comment**. Or click **New comment** in the **Comments** panel of a product.
2. Choose the item the question is about, or leave it empty for a general question.
3. Write your message and click **Post comment**.

Your customer's contact person is notified.

## When your customer asks for changes

When your customer reviews your submitted changes and asks you to change a value, or does not accept it, their note arrives as a thread under **Feedback**. Correct the value on the item's page, save, and submit it again.

## Choosing your email notifications

Click your name in the top-right corner and choose **Notification settings**:

* **Instant** sends one email shortly after each new reply. This is the default.
* **Daily digest** sends one email a day summarising new replies, at the time you choose (in UTC).
* **Off** sends no emails. The bell in the portal still shows new replies.


---

# 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/supplier-portal-guide/talking-to-your-customer.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.
