How do you structure tags and categories for better organization?

I haven’t had the opportunity to scale tags yet, however I can provide some general insights related to past experience being administrator in a CRM platform. 

1. Structure: This is something that you have to assess based on use case.  There are going to be cases where simple tags will provide value.  Other times the use case will require detailed tagging to gather valuable information to help drive business decisions. Always make sure you understand what the end goal is for the use case and what metrics are users wanting. The answers to those questions will help you determine the tagging structure that works. 
2. Tag Creation: My recommendation for this type of scenario is the less people who can create company and workspace level tags the better off the platform will be in the long run. This won’t prevent individuals from creating personal tags. They may even be able to provide recommendations based on the insights they gather from those personal tags. 
3. Best Practice:  Consistently review tag utilization and determine if they continue to be useful. If you notice that tags are limited in usage, ask questions to determine why and if the tag is still needed. 

I hope this helps get you started with the discussion internally regarding tags.

I have found that nesting tags has been very helpful! for example:

 - Urgency

------- High

------- Medium

------- Low

I do like to limit who can create tags, otherwise it becomes a mess and hard to have structure. We use tags heavily to trigger rules so having them organized is a high priority.

Hello,

Tagging message threads is highly critical, especially with the use of our shared inbox. The methods we use to organize our tags is to keep the creation and labeling at an efficient minimum. Our inbox reflects an ongoing process of moving clients through an organized structure.

We really only use about five tags for our process, which describe the current state of the task such as pass or deny tags, additionally the deny tag will have a branch set of options for reasons of denial. Then there would be a waiting tag and a few reason branch tags under the waiting status. Lastly, the few tags left include completion status or due date.

The best thought process you can set for yourself is not to overthink the process. A workflow doesn’t need to be like reinventing the wheel, but it should flow smoothly with structure. Front AI integrations can also help automate these workflow processes when you allow the tags to follow a rule structure. This can allow tasks to move to next steps, be put in a waiting period, or even automate follow-up messages.

Best,

Luke

We are beginning to use Front across a large team with diverse needs, consisting of 14 offices, each with a manager and an associate. Previously, we used Outlook and maintained hundreds of folders and subfolders within individual inboxes. During the migration to Front, these folders were imported as tags, resulting in approximately 300–400 tags within our shared workspace.

Our plan is to train the team on how to use and structure tags effectively. This training will include guidance on configuring tags so that they are visible only to the designated manager and associate for each correspondent assignment, nesting tags under individual assignments, and encouraging consistent and intentional usage across all offices. In addition, we plan to limit the ability to create new tags to the Company Administrator and Workspace Administrator roles to ensure clarity, consistency, and long-term sustainability.