Chat exclusion hides a particular conversation in the current workspace. It affects every member's ability to view and send in that chat, not just your own list.
Exclude a chat
- On the Messages page, confirm the actual account and conversation being operated.
- Open the conversation's context menu and select Exclude chat.
- Read the confirmation and proceed.
Members with View access to an account can set exclusions. Once effective, the chat disappears from the workspace's normal conversation lists, unread totals, and notifications. History, attachments, and sending are also blocked. Auto-replies and broadcasts must recheck exclusions.
Undispatched pending content is canceled. Content already submitted to Telegram cannot be guaranteed to be recalled. This does not delete, archive, or mute the conversation in Telegram itself. The same account's exclusions in other workspaces are independent.
Restore a chat
You can review exclusions you created in two places:
- Settings → Data and privacy: your exclusions in the current workspace.
- Settings → Telegram accounts → Excluded chats for the relevant account: exclusions by account.
Only the person who created an exclusion can restore their own record. Administrators cannot restore it on someone else's behalf. If multiple people excluded the same chat under an account, restoring your record may leave the chat hidden because another record remains. The page does not disclose whether other people set exclusions.
Restoration does not restart canceled sends. Analytics resumes from a new boundary and does not backfill removed data or the excluded period. Access to chat history depends on current account access, chat permissions, and content still available from Telegram.
Disconnecting, reconnecting, or disabling an account does not automatically delete exclusions.
Distinguish related actions
| Action | Effect |
|---|---|
| Silent preview | Views chat without marking it read; does not hide the chat |
| Mark unread | Changes the Telegram account's shared unread reminder; does not undo read receipts |
| Mute or archive | Changes actual Telegram conversation settings |
| Exclude chat | Hides the current workspace's access to a chat under the account without changing Telegram settings |
| Delete message | Performs actual Telegram message deletion within the confirmed scope |
| Disconnect account | Removes the account's association with the current workspace |
File and ticket visibility
Personal templates are available only to their creator. Storage totals do not let administrators read their text or file details. Shared template content follows workspace visibility. Make sure content is suitable for the team before sharing.
Ticket comments are for internal collaboration and are not automatically sent to Telegram. Linked ticket messages store references, not permanent backups of Telegram message bodies. References may stop working if the original message becomes inaccessible.
Settings → Sensitive words is not available yet. Do not rely on it to automatically block content.
Common questions
| Question | What to do |
|---|---|
| Nobody on the team can find a conversation | Check filters, permissions, and exclusions; you can only review exclusions you created |
| Data and privacy shows an ID instead of a name | The conversation index does not yet have a usable name; wait for sync. The ID can still be used to verify the chat |
| Restoring a chat did not resume a broadcast | Canceled sends do not resume automatically; use the original task results to decide what to do |
| An administrator cannot see another person's exclusions or personal templates | This is a visibility boundary; do not bypass it by reading content from the database |
Implementation and rules: chat exclusions, Data and privacy page, and analytics definitions.