Skip to main content

We've been using FrontApp for some time and I've discovered that the tags and nested tags has gotten out of control.
Does any one have any sound advice for managing these as we want users to create and use tags but found reporting is way to granular with too many tags.
Cheers,

Hi there Eugene! 

Other users may chime in here and add their experience / thoughts, but I wanted to share a little insight from our team 😊

 

Similar to Message Templates and Rules, Tags are a resource that it’s easy to “let loose on” as you continue using Front. Things change, processes get updated and without continued up-keep, you can quickly lose control of the overall organisation. 

 

As such, much of the “suggestions” or “best practices” might seem a little more like common sense my main suggestions would be the following: 

  • Prioritise Tag nomenclature and hierarchy
    • Ensure that when you and your team are creating tags, you’re sticking to a standardised naming format, something like “Team / Department - Category - Subject” 
    • You can then use Nested tags to create a folder structure based on your main categories, be it your internal teams, or a tiered approach, depending on your team’s specific use case. 
  • Archive, don’t delete
    • You have the option to Archive tags, rather than deleting them when no longer needed. 
    • I would recommend this option in most cases, as tags will remain on previous conversations, and be accessible in Analytics if needed. 
    • You can also Restore archived tags if they come back into play again.
  • Regular upkeep
    • As much as is possible in our busy day-to-day, we try to set aside a few minutes every couple of weeks to do some general upkeep of your tags and organisation. 

We ourselves are far from perfect too in this regard, of course 😄 But the above three points should help!

 

If anyone else has any suggestions or examples of how they’re using Tags in Front, please feel free to share! 💪


Reply