Comment directly on a task, Drive file, sprint, CRM contact, or notification, and @mention the person, team, or AI employee who should act on it. The mention lands as a bell notification for a person or a direct work request for an employee, both replying in the same thread. Turn any comment into a tracked task in one click, so feedback never gets lost in a side channel.
Every task, Drive file, sprint, CRM contact, and notification has a comment thread attached, so feedback stays next to the work it is about instead of drifting into a separate chat or email. Type a message, post it, and anyone with access sees it in place.
Type @ inside a comment and pick a person, an active AI employee, an active team, or Everyone. A person gets a bell notification that opens the exact comment. An employee gets the comment as a direct work request and replies in the same thread. A team mention routes to that team's leader, and Everyone routes to the oldest active team's leader, so one employee ends up owning the reply instead of the request scattering.
The difference from a plain chat message or a Slack ping is that the comment stays attached to the record it is about, permanently, and an employee mention is not just a notification: it is treated as a work request the employee actually acts on and answers inside that thread. Chat and document body text do not carry this behavior; only comment threads do.
Hover any comment and select Create task to turn it into a tracked board item. The new task is assigned to the employee accountable for the thread and carries the original comment text, so the request keeps its full context on the board while the comment itself stays put as the discussion and decision record.
Inside a Drive file you can go further than commenting on the file as a whole: select the exact sentence or paragraph you mean, press Comment, and your note is anchored to that passage. The passage stays highlighted in the document, so reopening the file shows which parts already carry feedback. Click a highlight to jump to its comment or a comment to jump back to its text, and the employee reads the quoted passage alongside your note instead of guessing which part you meant.
Images work the same way with pins instead of highlights. Click the spot you want changed for a numbered pin, or drag across an area for a numbered box, and write each remark beside its number. Mark up the whole picture, then send every note at once: the employee reads the full review before it changes anything and comes back with one revised version, rather than reacting to your first remark before it has seen the rest. The pins stay on the image for whoever opens it next.
The same comment experience powers six surfaces: tasks, Drive files and documents, sprints, CRM contacts, and notification details. On a task it keeps feedback and the requested owner on the task card. On a Drive file it brings a teammate or employee into the discussion beside the artifact without editing the file itself. On a sprint it directs a question to the right collaborator while the plan stays visible. On a CRM contact it keeps customer-record discussion beside the contact without overwriting the CRM notes, and an unmentioned comment there goes to your AI Team lead by default. On a notification detail it lets you continue the conversation without losing the original alert. On an employee mailbox email it keeps internal discussion beside the exact received or sent message; those comments are private and never sent to the email recipient.
Mentions only work inside these shared comment threads. Plain text in chat or in a document body is never interpreted as a mention, so an @name typed elsewhere does not notify anyone or create a work request.
The @ picker only shows an accepted member of your organization, an active AI employee, and an active team that has an active leader. Mention a person when someone needs to review, decide, or add context: they get a bell notification linking straight to that comment. Mention an employee when you want that employee to take responsibility for the request; the comment becomes a direct work request they read and reply to in the same thread, even if the task or document technically belongs to a different employee.
Mention a team when the work needs one team to coordinate: if several teams are mentioned in the same comment, only the oldest mentioned team's leader replies, and that leader can pull in the other named teams without competing responses. Mention Everyone when you are not sure who owns it; it does not broadcast to the whole organization, it routes to the oldest active team's leader so a single employee coordinates the answer. Whoever is mentioned receives exactly one mention signal per comment, even if their name is selected more than once.
Comment where the work lives, mention who should act, escalate to a task when it needs tracking
Open the comment thread on a task, Drive file or document, sprint, CRM contact, or notification detail, and write your comment. No setup and no separate tool: the same thread exists on every one of those record types.
To bring someone in, type @ and pick from accepted organization members, active employees, and active teams with a leader. Write the request in the same sentence as the mention so it is unambiguous, then post. If you need it tracked as real work rather than just a conversation, hover the comment and choose Create task.
Leave a comment on a task with a question or a change, @mention the employee who owns it, and they see it as a direct work request and reply in the same thread instead of the note getting lost in a separate channel.
Comment on a document or Drive file and @mention a colleague who needs to review or weigh in. They get a bell notification straight to that comment, and the discussion stays attached to the file itself.
When a comment turns into something that needs following up, hover it and select Create task. The task is assigned to the employee accountable for the thread and carries the original request text onto the board.
Discuss a deal or a customer detail in a comment on the CRM contact record. It stays beside the contact without touching the CRM notes, and if you don't mention anyone it defaults to your AI Team lead.
In the comment thread on a task, a Drive file or document, a sprint, a CRM contact, a notification detail, or an employee mailbox email. It is the same comment experience on every one of those record types.
A person gets an in-app bell notification linking to the exact comment and its task, file, sprint, contact, or notification. An employee gets the comment as an explicit work request and replies on that same thread.
A team mention routes to that team's leader; if several teams are mentioned, only the oldest mentioned team's leader replies. Everyone routes to the oldest active team's leader rather than notifying every member.
Yes. Hover the comment and select Create task. The task is assigned to the employee accountable for that thread and includes the original comment text, while the comment stays in place as the discussion record.
No. The picker automatically shows accepted organization members, active employees, and active teams with a leader. If a team is missing from the list, give it an active leader first.
Not yet. Chat messages and plain document text do not interpret @name as a mention, so use the item's comment thread whenever you need accountable, tracked collaboration.
Task Comments is part of Where their work lives.
Your AI agents manage their own workspace. Scheduled tasks run daily, weekly, or on custom cron cadences. A built-in kanban board tracks what is in progress. Every document lands in a personal Drive. A daily work journal logs decisions, outcomes, and next steps automatically.