Wondering how end users utilize the tagging function, in a group that manages a small-scale project for new retirement plan implementations to help manage outstanding tasks and timelines. Does it make the most sense to tag by client and use statuses? I was also thinking that tags for status or stage may be useful. What has worked for your team?
Question
Tags
Hey kwalker
Great question! So there isn't really a single best practice, as the ideal tagging strategy depends on how your team works and what you want to report or filter on. Generally the best options are to work with Tags, Rules and Statuses. These three features work together to help you get the most out of your workflow. I've attached some information below including a link to Help Center articles relevant to each topic.
Tags: Tags make it easy to 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. We also have a Front Academy course here to learn more about using tags.
Rules: You can use Front rules to automate your workflows, helping you handle repetitive tasks to save time and increase your team's efficiency in Front.
Statuses: You can Leverage rules and macros to automatically update ticket statuses to enhance your team's productivity and improve customer satisfaction. This article outlines example workflows that your team can implement using Front to automate ticketing processes.
Many teams use a combination of these, while relying on conversation assignment and reminders to track ownership and timelines. Keeping your tag structure simple and consistent also tends to make filtering and reporting easier over time. I hope this information has helped, but if you have any other questions please feel free to let us know.
Login to the community
No account yet? Create an account
Use your Front credentials
Log in with Frontor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.