CRM → Segments (/crm/segments).
Segments page

​
Static or dynamic

TypeWho is in itGood for
StaticWhoever you put there, by hand or by an add-to-segment nodeFixed lists: a Q1 batch, a cooldown list
DynamicWhoever matches the rules right nowLiving groups: customers tagged hot-lead in Vietnam
A dynamic segment stores no membership. Every time it is listed or resolved it queries the database against its rules and caches the answer for 60 seconds. Change a customer’s tag or company and the next read picks it up. Force it with ”…” → Recompute now.

​
Create one

1

+ New segment

Give it a name, and a description saying why it exists — teammates read that description when deciding whether to reuse it.
2

Pick static or dynamic

Static starts empty and you fill it. Dynamic asks for rules next.
3

Write the rules (dynamic only)

Predicates joined by AND and OR groups: tag contains or does not contain, company in a list, has or has not received inbound since a date, fit score on a product above a number, country, language, owner, currently in or never in another segment.

​
The segment page

/crm/segments/:id has three tabs.
The customer table for this segment. A static segment gets Add customers and Remove; a dynamic one gets Recompute. Bulk actions work here the same as in the customer table.

​
Segments that do a job

  • A cooldown segment holds customers who are not ready. The Exit — Cooldown node fills it. Name it Cooldown — <reason> so the reason survives.
  • An exclusion segment holds everyone campaign A already touched, so campaign B can exclude it and avoid a double send.
  • A suppression mirror is a dynamic segment of customers with at least one suppressed contact, useful when auditing who you have stopped contacting.
A static segment never removes anyone by itself. If a cooled-off customer warms up again, take them out by hand — or add a tag with an add-tag node and build a dynamic segment that filters on it.