> For the complete documentation index, see [llms.txt](https://docs.fullwhere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullwhere.com/documentation/documentation-en/inbox/internal-notes.md).

# Internal notes

Collaborate within your Fullwhere space thanks to internal notes

Internal notes are the private collaboration space on each customer interaction. From the customer interaction page, this space is accessible in the "Internal notes" section of the navigation bar.

{% hint style="info" %}
Your customers never see internal notes.
{% endhint %}

### Add a note or mention

1. Open an interaction in the Inbox
2. Open the tab **Internal notes**
3. Write your message
4. Type `@`, then search for and select a colleague or a [Teams](https://docs.fullwhere.com/documentation/documentation-en/get-started/teams.md) to mention
5. Click on <i class="fa-paperclip">:paperclip:</i> to add attachments to your message
6. Send the note

A Fullwhere user receives an email notification when they are mentioned or when another user replies to them.

### Find your mentions

Interactions where you are mentioned appear in the view [Mentions](https://docs.fullwhere.com/documentation/documentation-en/inbox/navigate-in-the-inbox.md).

There you can find the interactions where a colleague mentioned you or replied to you.


---

# 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.fullwhere.com/documentation/documentation-en/inbox/internal-notes.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.
