Can you tag a whole team in a Front comment?
No, not as one mention. Front's internal comments only support tagging individual teammates or @all, which notifies everyone with access to the shared inbox, not a specific group inside it. If you want something narrower than "everyone" and broader than "one person," Front's own staff point to a workaround rather than a built-in feature: build a custom @mention shortcut through Front's Rules, so that typing something like @cx in a comment notifies a defined list of teammates.
That answer comes straight from Front's staff on its own community forum, replying to a customer asking this exact question. It's a real fix, and teams use it. It's also not the feature people are asking for, which is why the underlying request, tagging a team by name in one mention, is still sitting open in Front's own product portal: 76 votes, status Backlog, since folded into a broader idea. It hasn't shipped, and there's no roadmap commitment that it will.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionWhat @all notifies
@all in a Front comment is a blunt instrument by design. It pings every teammate with access to that shared inbox, which in a support or sales inbox can easily be ten or twenty people who have nothing to do with the specific request. It works as a "someone please look at this" signal, but it trades precision for reach. Use it for urgent, all-hands situations, not as your default way to loop in "the right two or three people." Ping people repeatedly for requests that aren't theirs and some of them stop reading the pings at all, which is exactly backward when you need @all to land.
The custom shortcut, and its limits
The narrower option is a rule-based shortcut. You define @cx (or whatever string you pick) to fan out to a fixed list of teammates whenever someone types it in a comment. Front's staff describe this as gated to a paid plan tier above the base one. Front's plan names have shifted since that forum answer was posted, so check what your current tier unlocks rather than assuming a specific name still applies, but the mechanism itself is current. It's a rule, not a native mention, and it has a rule's limitations.
The one that matters most is that the list behind @cx is whoever you put there when you built the rule. It doesn't know your team's roster changed. Someone joins the design team in March, and every @design comment from January through March missed them, because the rule was never re-edited to add them. Someone goes on leave, and the shortcut still notifies them along with everyone else, so the "who's available right now" judgment is still sitting on a human, exactly like it was before the shortcut existed.
What that gap actually costs
Play it forward and the cost isn't abstract. A branding agency's @design shortcut still points at the three people who existed when someone built it. The team hires a fourth designer, nobody updates the rule because updating a mention list isn't on anyone's onboarding checklist, and a client's rush request for a transparent-background logo lands on @design while one of the three original names is out on leave. The other two assume the leave coverage already has it. Nothing in Front marks the comment as stale, because by Front's own bookkeeping it was handled: it existed, and someone was notified. The request just sits until the client's own follow-up, days later, forces someone to go look, at which point the fix is a five-minute file export and an apology for a gap nobody could see from inside the inbox.
Both workarounds share that same root limit. They depend on a human choosing the right target at the moment they write the comment, and on someone else keeping that target's membership current as the team changes. That holds up fine for a small, stable team handling a modest comment volume. It stops holding up once any of three things happen: the team roster changes often enough that shortcut lists go stale, the volume of requests is high enough that a missed mention isn't rare, or the actual problem isn't "who do I tag" so much as "did this get tracked anywhere durable, independent of who happened to read the comment."
At that point the fix isn't a better mention, it's routing that doesn't depend on a mention at all. That's the part we build. Modem connects to a Front-fed email pipeline and reads what a message is asking for, then clusters it into a topic based on that content and links it to a matching tracker issue when one already exists, not on which teammate someone remembered to type into a comment. Filing a brand-new issue still takes an agent request or a configured automation, not just the message arriving. A request about a transparent logo file lands wherever "creative asset requests" already live, whether the account manager thought to tag @design, tagged the wrong person, or tagged nobody at all because it was a slow Friday and they meant to circle back. When the person on leave returns, there's no backlog of missed mentions to dig through, because the request was never sitting on a person's attention as its only record. Modem is what we sell, not a neutral recommendation, so read that comparison with a skeptical eye: the two Front-native options above cost nothing extra and are the right call for a team small enough that everyone still knows who's out this week.
For the day-to-day version of getting requests out of a Front inbox at all, see the best tools to turn Front emails into feature requests, and for backlog you already have sitting untagged in old conversations, how to apply tags retroactively to old support emails in Front covers the search-and-mass-action route.
Audit the shortcuts you already have
If you're not ready to change anything structural, start by auditing whatever custom mention shortcuts already exist in your Front rules and confirming the list behind each one still matches your current team. That alone would have caught the missing-designer gap above before a client had to notice it, not after. Put a recurring reminder on it tied to your next new hire, not a calendar date, since roster changes are what break these lists.
