Direct answer
Velvet splits a fan list two ways: an automatic relationship stage that moves forward on real activity, and manual groups and tags that only a person changes. The two never overwrite each other, because the automation writes only rows it created itself and a stage set by hand is marked as such.
Most segmentation advice is a list of segments. The more useful question is which splits a system should maintain for you and which it must never touch.
Velvet draws that line in one place, and knowing where it sits is what makes the rest of a segmentation strategy safe to build.
Summary
- The automatic side is a single stage per fan: cold, qualified, active, vip or churned.
- The manual side is groups and tags, and neither is ever changed by a rule.
- A stage set by a person is marked as manual and automation stops touching it permanently.
- Churned is never automatic, because deciding a relationship is over is a judgement.
Where the line sits
Automation records what a fan did. People record what they intend to do about it. Velvet keeps a source flag on the stage so it can tell the two apart, and the automated writer only acts on rows it created or rows that do not exist yet. A chatter dragging a lead on the board is therefore a permanent decision.
- Nothing about a group or a tag is ever written by a rule.
- The stage is one field, so there is only one thing automation can touch.
- Overriding a stage is a normal action, not an exception someone has to remember to protect.
What moves a stage forward
Three things advance a fan. The first message they send moves them from cold to qualified. A paid offer presented in chat does the same, kept as a distinct signal so the two can be told apart afterwards. Money moving is what advances them further, and lifetime spend at or above $100 with one creator targets vip rather than active.
- The stage is written in the same transaction as the activity behind it, so the two cannot drift.
- Stage order is explicit, so a rule can check that a move is forward before making it.
- Nothing moves a fan backwards automatically; that direction is always a human decision.
What a group is actually for
Groups carry intent. They are named, coloured and priority-ranked, and a fan can belong to as many as you like at once, which is what makes them useful for things a lifecycle stage cannot express. A group is also the unit a broadcast targets, so a group that never receives a message is a group that should not exist.
- Adding a fan to a group never removes them from another one.
- Priority ranking orders the working board rather than the fans themselves.
- Tags carry facts about a fan; groups carry your plan for them. Keeping them separate keeps both readable.
Using both without confusing them
A useful setup treats the stage as the answer to where this relationship is, and groups as the answer to what happens next. Selecting on both is what makes a send precise: active fans in the renewal group, or vip fans in the group for a specific offer. Selecting on either alone is usually too blunt to be worth writing for.
- A broadcast can target groups, a tag, an audience, or an explicit list of fans.
- The vip threshold is lifetime spend with one creator, not spend across the platform.
- A fan who goes quiet keeps their stage; quietness is something you notice, not something the system decides.
Outcomes
- Decide for each split whether it describes what happened or what you plan; put it on the matching side.
- Set a stage by hand when you disagree with it, rather than building a workaround.
- Delete groups that have never received a message.
- Use tags for durable facts and groups for the current campaign.
- Check the stage source before assuming a fan's position was set by a rule.
Questions
Can automation demote a fan?
No. Automated requalification only moves fans forward, and it never touches a stage a person set.
Where exactly is the vip line?
At $100 of lifetime spend with that creator. Below it, a purchase advances a fan to active; at or above it, the same event targets vip.
Why is churned manual?
Because it is a conclusion rather than an observation. A fan who is quiet for a month may be on holiday, and a rule that writes them off is a rule that costs money.
Should groups mirror the stages?
No. That duplicates one field into five buckets that then need maintaining. Use groups for the things a stage cannot say.
Does a fan know which group they are in?
No. Groups exist on the creator's side. A fan sees only the messages they receive, in their own conversation.
Split one list and see the difference
Open a creator account, let the stages fill in on their own for a week, then build your first group around what you actually plan to send.