Organize contacts with tags in 6am

Organize contacts in 6am using labels with a clear meaning. Create the tag in the correct workspace, apply or remove it only for the intended contacts, and verify the resulting membership.

• Outcome: The intended contacts have the correct tags, unrelated tags remain unchanged, and the operator records the verification.
• Owner: A workspace administrator or member with tenancy: manage contacts permission.
• Tool: 6am dashboard → Contacts and Contact Tags.
• Inputs: The workspace, the inclusion/removal rule, the contact IDs or reliable identifying details, and the desired tag names.
• Scope: Tag definitions, individual and selected-contact changes, a single-tag filter, and behavior during contact merging. Tags do not send messages, start campaigns, or record marketing consent. Saved Smart Lists and AND/OR segments are outside this procedure.

01. Define the meaning and confirm the workspace

1. Check the workspace selector before searching or changing records. Contact lists, tags and permissions belong to the selected workspace.
2. Write one sentence explaining who qualifies, the evidence used, who owns the tag, and when it should be removed. Example: source:webinar identifies contacts acquired through a particular source; interest:seo identifies an expressed interest. Use an event-specific name when different webinars must remain separate.
3. Search Contact Tags for an existing equivalent. Reuse the same definition; do not create competing spellings for the same meaning. Names accept up to 80 characters and are unique within the workspace, ignoring capitalization and repeated spaces.
4. Confirm the intended contacts using their email, international phone or native 6am contact ID. A name alone may identify more than one person. If duplicate records remain, complete SOP 081 before assigning tags.
5. Keep the selection rule and original membership in the private job record when you need a reversible change. There is no separate tag-operation history or automatic undo screen.

02. Create a tag definition

1. Open Contact Tags from the sidebar or the button in Contacts.
2. Click Create tag, enter Tag name, and submit the form. Creating a definition does not assign it to any contact.
3. Find the saved name in the table. Contacts using this tag shows the current usage count. If the name already exists, close the form and use the existing tag.
4. Return through View contacts. Creating tags inside the assignment dialog is not supported; create the definition first.

03. Add or remove tags on one contact

1. In Contacts, search for the intended person. Open View if necessary to confirm the native ID and current tags before changing anything.
2. Use the row action Add tags or Remove tags. Select only the tag definitions intended for this change; up to 50 tags can be chosen per operation.
3. Submit and wait for the success notification. Adding preserves all existing tags and does not duplicate an existing association. Removing detaches only the selected tags; it does not delete their definitions or the contact.
4. Reopen the contact and confirm the expected tags and at least one unrelated existing tag. A repeated add or remove has the same final membership, but always inspect the current result after an uncertain response.

04. Apply the change to selected contacts

1. Search the contact list or open Filter → With tag to find contacts already carrying a tag. Choose the tag and click Apply filters. This is a single-tag filter, not a saved segment.
2. Select only the intended rows on the current page. The header checkbox selects that page, not every page of results. Review names and identifiers, then use the selected-record action Add tags or Remove tags.
3. Check the selected-contact count shown in the dialog and choose the tags. The server accepts at most 500 contacts and 50 tags per operation; the visible page may contain fewer contacts. Work page by page for larger groups and record completed selections to avoid omissions.
4. Submit once and wait for the notification with the affected contact count. The operation is synchronous; there is no separate Bulk actions queue to inspect.
5. If any selected contact or tag is no longer available in the workspace, the entire operation is rejected. Refresh and rebuild the selection. Do not assume that part of the group was changed.
6. Verify membership with With tag, inspect a changed contact and an unselected control contact, and confirm unrelated tags remain. Removing the tag used by the active filter may make the changed rows disappear; clear the filter and search by ID or email to verify them.

05. Rename or delete a definition deliberately

1. In Contact Tags, find the exact definition and review Contacts using this tag.
2. Use Rename for a naming correction that keeps the same meaning. Submit the revised name and verify it appears on existing contacts; renaming preserves associations. To introduce a different meaning, create a new tag instead.
3. Use Delete tag only when the definition is obsolete for every contact in this workspace. Read the confirmation and current usage count. Deletion removes the definition and all its associations, while retaining the contacts.
4. Deletion has no automatic recovery. Recreating a name does not restore its previous membership. To remove the label from only some people, cancel deletion and use Remove tags on those contacts.
5. If the tag was renamed while a dialog was open, close the dialog and review the current definition before retrying.

06. Account for imports and merges

• CSV contact imports do not map or assign tags. Complete SOP 083, verify the imported records, then apply tags in Contacts.
• A confirmed merge preserves the union of both contacts' tags on the surviving contact. The archived source loses active tag associations; the merge history preserves the original and resulting tag names.
• The merge comparison shows Tags kept after merge. If tags or their names change before confirmation, compare the contacts again. After merging, review the combined labels against their business rules and remove any label that no longer applies.

Exceptions and completion criteria

The job is complete when the workspace, membership rule and changed selection are recorded; the intended membership is verified; unrelated tags and an unselected control remain unchanged; and any unresolved record has an owner and next action. This editorial review describes the native 6am workflow delivered on the date shown above.