Start with a small tag system
Useful tags describe something the team will act on: plan, customer type, issue theme, or follow-up state. Avoid creating near-duplicates such as “billing” and “payments” unless they mean different workflows.
Create a lightweight shared vocabulary for customers, topics, and follow-up.
Useful tags describe something the team will act on: plan, customer type, issue theme, or follow-up state. Avoid creating near-duplicates such as “billing” and “payments” unless they mean different workflows.