> 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/the-ai-assistant-review.md).

# The Design Assistant

The Design Assistant generates the draft from your setup, and it checks each question as it generates it. You do not start the review. When the draft is ready, the header above the questionnaire shows the number of suggestions, for example **5 suggestions**.

Open the **Suggestions** tab (the light bulb icon on the right) to see them all. The suggestions also show as cards next to the questions in the draft.

![The Suggestions tab with design flags and LOI suggestions](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fc1puDyJLQ1wZS6STmyvn%2F21-suggestions.png?alt=media)

## Two kinds of suggestions

**Design flags** point to a problem in the design of a question, for example a grid that forces respondents to rate things that they do not use. Select **Flags** to see only these.

**LOI suggestions** show how to make the survey shorter. Each one shows the change and the time that it saves, for example **Saves about 15s**. Select **LOI** to see only these.

## Act on a suggestion

Each suggestion has these actions:

| Action          | What it does                                                           |
| --------------- | ---------------------------------------------------------------------- |
| **Add to chat** | Adds the suggestion to the queue above the chat box.                   |
| **Jump**        | Opens the question in the draft.                                       |
| **Dismiss**     | Removes the suggestion. Select **Undo** if you dismiss one by mistake. |

When the queue has the suggestions that you want, edit the instructions if necessary. Then select **Send**. The AI Assistant makes all the changes together.

{% hint style="info" %}
**Add to chat** does not change the questionnaire. The questionnaire changes only when you send the queue to the AI Assistant. Each change then shows in the **Tracked Changes** tab, where you can revert it.
{% endhint %}

## Ask the AI Assistant for changes

Type your request in the chat box, for example *"Add a Not sure option to Q1"*. The AI Assistant changes the questionnaire immediately. There is no approval step. If you do not want a change, select **Revert** on it in the **Tracked Changes** tab.

When you edit a question yourself, Metaforms adds **Review my changes** to the chat box. Send it to let the AI Assistant check your edit and update the suggestions.

Next, [learn about comments and tracked changes](/design-collaboration/comments-and-tracked-changes.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/the-ai-assistant-review.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.