Customer Buckets
Building bucket rules
The conditions that decide who is in a bucket, exclusions, and checking the result before you use it.
Last updated September 2, 2026
Rules are what define a bucket. Each one narrows the group, and together they answer "who is in this?".
What you can build rules on
| Rule on | Example |
|---|---|
| Categories | People filed as customers. |
| Business | People at a particular kind of business. |
| Custom fields | Anything your organisation records about people. |
| Calls | People who have called you. |
| Contacts and activity | People added recently — the last 7 or 30 days. |
| Products | What somebody has bought. |
Exclusions
A bucket can exclude people as well as include them. Exclusions are usually the thing that makes an automation safe: "everyone who has not bought in a year, except anyone we are already chasing".
Preview before you build on it
- Add one rule and look at the count.
- Add the next and watch which way it moves.
- Preview the actual people. Recognise them? If the names look wrong, the rules are wrong.
- Only then point a workflow at it.
THE RULES KEEP RUNNING
A bucket is not a snapshot. Somebody who buys tomorrow may fall into it tomorrow, and a workflow attached to it will treat them accordingly. Build rules that will still be right in six months, not just today.