Ability to Edit/Delete System Tags
We cannot edit or delete system tags, which results in duplicate tags being created/used. Please give us the option to edit or remove system tags.

-
Raquel Johnson commented
In addition to allowing us to customize, color code and delete system generated tags, allow us a wider variety of colors to choose from so we can color our code our tags so we don't need to use the same color on different tags. It makes it much easier for those with dyslexia.
-
Amy Ruiz commented
The system tags are hard to work around with our own tags, they seem to be in the way. Also, why have a tag of buyer and one of buyers?
-
Carolyn Vaught commented
I try to tell our team to not use the system/legacy tags as its duplication but this just causes confusion.
-
System tags have different case formats. "Downline" is capitalized and "collaborator" isn't. It's definitely a little thing but I promise the High C's out there will love fixing it.
-
LABS Team commented
Although there are a few tags I like that are created by the "System", I find that the a number of them I don't use and find it very annoying to have them in my scroll list. Is there a way to change the coding to allow agents access to delete original tags created by the "System" in the same fashion that you can do when you have created a tag yourself that you don't want anymore. Thanks
-
LABS Team commented
When the update changed them to the same color as my other tags, it really messed the team tagging system up.
-
LABS Team commented
Through trial and error I have learned that when you import database files into Command, the system will create a new custom tag so that it can import properly. For example, importing a spreadsheet that has "Girl Scouts" as a custom tag will populate it as a System-Created tag (which you cannot delete or change...ever). This makes the database management/cleanup incredibly complicated for teams. Please allow us to delete or edit "system" created tags AND lead sources so that we can avoid cluttered databases.
*Side note:
A workaround that I have found for this is to populate the custom tag/lead source ahead of importing so that it can latch on to the existing placeholder instead of "creating" a new one for you. However, this still does not solve the issue of past created tags/sources.