Shared Telegram inbox for multiple accounts

A workspace can connect several Telegram accounts. The product sets no maximum; the same number simply cannot be added twice to the same workspace.

• Login with a QR code, or with the code Telegram sends to the account, plus the two-step verification password if the account has one.
• On connection, the CRM reads the conversations of the last 180 days, then runs a full sync every 30 minutes.
• Private messages arrive in real time. Groups and channels update at each sync, and their history loads live when you open them.
• Each conversation always replies from the account the lead wrote to.

The inbox is shared, but not everyone sees everything. A member who is not a manager sees the leads assigned to them or that they took on. The “see all conversations” permission opens the other conversations; other permissions control sending and deleting messages.

• New leads are assigned one by one, in bulk, or automatically: in turn or to the least busy closer.
• A response-time alert (30 minutes by default) notifies the assigned closer and the owner.
• Monitoring flags links sent to clients, crypto wallet addresses that are invalid or not on your list, and conversations left unanswered.
• The activity log, for managers only, keeps track of the team’s actions.
• An internal chat brings the team together: general channel, direct messages, mentions and attachments.

• Saved replies open when you type “/” in the message box, with your saved media and voice notes.
• The AI suggests three replies in the lead’s language based on the conversation, and can improve or translate your draft. You read it before sending.
• Ctrl + K finds a lead, a conversation, a deposit or a tag.

Automatic messages, follow-up rules and AI are covered on the Telegram auto reply page.

A conversation becomes a lead in one click. It then enters your affiliate pipeline, with its source, broker, tags, deposits and timeline. If it comes from a tracked ad, the campaign and original click are already on the card: see Telegram ad tracking.

Telegram limits sending without publishing its thresholds. When Telegram imposes a wait (FLOOD_WAIT), the CRM pauses fetching messages, media and read receipts for that account until the delay is over. Media download two at a time per account, and a conversation’s read receipt goes out at most once every 30 seconds.