creator paid community6 min readUpdated 2026Direct answer
Velvet has no group room: a conversation is strictly one fan and one creator profile, so a broadcast to a group fans out into that many individual sends instead of posting to a shared thread. Each fan then replies privately, keeps their own unread state, and can be followed up on without the rest of the group watching.
Creators arriving from a Telegram channel expect a paid community to be a room. Velvet deliberately does not have one, and the reason is worth understanding before you design an offer around it.
A room makes one relationship out of a hundred fans. Velvet keeps a hundred relationships and gives you a way to address them at once.
Summary
- A conversation is one fan and one creator profile, and that constraint is what everything else is built on.
- A group is a named, coloured, ranked selection of fans, and a fan can be in several at once.
- Sending to a group creates one private message per member, using the same delivery path as any other message.
- A single send is capped at 500 recipients, which is a deliberate limit rather than an inconvenience.
A group is a selection, not a room
Fan groups are buckets a creator drags fans into: each has a name, a colour and a priority ranking. Membership is many to many, so adding a fan to a new group never removes them from another. A group has no thread, no member list a fan can see, and no shared history.
- A fan can be a VIP and a renewal risk at the same time, because groups do not compete.
- Priority ranking orders the board for the person working it, not for the fans.
- Groups sit alongside tags and the automatic relationship stage rather than replacing either.
One send becomes many sends
Broadcasting to a group reuses the ordinary conversation and message infrastructure rather than inventing a group thread. The send resolves the group's members and creates one message in each fan's existing conversation. From the fan's side there is nothing to distinguish the mechanics from a message written to them alone.
- Each fan can reply, and the reply lands in their own thread rather than a shared feed.
- Unread counts, read receipts and typing indicators stay per conversation.
- The history record keeps what was sent and which groups were targeted, so a send can be audited afterwards.
Five hundred at a time, on purpose
A single send is limited to 500 recipients. The cap is a discipline as much as a safeguard: a message written for five hundred people is usually a message written for nobody, and a paid community that receives identical broadcasts stops feeling paid within a month.
- Recipient discovery, authorisation and delivery happen inside one transaction, so a partial send cannot leave a history row without messages.
- Sends can target an audience, a tag, one or more groups, or an explicit list of fans.
- The recorded recipient count is what actually went out, not what was selected.
What a fan can do here that a channel member cannot
In a channel, a member is one of many and their message competes with everyone else's. In a Velvet conversation the fan has the creator's attention by default, buys without leaving the thread, and can be given content that nobody else in their group received.
- A paid offer can be sent to one fan at a price that is theirs alone, within the $500 delegated ceiling.
- Leaving is per fan and reversible, rather than a public exit from a member list.
- A quiet fan is visible as a quiet fan, instead of disappearing into a member count.
Outcomes
- Build groups around what you will actually send, not around how fans feel to you.
- Keep a group small enough that its message could plausibly have been written to one person.
- Use the automatic relationship stage for lifecycle and groups for intent.
- Review the send history before repeating a broadcast to overlapping groups.
- Follow up individually on replies; the reply is the reason the send was worth making.
Questions
Can fans see each other?
No. There is no shared room and no member list. Every message sits in a conversation between one fan and one creator profile.
Is a broadcast slower than posting to a channel?
It creates one message per member rather than one post, which is why the 500 cap exists. In exchange each of those messages can be replied to privately and followed up individually.
Can a fan be in more than one group?
Yes, in as many as you like. Adding a fan to a group only adds the membership and never removes them from another one.
What stops a broadcast turning into spam?
The recipient cap, the send history, and the fact that every recipient can reply to you directly. A broadcast that annoys people produces immediate, attributable feedback.
Does a paid community need a subscription?
Not necessarily. Groups work with any mix of subscribers, one-off buyers and fans who have not yet paid, because membership is a selection rather than an entitlement.
Build one group and send to it once
Open a creator account, put five fans in a group and send them something you would have been happy to write to one of them.