One fan, one creator profile
There is no shared thread and no group room. The constraint is what makes a conversation carry a fan record, a purchase history and an unread count that all mean something.
Every conversation is one fan and one creator. How the two sides of that thread differ, who decides which signals are sent, and where availability comes from.
In Velvet a conversation is strictly one fan and one creator profile, and the fan always sees the creator, whether the message was typed by the creator, a chatter or the assistant. The team side keeps the real author of every line, and the privacy signals a fan receives follow the profile owner's settings rather than whoever happens to be on shift.
A creator inbox has two audiences that must never see the same thing. The fan should see one relationship. The creator, the agency and an admin need to see who actually wrote each line.
Velvet resolves that in one place, at the moment a message is serialised for a fan, and leaves the stored record untouched. Everything below follows from that decision.
There is no shared thread and no group room. The constraint is what makes a conversation carry a fan record, a purchase history and an unread count that all mean something.
Messages written by a chatter or the assistant reach the fan under the creator's identity, across the message list, realtime delivery, guest chat, presence, read receipts and typing.
Sender identity and sender type are never rewritten in storage. Substitution happens only on the way out to a fan audience, so a creator can still see who wrote a line months later.
Whether a request is a fan audience is worked out from the caller's relationship to the conversation. It is never taken from a flag the client supplies.
Turning read receipts off means neither sending nor receiving them. A signal only appears when both sides have it on, and a chatter inherits the profile owner's setting rather than their own.
A creator can publish recurring shifts as an "usually active" signal, held with a timezone and converted to the fan's own local time. It is separate from live presence, which reflects real recent activity.
The conversation is presented as the creator throughout. Velvet's position is that the fan bought a relationship with the creator, and the complete record of who wrote what stays available to the creator, the agency and an admin.
Attribution fields are stripped from fan payloads rather than hidden in the interface, and every fan-facing emitter goes through the same substitution. That is why it is one place rather than a rule each screen has to remember.
Guest conversations have no fan on the other side, so nobody there can have opted out of a privacy signal. The counterpart counts as enabled, and the conversation still belongs to the creator profile.
No. The signals are reciprocal in both directions, which is what makes the setting a real privacy choice rather than a one-way advantage.
It is a schedule the creator publishes, up to forty recurring shifts with a timezone attached. Live presence is separate and reflects actual recent activity rather than a plan.
Open a creator account, send yourself a message from a second browser, and check that the presentation is the one you want fans to see.