Manage guide

Organize Contacts with Tags

Create a small, governed set of reusable labels so your team can find contacts, coordinate follow-up and support approved workflows without losing the evidence behind each decision.

Verified guideLast reviewed August 22, 2026

Quick answer

Use tags for decisions your team will act on

Define each tag before using it, apply it only when its condition is true and remove it when that condition changes. Keep the supporting evidence in the conversation, a field, a note, a task or an approved connected record. Review shared tags before renaming or deleting them.

1 Define2 Apply3 Filter4 Act5 Review

Information design

Use a tag for a reusable category

Tags are reusable labels for organizing contacts and conversations. They can support inbox filters, follow-up decisions, reporting and approved connected workflows.

Tag

A shared category or condition used to group, filter or coordinate work.

Service interest, qualified, booked or follow-up category.

Field

A structured value with a defined meaning and expected format.

Preferred location, company or appointment date.

Note

Concise human context that does not fit a reusable structured value.

Customer asked to reconnect after a specific internal review.

Tags are not a complete record. A tag shows a category, not why it applies. Keep the conversation as evidence and use the right supporting record when the detail or next action matters.

Tag design

Start with a small, controlled tag system

Create tags around decisions your team will actually use. A smaller governed set is more useful than hundreds of unreviewed labels whose meaning changes from person to person.

1Decision

What action it supports

2Definition

When it is true

3Owner

Who governs it

4Lifecycle

How it is removed

5Dependencies

What relies on it

Interest

Service category

Apply after the contact confirms an approved service or product interest.

Define the qualifying statement

Qualification

Defined state

Use only when the contact meets the written, objective qualification rule.

Keep evidence in context

Progress

Booked status

Apply when the approved booking condition is confirmed and remove if it is reversed.

Document both directions

Follow-up

Action category

Use with a clear owner or task when a person must complete a specific next step.

A tag alone is not ownership

Search before creating. Avoid near-duplicates, synonyms, personal opinions and labels that depend on private interpretation.

Naming and governance

Give every important tag one stable meaning

Write a one-sentence definition and owner for each important tag. Use clear, stable names that make sense to every authorized person who will filter, report or act on them.

Definition

What exact condition makes the tag true?

Prevents people and automations from applying different meanings.

Owner

Who approves changes and resolves overlap?

Keeps the shared system controlled as the team grows.

Add rule

Which evidence or event applies the tag?

Makes manual and automated updates testable.

Remove rule

When is the condition no longer true?

Stops old states from remaining indefinitely.

Dependencies

Which filters, messages or workflows use it?

Protects downstream behavior during maintenance.

Consistency beats decoration. Choose one naming pattern and casing convention, then keep it stable. Do not create punctuation or capitalization variants of the same concept.

Manual updates

Apply and remove tags from the contact or conversation

Open the relevant contact or conversation and add the existing tag whose defined condition is true. Remove it when the condition no longer applies.

Confirm the contact.Verify that you are working in the intended record and conversation.
Use the existing tag.Search for the governed label before creating anything new.
Check the definition.Make sure the conversation or approved record supports the condition.
Apply or remove it.Change the label only as required by the documented lifecycle rule.
Preserve the next action.Create or update the appropriate task, note, assignment or connected record when work remains.

Do not treat a tag as proof. If the reason may be questioned later, preserve the supporting conversation or approved record rather than relying on the label alone.

AI permissions

Let an AI Agent manage only selected tags

An AI Agent can be allowed to add or remove specific tags when its rules are met. Write both sides of the rule and test what happens when the contact gives a direct, ambiguous, contradictory or changed answer.

Add ruleApply after the contact confirms a defined condition

Remove ruleRemove after that condition is no longer true

Direct answer

The contact clearly states or confirms the condition defined for the tag.

Ambiguous answer

The Agent asks an approved clarifying question or leaves the tag unchanged.

Contradictory answer

The Agent avoids guessing and follows the defined clarification or escalation rule.

Changed answer

The remove rule clears the old state and the current evidence remains available.

Keep automated labels objective. Do not ask an Agent to infer or apply subjective, sensitive or consequential labels from vague conversation context.

Operational use

Filter and act without confusing category with ownership

Use governed tags to narrow an inbox view, find a contact group, support follow-up decisions, review patterns or provide an approved input to a connected workflow.

Organize

Find the defined group

Filter by the current approved tag and verify that representative records match its definition.

Act

Use the correct work control

Assign a responsible person, create the next action or run the approved workflow with its own safeguards.

Inbox filter

Narrows the view to contacts with the selected label.

Review conversation status, ownership and urgency separately.

Follow-up

Groups contacts that share a defined follow-up category.

Use an assignment or task for responsibility and timing.

Reporting

Supports counts or trends when definitions remain stable.

Document changes so historical interpretation stays clear.

Connected workflow

Provides an approved trigger or condition.

Test permissions, entry criteria, duplicate handling and failure behavior.

A tag is not an assignment. If a person owns the next step, assign the conversation or create the appropriate task instead of assuming the label creates responsibility.

Bulk changes

Control the scope before changing many contacts

If your account provides a bulk tag action, treat the filtered selection as a data change. Confirm the definition and scope on a small representative sample before applying or removing a tag across the full set.

1Filter

Build the intended scope

2Count

Check selection size

3Sample

Review records

4Change

Apply one action

5Verify

Spot-check results

Do not rely on the filter name alone. Check the actual selected records, excluded cases and any connected workflow that may start when the tag changes.

Safe maintenance

Review dependencies before renaming or deleting a tag

Before changing a shared tag, check saved filters, assignments, messages, reports and connected workflows that may depend on its exact value.

Unused tags

No current contacts, owners or documented dependencies.

Confirm the absence of hidden workflow use before removal.

Overlap

Two labels represent the same condition or decision.

Select the canonical tag and plan a verified consolidation.

Stale state

The condition changed but the remove rule did not run.

Correct affected contacts and repair the lifecycle rule.

Dependencies

Filters, assignments, messages, reports or workflows use the tag.

Update and test every dependency before changing the label.

Before changeInventory records, owners, rules and downstream uses

After changeVerify representative contacts and every affected workflow

Deletion can change behavior. Preserve the definition and dependency list until the replacement or removal has been verified.

Privacy and access

Keep labels objective, necessary and appropriately restricted

A short label can still disclose sensitive information or drive a consequential action. Use the narrowest category needed for the approved workflow and limit access to tags that trigger important decisions.

✓

Objective condition

The tag has a written business definition supported by approved evidence.

✓

Necessary purpose

The category supports a real operational decision, filter or workflow.

✓

Controlled access

Only authorized people and connected workflows can view or change it.

✓

Appropriate retention

The label is removed when its condition ends or its approved purpose no longer applies.

Never encode private detail in a tag name. Avoid credentials, financial details, health information, personal judgments or other sensitive text that the workflow does not need.

Troubleshooting

Resolve common tag problems

Two similar tags exist

Pause new use and compare definitions

Choose the canonical label, find every dependency and plan a controlled consolidation instead of deleting immediately.

Tag returns the wrong contacts

Check the definition and update source

Review representative records, manual changes, Agent rules, imports and connected workflow activity.

AI Agent applies the tag too early

Tighten the evidence rule

Require the defined confirmation, add ambiguous examples and specify when the Agent must leave the tag unchanged.

Old tags remain in place

Repair the remove condition

Define the reversal event, correct affected records and retest changed-answer behavior.

Workflow starts unexpectedly

Stop and inspect dependencies

Preserve the contact, tag event and workflow details, then verify entry criteria and duplicate handling.

Team cannot tell who should act

Add ownership and a next step

Use an assignment or task with context and timing; keep the tag only as the shared category.

Preserve evidence before correcting a shared label. Record representative contacts, the tag definition, who or what changed it and every affected workflow.

Common questions

Contact tag questions

How many tags should we create?

Start with the smallest set that supports real decisions. Add a new tag only when it has a distinct definition, owner, lifecycle and operational use that an existing tag cannot serve.

When should I use a tag instead of a contact field?

Use a tag for a reusable category or condition. Use a field for a structured value with a defined format, and use a note for concise contextual information.

Can the AI Agent add and remove tags?

It can manage selected tags when you define objective add and remove rules. Test direct, ambiguous, contradictory and changed answers before relying on the rule.

Should a tag create the next action?

The tag can group contacts or support a workflow, but use an assignment, task or approved connected record to establish responsibility, timing and completion.

Can I rename or delete an unused tag?

Check saved filters, assignments, messages, reports and connected workflows first. A tag with few current contacts may still be a dependency elsewhere.

Can tags contain sensitive customer details?

Avoid subjective or sensitive labels. Use only the minimum objective category required for the approved purpose, control access and keep detailed evidence in the appropriate protected record.

Need tag help?

Send the definition and affected workflow

Include the ConvoRev account, exact tag name, written definition, expected add and remove rules, representative synthetic examples and any affected filter or connected workflow. Remove credentials and unnecessary private customer information.

Email ConvoRev support