CRM Tags

CRM tags are simple labels you can add to contacts to make important information visible and actionable.

An agency might use tags to identify VIP clients, flag overdue accounts, mark contacts who need onboarding, or separate people who should receive a particular campaign. Because a contact can have multiple tags, you can use them to describe different aspects of a relationship without changing the underlying contact data.

In Cleo, tags also go beyond organization. You can filter contacts by tag, build smart lists, and use tags as conditions for automations.

On this page

• What are CRM tags?
• How agencies use tags
• Tags vs. custom fields
• How to add a tag to a contact
• Using tags as warnings and reminders
• Using tags with smart lists and automations
• CRM tag examples for agencies
• Common questions about CRM tags

What are CRM tags?

A CRM tag is a label attached to a contact. Unlike a custom field, a tag has no predefined value or data type. You create a tag when you need a simple marker that tells your team something about a contact.

For example: vip, onboarding, at-risk, decision-maker, monthly-report, do-not-contact.

A contact can hold several tags at once. One contact might be both vip and decision-maker; another might be onboarding and monthly-report. That is the strength of tags. They mark information that crosses different parts of your CRM. A contact can belong to an enterprise client, be the main decision-maker, and require a quarterly review, and those are three independent tags.

Tags are also visible on the contact record itself. Anyone opening the contact reads the important context without running a report or digging through notes.

How agencies use tags

Agencies work with many clients, contacts, and recurring processes at the same time. Tags are a lightweight way to mark contacts that need similar treatment.

Consider a digital marketing agency managing twelve client accounts. It might use:

• onboarding for contacts currently going through onboarding
• monthly-report for contacts who receive monthly performance reports
• qbr for stakeholders who join quarterly business reviews
• decision-maker for people who approve proposals
• at-risk for contacts on accounts showing signs of churn
• paused for clients who temporarily stopped their campaigns

Now the agency filters on those tags instead of maintaining separate spreadsheets or searching account by account. When a new stakeholder joins a client, adding qbr puts that person into the next quarterly review. When a client pauses ad spend, adding paused makes that status visible to the whole team.

A tag does not need to describe the whole contact. It only needs to mark something useful to know or act on.

Tags vs. custom fields

Tags and custom fields both store information about a contact, but they suit different kinds of information.

Use a tag when you need a flexible label: vip, at-risk, onboarding, decision-maker.

Use a custom field when the information has a defined structure or value:

The rule of thumb: if you want to mark or classify a contact, use a tag. If you need to store a specific piece of data, use a custom field. enterprise works well as a tag when you just want to identify enterprise contacts. If you need the exact employee count, use a custom field. Picking the right one keeps your CRM easier to filter, automate, and maintain.

How to add a tag to a contact

Adding a tag takes a few seconds.

1. Open Contacts and select a contact.
2. Click Add tag on the contact record.
3. Enter the tag name.
4. Press Enter, or select an existing tag from the suggestions.

To remove a tag, click the × on its chip. Removing the tag means anything depending on it, a smart list or an automation, stops matching that contact. Check before you remove a tag an automation relies on.

Using tags as warnings and reminders

Tags do not have to be a marketing segment. They can act as visible warnings.

Because tags sit directly on the contact record, they work for information a team member should notice before acting.

Picture a junior account manager opening a contact to propose an extra service. The contact has an invoice-overdue tag. That one detail changes what happens next. Instead of sending the upsell email, the account manager resolves the outstanding invoice first. The tag produced no report and needed no dashboard. It put the context where the work was happening.

Using tags with smart lists and automations

This is where CRM tags become more than labels.

Build dynamic contact lists

A smart list can filter contacts by their tags. A smart list on monthly-report shows every contact who should receive the monthly performance report. When a contact gets the tag, they appear in the list. When the tag is removed, they drop out. The list stays connected to the contact data instead of becoming another spreadsheet to maintain.

Trigger automated work

Tags can also feed automations. Add the onboarding tag and an automation can:

1. Assign the onboarding workflow to the account owner.
2. Create the required setup tasks.
3. Schedule the kickoff process.
4. Send the internal notification.

Instead of relying on an account manager to remember every step, the tag becomes the signal that starts the process. The same pattern works for other agency work: renewal-soon creates a renewal task, at-risk notifies the account owner, monthly-report adds the contact to the reporting workflow, vip routes the request to the right team.

The tag stays simple. The automation decides what happens when that tag is present.

CRM tag examples for agencies

There is no single correct tagging system. The useful tags are the ones your team actually uses.

Client lifecycle: lead, onboarding, active, paused, churned

Account management: vip, at-risk, renewal-soon, invoice-overdue

Contact roles: decision-maker, champion, billing-contact, technical-contact

Communication: monthly-report, qbr, newsletter, do-not-contact

Avoid creating a tag for every piece of information in your CRM. If a tag is never used for filtering, visibility, or automation, it probably does not need to exist. A small, consistent set is easier to maintain than dozens of overlapping labels.

Common questions about CRM tags

Can a contact have multiple tags? Yes. Tags are independent, so a contact can hold as many as your workflow needs. One contact could be vip, decision-maker, and qbr at the same time.

What happens when I remove a tag? The tag comes off the contact, so the contact no longer matches filters, smart lists, or automation conditions that depend on it. Check whether an automation uses the tag before removing it.

Are tags the same as custom fields? No. Tags are flexible labels for classifying or flagging contacts. Custom fields are better for structured information such as dates, numbers, IDs, or predefined values.

How many tags should an agency have? There is no fixed number. Consistency matters more than count. A small set of well-defined tags is easier to work with than dozens of overlapping ones. Define what each important tag means and use the same naming across the team.

Can tags trigger automations? Yes. Tags can be conditions in an automation, so adding onboarding can start a larger process.

Can I filter contacts by tag? Yes. Tags can filter contacts and build targeted lists, so a label like at-risk or monthly-report becomes a working segment your team uses every day.