Front Tags Explained (and How to Use Them Well)

What a tag actually does in Front

Front's own documentation is blunt about the job a tag does, and it's worth internalising because it explains every design decision that follows. Per Front's Understanding tags help article, a tag lets you track certain topics in your inboxes, set up rules to sort messages automatically, report on trends in analytics, and use as private folders to file your messages into.

That's four distinct jobs from one primitive. The same billing tag can surface every payment question across three shared inboxes, trigger a rule that routes those conversations to the finance team, appear as a row in your analytics with volume and response-time metrics, and — if it's private — act as a personal folder only you can see. Because Front is a shared-inbox platform rather than a ticketing system, tags do a lot of the categorisation work that "ticket fields" or "ticket types" would do elsewhere, but they stay lightweight and stackable: a single conversation can carry as many tags as it needs.

Shared, private, and company tags — the scope that decides everything

The single most important thing to get right is a tag's scope, because scope decides who sees it and who can manage it. Front has three levels.

• Private tags are personal to each teammate. They show with a lock icon in your tag list, and — critically — your teammates cannot see them even when you apply one to a shared conversation. These are your personal folders.
• Shared tags are available to everyone in your workspace and are visible on any conversation a teammate has access to. These are the tags your reporting and routing should be built on. They're managed by admins or teammates with workspace permissions.
• Company tags are available across all workspaces in your company and are managed by company admins only. Per Front's docs, company tags are an Enterprise-plan feature.

There's a subtlety worth flagging for anyone connecting email accounts: the scope often gets decided for you at connection time. As Front notes, if you connect an account as a personal channel the tags will be private, and if you connect it as a shared channel the tags will be shared with your team. So the "why can't my colleague see this tag?" question usually traces back to how the channel was connected, not to the tag itself.

How to create and apply a tag

There are two entry points, and both are documented in Front's Understanding tags guide.

1. From a conversation. Open the conversation, click the (+) plus icon at the top, choose the tag option, and either pick an existing tag or select Create new tag. The tag is applied immediately.
2. From Settings. Go to Settings → Tags, click Create tag, and name it. This is the place to manage the full library — rename, nest, delete, and set scope.

Front supports nested tags, so you can group related labels under a parent (think a Billing parent with Refunds, Invoices, and Chargebacks beneath it). The limits are generous: up to 5,000 tags can be nested under a single parent, and you can display up to 500 tags in your sidebar. In practice you want far fewer than that — a tight, curated set beats a sprawling one every time.

Auto-tagging with rules

Applying tags by hand is fine for a handful of conversations, but it doesn't scale and it doesn't stay consistent. The fix is to let rules do the tagging. Rules are Front's automation engine — a linear WHEN → IF → THEN flow — and adding a tag is one of the most common THEN actions. We go deep on the mechanics in Front rules explained, but the tagging pattern is simple.

Under Settings → Rules and macros → Create rule, a classic auto-tag rule looks like:

• WHEN an inbound message is received
• IF the conversation is in the Support inbox AND the subject or body contains "refund", "invoice", or "charge"
• THEN add the tag billing

Now every payment question tags itself the moment it lands, which means your routing and your reporting both get consistent data without anyone remembering to click. You can stack conditions with AND/OR logic, match on sender domain, channel, or account, and combine tagging with other actions like assigning a team or moving the conversation. This keyword approach is exactly where auto-tagging starts to show its limits — more on that below.

Tag-based routing and analytics

Once tags are applied consistently, two things get much easier.

Routing. Because a rule can both read tags (IF conversation has tag X) and set them, tags become a routing signal. A common two-step pattern: one rule tags inbound conversations by topic, and a second rule routes anything tagged billing to the finance shared inbox and anything tagged urgent to a priority queue. That separation keeps your logic readable — tagging rules describe what a conversation is about, routing rules describe where it should go. If you're still setting up the underlying inboxes, our guide to the Front shared inbox covers how those queues are structured.

Analytics. Tags are the backbone of topic-level reporting. Front's Tags report breaks down volume and performance per tag over a selected period, so you can answer questions like "is billing volume growing?" or "which topic has the slowest first-reply time?" Per Front's documentation, the Tags report analytics sit on the Professional plan or above, so if you're on a lower tier, plan to use tags for organisation and rules now and layer reporting on later.

The "tags lost on move" gotcha

Here's the behaviour that surprises almost everyone, and it's not a bug — it's how private-tag filing is designed. Per Front's Using tags to label and file conversations guide, when you drag a conversation from your Inbox into a private tag, Front removes the Inbox tag and adds the private tag. Tags are automatically added or removed as you drag a conversation between tags.

The upside is that private tags work exactly like folders: filing a thread into Follow-up pulls it out of your main Inbox view, and dragging it back re-adds the Inbox tag. The trap is assuming a drag adds a tag without removing another — it can do both. If you rely on the Inbox tag to represent "still needs attention", filing a conversation away will quietly clear that signal. The clean mental model: private tags are moves, shared tags are labels. Dragging into a private tag is a filing action that swaps tags; applying a shared tag from the (+) menu is additive and leaves everything else in place. Once you internalise that distinction, the surprise disappears.

The honest limits — and where an AI layer picks up

Front's tagging system is genuinely well-built for what it is: fast to apply, cheap to stack, scriptable through rules, and wired straight into analytics. For a lot of teams it's all the categorisation they need. But it's worth being clear-eyed about where it runs out of road.

Rules tag on keywords, not meaning. A rule that watches for "refund" will miss "I want my money back" and will mis-tag "no refunds on this one, but here's a discount." Keyword matching is brittle in exactly the way natural language is messy.

Native AI tagging exists, but with guardrails. Front does offer AI Tagging, where an admin picks up to 50 tags per inbox and Front uses the message subject and body to apply them, with automatic tagging switching on after you approve 10 sample emails. It's a real upgrade over keyword rules — but it's scoped to tagging alone. It categorises the conversation; it doesn't act on it.

Required tagging is plan-gated. If you want to force teammates to tag before archiving — the thing that keeps your analytics honest — Front's Required tagging is available on the Professional plan or above, and even then it's not retroactive, doesn't apply on the mobile app, and is bypassed by the "Send & archive" button. Good to know before you build a reporting strategy on the assumption that every conversation is tagged.

This is the seam where an AI agent layer fits, and it's worth understanding the broader category of AI agents for customer service before you reach for one. Macha is one such layer, and it runs on top of the Front you already use through a live native connector — it does not replace Front or its tagging. Once connected to Front, a Macha agent reads the full conversation and classifies by intent rather than keyword, so billing gets applied to "I want my money back" and withheld from "no refunds this time." Because it's an agent and not just a classifier, the same pass that tags the conversation can draft or send a grounded reply, look up an order or invoice through a custom tool that turns a REST API into something the agent can call, and route based on what it actually understood. Credits are consumed per AI action, not per resolution — the pricing page breaks that down.

The clean division of labour: keep Front's tags as the shared vocabulary your routing and analytics are built on, and layer an agent on top for the part keyword rules can't do — reading a message the way a human would and tagging (and answering) accordingly.

FAQ

How do I create a tag in Front? Two ways. From a conversation, click the (+) plus icon at the top, choose the tag option, and select Create new tag. Or go to Settings → Tags and click Create tag, which is also where you manage, rename, nest, and set the scope of every tag.

What's the difference between a private tag and a shared tag? A private tag is personal — it shows with a lock icon and your teammates can't see it, even on a shared conversation, so it works like a private folder. A shared tag is visible to everyone in your workspace on any conversation they can access, which is why routing and analytics should be built on shared tags.

Why did my Inbox tag disappear when I filed a conversation? That's expected. When you drag a conversation from your Inbox into a private tag, Front removes the Inbox tag and adds the private tag — private-tag filing is a move, not an add. Drag it back to the Inbox to re-add the Inbox tag.

Can Front tag conversations automatically? Yes, in two ways. You can build a rule (Settings → Rules and macros) that adds a tag when a message matches conditions like a keyword or sender, and Front also offers native AI Tagging where an admin picks up to 50 tags per inbox and Front applies them from the subject and body after you approve 10 sample emails.

Can I add AI tagging without replacing Front? Yes. An AI agent layer like Macha connects to Front as a native connector and runs on top of your existing inbox — it doesn't replace Front or its tags. It classifies conversations by intent rather than keyword, applies the right tag, and can draft or send the reply too, while Front stays the system of record for your inboxes and analytics.

Ready to tag by meaning instead of keywords — and answer while you're at it? Start a free trial of Macha and connect it to your Front inbox in minutes.