Library·SOP·Operations
Build, preview and maintain workspace contact segments using current fields and tags, with clear AND/OR rules.
Last reviewed: · Editorial review
Clarity, structure and references reviewed in this version. This is not a test in a live account.
Build a saved contact segment in 6am that recalculates its members from current contact fields and tags. Save the rules once; reopen the list to see who matches now.
This procedure covers native 6am smart lists, including creation, preview, editing, deletion and verification. Have contacts in the workspace and create any required tags first. A list is shared within that workspace with people who can manage contacts.
Available fields are First name, Last name, Email, Phone, Company and Notes, plus Contact tag. Custom fields, City, opportunities, form submissions and workflow triggers are not part of this editor. Lists do not send messages, create consent or automatically apply tags.
Related procedures:
Describe who belongs before opening the editor. Use facts already stored on the contacts. For example: contacts tagged interest:seo whose Company equals Acme or Beta.
Use AND inside one group: every condition must be true. Use OR between groups: matching any complete group is sufficient. The example becomes:
Repeat the tag condition in both groups. A separate group containing only Company equals Beta would also include untagged contacts from Beta. If one group is enough, do not create another.
Text operators are Equals, Does not equal (includes empty), Contains, Does not contain (includes empty), Is empty and Is not empty. Text matching ignores case; use the exact stored spelling and check accented names in the results. Contains treats %, _ and punctuation as literal text, not search wildcards. Text values are limited to 255 characters. Phone comparisons use the stored phone string; this editor does not normalize a typed number.
Is empty matches a missing value or an empty string. Negative text conditions also include empty fields. Add an Is not empty condition in the same group if empty values should be excluded. Empty/not-empty rules do not need a Value. Changing a field or operator clears its previous value; complete the condition again.
The list stores rules, not a frozen set of people. Reopening or refreshing the table recalculates members from current contact data. Imports, edits and tag changes can change membership. Merged source contacts are archived and excluded; the surviving contact is evaluated using its current fields and combined tags.
A page already open is not a live stream of every change. Refresh and inspect the selection immediately before any bulk action. Existing contact tag actions operate on explicitly selected contacts on the current page, up to 500 contacts and 50 tags per operation. They do not target every current or future list member. See SOP 085 for the tag workflow.
If you need a historical audience or proof of consent, this dynamic list is not that record. This release has no saved membership snapshots, scheduled refresh jobs, messaging or automation attached to lists.
Use Edit rules to rename the list or change its groups. Preview again, save and reopen View contacts to check the effect. If another team member changed the list while your editor was open, the system blocks the stale save. Reopen it, review the latest rules and then apply your intended change.
Use Delete list and confirm only when the team no longer needs those rules. Deletion removes the saved list, not its contacts or tags. There is no list trash or automatic undo; record any rules you may need before deleting them. A stale deletion is also blocked if the list changed after confirmation was opened.
The intended workspace is selected; the list name identifies its purpose; all groups are deliberate; the current count is plausible; matching and nonmatching examples were checked; no repair warning remains. Record the reviewed rule and the date in your operational notes. Recheck the audience before using it later.
