> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Internal comments and mentions

> Leave internal comments on sessions and messages, @mention teammates or teams, and follow up from the notification center. Customers never see them.

Internal comments let your team talk about a session inside the session itself: flag something for a colleague, ask a team for help, or note what you checked. Customers never see them, and an @mention sends the person or team a notification.

> [!NOTE]
>
> Comments live in every session in your [OpenCX inbox](https://platform.open.cx/inbox). Writing, editing or deleting a comment requires write access to that session: **Inbox** write, or **Team sessions** / **Assigned sessions** write for sessions in your scope (see [Limit a role to its assigned sessions](https://docs.open.cx/inbox/intro.md#limit-a-role-to-its-assigned-sessions)).

## Add a comment to the session

**1. Turn on As comment**

In the composer, turn on the **As comment** switch beside **Send**. The composer switches to a dashed, highlighted note style.

**2. Write the comment**

Type your note, mention people with **@**, and attach files if needed.

**3. Send it**

Select **Send**, or press **⌘ + Enter** on Mac or **Ctrl + Enter** on Windows and Linux.

The comment appears in the timeline as an internal comment, and the session card shows it with an **Internal note:** prefix. Your unsent reply and unsent comment are kept separately: a dot beside **As comment** means the other mode still holds a draft. Opening another session switches the composer back to a reply.

## Comment on a specific message

Hover a message in the timeline and select the comment icon (**Add comment**). A thread opens under the message with an **Add a comment...** box. Type your comment and select the arrow, or press **⌘ + Enter** / **Ctrl + Enter**.

Once a message has comments, the icon shows the commenters' avatars and the number of comments. Select it to open or close the thread. Threads are one level deep: you comment on a message, or on a top-level comment, but not on a comment inside a thread.

## Mention teammates and teams

Type **@** in a thread comment, or in the composer while **As comment** is on, then pick from the list:

| Section | What the mention does |
| - | - |
| **Agents** | Sends that teammate a **Personal** notification: "mentioned you in a comment" |
| **Teams** | Sends every member of the team a **Team** notification: "mentioned \[team] in a comment". You are left out if you belong to the team you mention |
| **AI Instructions**, **Actions**, **Workflows** | Inserts a link to that item; selecting the chip opens it in a new tab. Nobody is notified |

Someone mentioned both directly and through a team gets one notification, not two. Mentions can also start workflows that use the **Agent Mentioned** trigger.

> [!WARNING]
>
> Mentions are internal. If you insert one and then turn **As comment** off, the composer warns you: the mention would reach the customer as plain "@Name" text.

### Who is notified about thread replies

When someone comments in a thread, people who commented in that thread earlier, including whoever started it with a comment, get a notification: "added comment to thread". You are not notified about your own thread replies, and anyone mentioned in the new comment gets the mention notification instead.

## Edit, delete or hide comments

* **Edit or delete**: hover your own comment and select the pencil or trash icon. Only the author can do this. An edited comment shows **(edited …)**; a deleted one stays in place as **\[deleted]**. Editing does not send new notifications.
* **Hide one comment**: open a top-level comment's message menu and select **Hide comment**. It collapses to **Internal comment hidden**, which you can expand again.
* **Hide all comments**: in the session's **⋯** menu, open **View options** and turn off **Show comments**. While it is off, the composer warns that a new comment won't appear in your view until you turn it back on.

Hiding only changes your own view in this browser. Teammates still see every comment.

## What customers and the AI see

* **Customers** never see internal comments or mentions, on any channel. Comments are left out of [PDF exports](https://docs.open.cx/inbox/intro.md#export-a-session-as-pdf) and of the history a new primary contact receives when you change an email session's recipient.
* **The AI** does not read internal comments. The exception is your reply in the thread of an AI help request, which is how you answer it (see [Answer an AI help request](https://docs.open.cx/inbox/intro.md#answer-an-ai-help-request)).
* **Connected helpdesks**: with Zendesk, Intercom, Jira Service Management or Genesys Cloud as your ticketing system, a new top-level comment is also added to the linked record as an internal, agent-only note. Thread replies, edits and deletions are not copied.

Comments are separate from [Session notes](https://docs.open.cx/inbox/intro.md#session-notes), the shared to-do pad in the session sidebar.

## Use the notification center

Select **Notifications** in the sidebar, or press **⌘ + .** on Mac or **Ctrl + .** on Windows and Linux. A red dot and a counter (up to 99) show unread notifications.

Use the selector at the top to switch between:

* **Personal**: your mentions and updates.
* **Team**: mentions of teams you belong to.

Each entry names who acted, what happened and, for sessions, the session number and channel, with a short preview. Select an entry to mark it read and open it: for a comment, the session opens scrolled to that comment, which is briefly highlighted. Use the up and down arrow keys, **Home** and **End** to move through the list. **Clear all** empties the current tab; see [Clear notifications](https://docs.open.cx/inbox/intro.md#clear-notifications).

### Notification types

| Notification | You get it when | Tab |
| - | - | - |
| **\[name] mentioned you in a comment** | Someone mentions you in a session comment or an AI instruction comment | Personal |
| **\[name] mentioned \[team] in a comment** | Someone mentions a team you belong to | Team |
| **\[name] added comment to thread** | Someone comments in a session or AI instruction thread you commented in | Personal |
| **Customer replied** | A customer replies to a session assigned to you. Each session keeps one entry, which moves to the top and becomes unread again with each new reply | Personal |
| **Your session export finished** | A session export you started is done | Personal |
| **Your export is ready to download** | A Customer Insights export is ready | Personal |
| **Your deep research report is ready** | A deep research report completes | Personal |
| **\[name] mentioned you in an insight discussion** / **replied in an insight discussion** | Activity in a Customer Insights discussion | Personal |
| **\[name] assigned an insight to your team** | A Customer Insights insight is assigned to your team | Personal |

Customer reply notifications go only to a human assignee, never while the AI owns the session, and an admin can turn them off for the workspace. Desktop pop-ups and sounds are set separately; see [Notification settings](https://docs.open.cx/ticketing/notifications.md).

***

## Related Documentation

> [card] [Notification settings](https://docs.open.cx/ticketing/notifications.md)
>
> Desktop pop-ups and sounds

> [card] [Inbox](https://docs.open.cx/inbox/intro.md)
>
> AI help requests and session notes

> [card] [Keyboard shortcuts](https://docs.open.cx/inbox/keyboard-shortcuts.md)
>
> ⌘. and other shortcuts

> [card] [Teams](https://docs.open.cx/teams.md)
>
> Who a team mention reaches


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.