One profile at a time
The Telegram module is enabled per creator profile rather than per account. An agency running six creators connects six channels, and each one carries its own connection state, its own contacts and its own outbox.
Telegram becomes a channel into the creator's existing Velvet inbox. What the connection covers, what it never asks for, and what happens when it drops.
Connecting Telegram to Velvet turns it into a messaging channel on one creator profile, feeding the same inbox, the same fan records and the same paid links the rest of Velvet already uses. The connection is authorised once by the creator on their own profile, and nobody working the inbox afterwards ever holds the credential.
Most Telegram tooling asks a creator to run a second product alongside the one they already use. Velvet treats Telegram as a channel: the conversations arrive in the inbox that already holds the fan record, the purchase history and the paid links.
That framing has consequences worth knowing before you connect. This page covers what the module actually does, what it deliberately does not do, and where the boundaries sit.
The Telegram module is enabled per creator profile rather than per account. An agency running six creators connects six channels, and each one carries its own connection state, its own contacts and its own outbox.
Connecting starts a phone-code authorisation and finishes when the code is verified. The pending state expires after ten minutes, so an abandoned attempt does not leave a half-open door behind it.
Once connected, contacts and conversations are synchronised into the profile's workspace, which is what makes an existing Telegram audience visible as fan records rather than as a list of names.
Outgoing messages sit in an outbox with a retryable state instead of failing silently. A message that could not be delivered is visible as a message that could not be delivered.
Disconnecting ends the channel for that profile and records when it happened. The conversation history that already reached Velvet stays where it is, attached to the fan records it belongs to.
The creator authorises the channel on their own profile. A chatter reaches it through their invitation to that profile, which means onboarding a chatter never involves passing a login to anyone.
No. Fans keep messaging where they already are. What changes is where the creator's side lives: one inbox, with the fan record, the purchase history and the paid links attached to the conversation.
No. The module is enabled per creator profile, and each connection carries its own state. A roster is connected one profile at a time on purpose.
What already reached Velvet stays attached to the fan records it belongs to. Disconnecting ends the channel and records when, rather than erasing what happened before.
Because a half-finished authorisation is an open door. Ten minutes is long enough to read a code off a phone and short enough that an abandoned attempt cannot be resumed by someone else later.
Nothing. The credential belongs to the creator's authorisation. A chatter's access comes from their accepted invitation to the profile and ends when that invitation is revoked.
Enable the module on a single creator profile, sync it, and send one message before you connect anything else.