Here's How to Stay in the Loop with @Followers! 🔔

We use a mix of @ mentions! 

• Individual @[user] when we need to mention something to one specific person regardless if they are an assignee or not (i.e. @mentioning the assignee of the task for a status update or someone who's outside of the task but who has insight on how to get something done)
• @[job role] when we need to run something by a designated group of people (i.e. @mentioning a committee job role for approval/support on a task)
• @assignees when we want to call out to all assignees on the task (i.e. @mentioning all assignees to let them know they can get started on their task)
• @followers when we need to inform people who are following a task or project regardless if they are assigned to it/expected to take action (i.e. @mentioning all followers to let them know as stakeholders that the work has been done or an issue has been resolved)

For @followers in specific, we'll follow tasks that perhaps impact a larger project we are working on. We like the fact that we can keep an eye on things this way instead of needing to assign ourselves to the task, especially in cases where we just need oversight on work and not actually part of the delivery workflow.

@mentions are one of the core functions of the Wrike. I can't imagine functioning without this feature.
The problem comes when you mention user group and no one responds 🙂

We have a few automations set up to send notifications out using the @followers feature. The teams that use this feature love it! I am working to spread the word across our organization!

@mentions are awesome, when you need feedback on something specific you can tag them so they know exactly what you're looking for information or feedback on

I've not been using @followers in task comments, but it's good to know it notifies even former task assignees.

One of our last steps in closing a task being implemented from a product backlog is to communicate its completion to the requester and other key stakeholders (at least). This is one way to do that without switching contexts - and so they can review the entire context of what got it to delivery. (Since we maintain product channels in Microsoft Teams, I post there for visibility to all stakeholders, most of whom don't use Wrike. But I link to that post from that step in the task description, or in a comment.)

I often use the @followers on tasks where I know there are more collaborators than just those assigned to the task. This helps everyone stay more informed. 

In my project portfolio, I use Wrike's @followers feature to follow projects within the project programs I oversee.  This helps me stay informed in real-time of project updates.

I have a weekly call will dedicated project managers on my team to discuss the freshest updates around ongoing projects. We discuss roadblocks, wins, and tasks statuses. All updates are captured and shared at the project level using the @followers tag to alert all stakeholders.

I also haven't been using @followers, but that is such a helpful feature. I use @mention a lot when working on tasks and wanting to get status updates from someone on my team. 

I use all mentions type but @followers when I need to update a lot of people in a single action

@assignees is extremely helpful to get everyone looped in on the task. If you have a group of people assigned to a task, all will be notified if @assignees is used. Very helpful.

@mentions are essential. Nobody will see if you change the text of a task. So important notes have to be submitted to the attention of colleagues by @mentions. I always explain the @mentions as replecement of mails. 

So if you change something on a task somebody must know: @mention is a must. Normaly we use a person directly or the followers.

Our team will use @followers on tasks where there are more stakeholders than those who are working on the task and need to be notified about a major change, question, or update. 

@mentions are integral to our automations to remind assignees and followers about task timelines. It's also helpful to keep followers up to date on status of a particular project without having to send emails or hope they saw a dashboard.

• @assignees when we want to call out to all assignees on the task (i.e. @mentioning all assignees to let them know they can get started on their task) It helps to ensure the team stays on track and I use it to clarify work tasks. 

@group - for project teams

@assignees - if more than one assignee

We use automated @mentions to remind our users of commonly missed steps as well as to notify key stakeholders at specific points in the project life-span. This way nothing gets missed!

We use a variety of @mentions! 

We use

• @[Group Name] to alert a team
•  @[User] to get ahold of someone specific
• @[author] is a favorite of ours to alert the requestor when their request has been completed
• @[followers] gets some use within our department, but not as much since we use projects mainly and you have to specifically choose to follow projects. 
• @[assignees] gets used to alert when we have someone going into a specific report type so others don't also go in to running that report until the other is out. Very helpful!

We use @mention anytime we want someone to see something or reply to something.We typically have several assignees to each task, so we use @assignees for any updated to the task so everyone sees them.

We us automations to @mention @assignees. We also encourage our teams to @mention an individual(s) to help ensure we keep a conversation of progress and understanding.

We use the @ Mentions to communicate within tasks, but also for automated Messaging.
e.g Approval Process.

@Florian the document is ready to be verified.. etc.

Use automations available in Wrike to generate custom emails from a user mailbox whereas standard Wrike @ notifications may be ignored as spam

All this being said, the little Wrike warning that pops up when I forget to @mention someone in a comment, making sure it is intentional has saved me a time or two 🙈

The use of @mentions is one of the number one "best practices" that I tell individuals to use when joining the Wrike platform. 

A valueable tip is: you can fine tune the email notifications you receive from Wrike, you can keep the notifications for when someone mentions you and turn off others, for example. Just go to your profile and adjust to your needs.

We use the @ Feature all day. Groups that are assigned to a project on the changes.  I prefer everyone uses the @ Feature so nothing gets missed and its in my feed. 

We haven't adopted @mentions much. Right now, we just copy the URL to Teams and keep our convos in a single platform. Some great advice here to spread adoption, though!

@mentions are critical to success - we always tell our people to double down with an @mention - even if you change status, upload a file or do anything in a task - make sure to let people know - without it people may miss it!  If it is related to a task, then you must master communication within the task!  Not everything belongs in the task.  Natural conversations and discussions can be live, MS Teams etc - but take notes in the task - then @mention the team to refer as needed.

ALSO automations and @mentions are best friends!!  Gentle reminders when something is off-process helps your team stay on the same page and adhering to their process better!

@mentions are essential to our work.  We like the Wrike project to be the single source of truth so anyone can pick it up and know what's been happening.  We mainly use @mention for individual users and @mention groups for whole teams.  We have also set up some automations to @mention to trigger actions and remind team members of certain things.

We mainly use @mentions because each task is typically assigned to one person. I do like the idea of this for our Issues task as they are picked up by next available person.