@mention teammates or @hamster from inside any thread or document — the right person gets the right notification, with the deep link to exactly the message that mentioned them.
Mentions let you address a specific teammate — or the AI agent — directly inside a Brief, document, or conversation by typing their name with the @ symbol. The person you mention is added to the thread, gets a deep-link notification, and can pick up the conversation in context. Notifications also surface other account-level updates so the team stays informed without manual check-ins.
The mention pipeline is built to be predictable. Type @h, then @ha, then @ham — Hamster stays at the top of the autocomplete the whole way through. Click a teammate, send the message, and you can trust three things: they're a participant on the thread, they have a notification, and the notification opens to the exact message they were mentioned in.

Trigger the mention picker — In a Brief, document, or chat, type @ followed by any part of a teammate's name or email. A picker appears with matching team members and the Hamster AI.
Pick the person (or @hamster) — Use arrow keys and Enter, or click directly. The mention is inserted as a styled tag in the content.
Send the message — The mention is submitted as a structured target alongside the message body, so the system knows exactly who you meant.
The mentioned person is added to the thread — Mentioned teammates are added as participants before notifications fire, so they have permission to read and reply when they click through.
A deep-link notification is sent — The recipient gets an in-app notification linked to the exact thread item that mentioned them. Real-time Delivery (if enabled for your workspace) pushes it instantly; otherwise it appears on their next page load. The notification keeps the surrounding conversation context, so they can read the thread and understand why they were mentioned before clicking through.
Sticky context handles follow-ups — Once you've mentioned someone in a thread, follow-up messages stay routed to them without re-mentioning. Switch threads to reset.
Read or dismiss — The recipient can mark a notification read (clears the unread badge but keeps it in the list) or dismiss it (removes it). Notifications expire automatically after about a month.
| Target | Behaviour |
|---|---|
@hamster |
The AI agent always responds when mentioned, even when you also mention people in the same message. Hamster sticks to the thread until a different mention replaces the context. |
@teammate |
Adds them as a participant, sends a deep-link notification, and routes follow-ups to them until a different mention replaces the context. |
Mixed (@hamster + @teammate) |
Hamster responds; teammates are added and notified. No more situations where the AI gets silently filtered out by other mentions in the same message. |
@h → @ham → @hamster) is consistent across every composer surface — chat, Brief editor, and document editor all use the same logic.| Type | When it appears |
|---|---|
| Info | Standard updates and mentions |
| Warning | Situations that may need attention (e.g. Brief quota approaching the limit) |
| Error | Actions that failed or require follow-up |
Notifications are delivered in-app by default. Real-time Delivery (instant push to open browser sessions) is a separate workspace configuration.
Notifications can be turned on or off at the workspace level:
Contact your workspace administrator to change these settings.
@hamster to assign the AI a question or Task inline — useful when you want to flag something for AI follow-up without leaving the document.