Static vs dynamic contact lists: which one you actually want
Most list problems are really one wrong decision made at the moment the list was created. Three list types, and the question that picks between them.
Almost every complaint about a contact list traces back to one decision made in the first ten seconds of creating it. Someone wanted a list of open opportunities, built it by hand, and two weeks later it still held the deals that closed. The list was not broken. It was a snapshot, and they needed a question.
LeadWise gives you three kinds of segment. The difference between them is not what they contain, it is when they decide what they contain.
The three types
| Type | Decides membership | Best for |
|---|---|---|
| Static | Once, when you add someone | A named group that should not move under you |
| Dynamic | Every time you open it, from filters you set | A condition you want tracked continuously |
| AI | Every time you open it, from a description you wrote | A fit judgement that filters cannot express |
Static: a snapshot you control
You put contacts in, and they stay until you take them out. Nothing the contact does changes their membership. This is the right choice when the grouping is a decision rather than a fact: the forty accounts you committed to this quarter, the people you met at a trade show, a list handed to you by a partner.
It is the wrong choice for anything describing a state, because states change and a static list will not notice.
Dynamic: a saved question
You set filters, and membership is recalculated from the current data whenever the segment is read. Add a contact whose health status turns to warm and they appear. Mark one bounced and they leave. Nobody maintains it.
Use it for anything phrased as a condition: contacts with no activity in thirty days, everyone at a company size you sell to, every lead from last week that has not been contacted.
AI: a description of fit
You describe the customer you want in plain language and LeadWise evaluates contacts against that description. It recalculates like a dynamic list, but it can act on things no dropdown contains: what a company sells, who it sells to, whether it is the kind of business your product suits.
The cost is that it is a judgement rather than a rule, so it is worth reviewing rather than trusting blindly on day one. Writing a good description is its own skill.
The question that decides it
Ask yourself: if a contact changed tomorrow, should this list change with them?
- No, the group is fixed and I decide who is in it. That is static.
- Yes, and I can state the change as a rule about a field. That is dynamic.
- Yes, but the rule is about what kind of company they are. That is AI.
What happens when you enroll one in a sequence
This is where the difference stops being academic. Enroll a static list and you enroll exactly the people in it at that moment. Enroll a dynamic or AI list and anyone who later matches can be picked up on the next pass, which is what you want for an always-on motion and emphatically not what you want for a one-time announcement.
If you are running a campaign that should reach a fixed audience once, use a static list even when a dynamic one would have been easier to build.
Do
- Name the list after the question it answers, not the campaign that used it first.
- Prefer dynamic when the grouping describes a state, so nobody has to maintain it.
- Use static for anything a human hand-picked and wants to stay hand-picked.
- Review an AI segment the first few times before you send to it.
Don't
- Do not build a static list of "everyone who has not replied". That is a condition, and it will be stale by Thursday.
- Do not enroll a dynamic list in a one-time announcement. Late joiners will get it weeks later.
- Do not create a second list because the first went stale. Fix the type instead.
- Do not stack so many filters that you cannot say out loud what the list means.
Can I convert a static list into a dynamic one?
Not in place, because the two store different things. Create the dynamic segment with the filters you want and retire the static one once you are happy the membership matches.
Does a dynamic list slow down as it grows?
No. Membership is resolved from indexed fields when the segment is read, so a list of fifty thousand behaves like a list of fifty.
Can a contact be in more than one segment?
Yes, and that is normal. Segments are views over your contacts, not folders that own them.