> 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/review-collaboration/reconciling-client-feedback-pm.md).

# Reconciling client feedback

Everything a client comments on or edits is visible to you the moment they do it — in the Changes and Comments tabs of the Review page, with the approver's name shown on each approved change.

![A client comment arrives, the PM applies the change, replies, resolves the thread, and approves the change](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FTq31XypF06o09HlXUcZP%2Fpm-reconcile-feedback.gif?alt=media)

From there you'll typically do one of three things:

**Apply the change** and resolve the related comment.

**Reply** with a clarifying question.

**Reach out directly** if something needs more discussion.

{% hint style="info" %}
If an approve is refused with *"Still syncing — try again in a moment"*, the change is real and the request was fine; the document just hasn't been written out yet. Wait a moment and try again.
{% 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 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/review-collaboration/reconciling-client-feedback-pm.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.