> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/design-collaboration/reconciling-client-feedback.md).

# Reconciling client feedback

Each comment and edit from your client shows on the Design page immediately:

* **Client comments** show in the **Comments** tab and on the question. Each one shows the email address of the client and a globe icon, because your client can see the thread.
* **Client edits** show in the **Tracked Changes** tab with the email address of the client. Only clients with the **Edit** access level can edit.

![A team comment and a client comment in the Comments tab](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FpQBkEgYlXdKC3UctpPB2%2F24-comments-panel-v2.png?alt=media)

From there, you usually do one of these things:

**Make the change** yourself, or ask the AI Assistant to make it. Then resolve the comment.

**Reply** with a question. Your reply is in the same thread, so your client sees it.

**Revert a client edit** that you do not agree with. Select **Revert** on the edit in the **Tracked Changes** tab, then tell your client why.

**Speak to your client directly** if the topic needs more discussion.

{% hint style="info" %}
A comment from your client is always visible to your client. Do not reply in a client thread with information that is only for your team. Add a new **Internal** comment instead.
{% endhint %}

Next, [hand off the version to programming](/design-collaboration/versions-and-handing-off-to-programming.md).


---

# 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://help.metaforms.ai/design-collaboration/reconciling-client-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.