Pomio CRM lets a team filter on labels, next to teams, locations and live search across deals, companies and tasks. Labels are only useful in a filter when everyone uses the same words for the same thing, and that is a decision, not a setting.
What goes wrong when everyone makes their own labels
When every user can type a new label, the list grows quickly. One person tags a deal “Hot”, another “hot lead”, a third “Priority”, and all three mean the same thing. A filter on one of them then misses the other two, so the list a manager looks at on Monday is incomplete without anyone noticing. After a year the label list is longer than the pipeline, and people stop trusting it.
What a label is for, and what it is not for
A label marks something the CRM has no field for: a check that is needed before follow-up, a campaign, a region you report on separately, or a temporary project. Do not use labels for information that already has a field. The stage belongs in the pipeline, the owner in the owner field, and the origin of a lead in the source field. The same goes for the industry category of a company and the forecast category of a deal. When a label repeats a field, the two drift apart and nobody knows which one is right.
Keep the list short and write down what each label means
Most small teams manage with ten to twenty labels. Give each label a name that explains itself, and one line that says when to use it and when to remove it. Keep that list where the whole team can find it, for example in the onboarding notes for new colleagues. A label without a written meaning becomes a personal note, and personal notes do not belong in a shared filter.
Let one person add new labels
New labels are fine, but someone has to decide on them. Let the main administrator, or the backup administrator, add or rename labels, and let everyone else ask. That keeps duplicates out and is easy to arrange when the CRM has a small number of named administrators. A request for a new label is also a good moment to ask whether a field or an existing label would do the job.
Use labels in the filters you already look at
Labels prove their value in the views the team actually uses. Add a label filter to the weekly pipeline review, for example all open deals with a label that means “check before sending”, so those deals are handled in the meeting rather than forgotten. A label that never shows up in a filter or a review is usually a label nobody needs.
Clean up the list every quarter
Once a quarter, go through the list with the administrator. Merge labels that mean the same, move the records to the label you keep, and retire labels that are no longer used, such as one for a campaign that has ended. Do the move as one bulk action where your role permits it, so the records stay complete. Update the written list at the same time.
How Pomio CRM supports a fixed list of labels
In Pomio CRM labels are filterable, next to teams, locations and live search across deals, companies and tasks. Bulk actions are available where the user’s role permits them, so merging or retiring a label does not mean editing records one by one. Roles and their scope (own, team or organisation) are enforced on the server, and important actions are recorded in the audit log, so it stays clear who changed what.
A practical checklist
Agree one short list of labels; write down one line per label on when to use and remove it; let only an administrator add or rename labels; never use a label for stage, owner, source, amount or another existing field; add label filters to the weekly pipeline review; merge duplicates and retire unused labels every quarter with a bulk action; update the written list after every change.
Go deeper
How many labels does a small business CRM need?
Most small teams manage with ten to twenty. If the list grows beyond that, check whether some labels repeat a field or mean the same thing as another label.
Should labels be in one language?
Yes. Pick one language for the label names, even in a team that works in two, so a filter does not miss records tagged in the other language.
Can a record have more than one label?
Yes, as long as each label answers a different question. Two labels that mean almost the same thing on one record are a sign the list needs a clean-up.
What do we do with old labels from a previous CRM?
Do not import them all. Map the useful ones to your new list, turn the ones that describe a field into that field, and leave the rest out.