MestraMestra
All posts

Comments and mentions in tasks: how to discuss work where it gets done

Management6 min read

Comments and mentions in tasks: why to discuss work inside the task and not in a messenger, how to mention colleagues properly, team rules and examples.

M
Mestra Team
Mestra — comments and colleague mentions inside a task

Comments in a task are a conversation inside the task, and mentions are a way to bring a specific colleague into the discussion so they get a notification and see the whole history. That keeps the discussion next to the work: the assignee, deadlines, files and decisions are all in one place.

Comments in a minute

What Why
Comment A clarification, a question, an interim result
Mention Call in a specific person
File in a comment A document next to the discussion
History You can see who wrote what, and when

Why discuss in the task and not in a messenger

In a messenger In the task
The message sinks in the feed The discussion is next to the work
A new participant doesn't see the context The whole history is in front of them
It's unclear where to find the decision The decision is recorded in the task
The conversation is lost when an employee leaves The history stays in the company
Files are scattered across chats Files are attached to the task

When to use mentions

  • You need an answer from a specific person. "@Olga, please confirm the 7% discount for the client."
  • You need approval. "@Igor, please check the estimate by Thursday."
  • You need to give a heads-up. "@warehouse, the client moved delivery to Monday."
  • Handing over work. "@Maria, I'm handing over this client, the whole history is above."

A mention without a question is noise. Every mention should say what exactly is needed from the person and by when.

Rules for the team

  1. Everything about the task goes in the task. Even if you discussed it by voice, the outcome is recorded in a comment.
  2. A specific question. "What do you think?" is worse than "Do you agree to a 7% discount? I need an answer by 3:00 PM."
  3. One mention, one action. The person called in understands what is needed from them.
  4. The outcome of the discussion. The last comment records the decision.
  5. Don't duplicate in a messenger. If it's urgent, a short "look at the task".

Examples

Real estate agency

@Anna, the buyer is asking for a 200,000 ₽ discount on the apartment on Tverskaya. The seller is ready for 150,000 ₽. Do we agree? We need to reply to the client by this evening.

Renovation company

@Sergey, at the Mira Street site the customer wants to move the sockets in the bedroom. Photo attached. How much will this add to the estimate and the timeline?

Sales team and accounting

@accounting, the client Vector LLC is asking for an invoice with a 14-day deferral. Is that OK?

Comments and micromanagement

Comments help you see the progress of work without constantly asking "how's it going?". If the assignee posts an interim result in the task, the manager doesn't need to pester them. More in the article on micromanagement.

How to move discussions from a messenger into tasks

The habit of writing to colleagues in private messages doesn't go away by itself. Simple steps help:

Step What to do
1 The manager starts discussing tasks only inside tasks
2 Reply to a private-message question with a link: "Write it in the task, we'll answer there"
3 Record the outcomes of meetings and calls in a comment
4 After two weeks, discuss what has become more convenient and what hasn't

It is important to leave room for quick, informal chat: that is what the shared team chat is for. More in the article on a corporate messenger.

Template for a good comment

  1. To whom: mention a specific person.
  2. What happened: briefly, with facts.
  3. What is needed: a decision, a check, a file.
  4. By when: a date or time.

Example:

@Dmitry, the client from Vector LLC sent edits to the contract (file below). We need to check the clause on payment deferral — by tomorrow 12:00 PM, so we can send back the signed version.

Common mistakes

  1. Discussing in three places. Part in the task, part in a messenger, part by voice.
  2. Mentioning everyone. People stop reacting to notifications.
  3. No final decision. A week later it's unclear what was agreed.
  4. Comments instead of tasks. A new assignment should be a separate task with a deadline.
  5. Long messages. The point gets lost — better short and in bullet points.

Mestra — task workflow with stages and comments

How it works in Mestra

  • Comments in the task. Discussion, files and decisions — inside the task.
  • Colleague mentions. A mentioned employee gets a notification and sees the whole history.
  • Activity history. Comments, status changes, assignee and deadline changes are visible in the timeline.
  • Internal team chat. For general questions not tied to a task.
  • Link to the client. The task is linked to the client and the conversation — the context is nearby.
  • Tasks from conversations. AI turns new agreements into tasks with deadlines on its own.

Frequently asked questions

Why comments in tasks if there is a messenger?

So the discussion stays next to the work: the assignee, deadlines, files and decisions in one place, with the history kept in the company.

What is a mention in a task?

Tagging a colleague (@name) in a comment: they get a notification and see what is needed from them.

How do I get the team to discuss tasks in the tasks?

Agree on the rule "everything about the task goes in the task", record the outcomes of voice discussions in a comment and don't duplicate questions in a messenger.

How many people should I mention in a comment?

Only those from whom you need an action or whom you need to warn.

What should I do if a new assignment appears in the comments?

Turn it into a separate task with an assignee and a deadline.

Summary

Comments and mentions move the discussion to where the work is done. Decisions don't get lost, new participants see the context right away, and the manager doesn't have to keep asking how things are going.

In Mestra, comments, mentions, files and activity history are inside the task, next to the client and the conversation. Try Mestra free for 15 days at mestra.chat.

Keep reading

Sign up for a demo and see it in action

Niche analysis with ready scenarios and fields

Sign up for a demonstration

Leave your contacts and we will schedule a short demo.

We use cookies

Cookies keep Mestra running, remember your preferences and help us understand how the site is used. See our Privacy Policy, Terms of Service and Consent Form.