> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/care/communication/inbox/inbox-mentions.md). # @Mentions @Mentions allow users to tag a specific colleague within an Inbox conversation, directing their attention to a message or thread. Mentions are currently available within [Internal Notes](/care/communication/inbox/inbox-internal-notes.md). *** ## Mentioning a Colleague To mention a user, type **@** followed by their name in the Internal Note composer. An autocomplete list appears with matching users — select the person you want to tag and complete your message. If the mentioned user does not have access to that conversation, a warning is shown before sending so you can decide how to proceed. If the mentioned user's account has been deactivated, their name appears with a **\[Deactivated]** label wherever the mention is displayed. This applies both at the point of tagging and in the conversation history, ensuring mentions remain traceable even when team members leave. *** ## The Mentions Tab A dedicated **Mentions** tab in the Inbox aggregates all conversations where you have been tagged. This gives you a single place to review and act on every mention directed at you, without having to search through individual conversations. The tab shows a counter of **new mentions** — the number updates in real time as new mentions arrive or existing ones are marked as read. *** ## Mention Status Each mention has a status of **New** or **Read**: * **New** — the mention has not yet been viewed * **Read** — the mention has been seen Read mentions are visually distinct from new ones, making it easy to separate what still needs attention from what has already been seen. *** ## Notifications Mention events can trigger automations in Designer, allowing you to send a notification to the mentioned user via the following action types: * Notification * Email User * SMS User * Task * Webhook For the Notification action type, the body field is not shown — the notification automatically includes the relevant portion of the message content. To configure mention notifications, add a new automation using the **Mentions** event group in Designer. *** ## Related Topics * [Inbox](/care/communication/inbox.md) — Inbox overview and general usage * [Inbox: Internal Notes](/care/communication/inbox/inbox-internal-notes.md) — composing internal team messages * [Automated Notifications](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/designer/automated-notifications.md) — setting up automation-based notifications --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.welkinhealth.com/care/communication/inbox/inbox-mentions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.