Telegram CRM for creators6 min readUpdated 2026Direct answer
Velvet keeps one fan record per creator profile, holding what the fan did, what stage the relationship is at, the labels a human applied, and observations drawn from the conversation with a confidence score attached. Nothing in it is inferred from a Telegram profile; every field has a source you can point at.
A CRM is only worth the trust you put in it, and trust comes from knowing where each number came from. This page lists the fields Velvet keeps about a fan and names the origin of each one.
It is written for a creator or an agency arriving from Telegram, where the fan history lives in a scrolling thread and nothing is countable.
Summary
- One record per fan per creator profile, because a conversation on Velvet is strictly one fan and one creator profile.
- Activity totals come from settled purchases, tips, gifts and custom requests, counted once.
- The relationship stage is one of cold, qualified, active, vip or churned, and carries whether a human or the system set it.
- Observations pulled from a conversation carry a confidence score and can be corrected or dismissed.
One record per creator, not one per platform
A Velvet conversation is strictly one fan and one creator profile. That constraint is what makes a fan record countable: every purchase, tip, gift and custom request resolves to the same row, so a lifetime total is a sum rather than a guess. A fan who talks to two creators has two records, and neither can see the other.
- A guest conversation has no fan account behind it, and the record reflects that rather than inventing one.
- Merging is never implicit: two identities stay two records until someone decides otherwise.
- The record belongs to the creator profile, so an agency managing five creators sees five separate histories.
What the fan did, counted once
Activity is written in the same transaction that records the underlying event, which is what keeps the rollup from drifting away from the rows it summarises. Lifetime spend is held in integer cents, never a rounded currency figure, and it only counts money that actually settled.
- A pending payment is not spend until it settles, so the total never has to be revised downwards.
- Last activity is a timestamp on the record, not a scroll position in a thread.
- The same rollup feeds the stage automation, so the two can never disagree.
The stage, and who put it there
Every fan sits at cold, qualified, active, vip or churned. Alongside the stage, the record keeps who set it. Automation only ever writes rows it created itself, so a stage a chatter set by hand survives every subsequent automated pass.
- A first message moves a fan from cold to qualified; a purchase moves them further.
- Churned is never set automatically. It is a judgement a person makes.
- Stage ordering is explicit, so a rule can check that a move goes forward before making it.
What the conversation implies, held at a confidence
Velvet can attach observations drawn from a conversation to a fan record. Each one carries a confidence score, a link back to the message it came from, and a status of active, corrected or dismissed. That structure exists so a wrong inference can be corrected in place instead of quietly steering follow-up for months.
- An observation names the message it was drawn from, so it can always be checked against what the fan said.
- Correcting an observation replaces it and records that a human overrode it.
- A separate chatter-safe wording exists for observations a chatter should act on but not read verbatim.
Outcomes
- Open one fan record and trace each number back to the event that produced it.
- Check the stage source before changing a follow-up script; a manual stage means someone already decided.
- Dismiss observations you disagree with rather than working around them.
- Keep tags for facts and groups for intent; mixing the two makes both useless.
- Treat lifetime spend as settled money only, and plan against the available balance.
Questions
Does Velvet import a fan's Telegram profile?
No. The record is built from what the fan does inside Velvet: messages, purchases, tips, gifts and custom requests. Nothing is copied from a social profile and presented as fact.
Why one record per creator instead of one per fan?
Because a conversation belongs to a creator profile. A shared fan record across creators would mean one creator's purchase history informing another creator's inbox, which is not a boundary a roster should cross.
What happens to the record when a fan has no account?
A guest conversation is kept as a guest conversation. Velvet does not fabricate a fan identity so that a row looks complete.
Can a chatter see the whole record?
Only the parts their permissions allow. Revenue visibility and analytics visibility are separate switches, and some observations carry a wording written for a chatter to act on rather than the raw note.
How is lifetime spend calculated?
As a sum of settled purchases, tips, gifts and custom requests in integer cents, written in the same transaction as the event itself so the total cannot drift from the rows behind it.
Look at a real fan record
Open a creator account, start one conversation and watch the record fill in as the fan acts.