Inbox
Unified inbox for all account conversations
The inbox aggregates DM, group, channel, and bot conversations across every account in your workspace into a single real-time feed.
Unified inbox concepts
Every message received by any of your accounts appears in the unified inbox. Messages are deduplicated by Telegram message ID and chat ID.
| Feature | Description |
|---|---|
| Real-time updates | WebSocket connection delivers new messages as they arrive. No polling. |
| Per-account filter | Filter the inbox to show messages from a single account only. |
| Per-chat filter | Filter to a specific chat, group, or channel. |
| Unread counts | Per-account and per-chat unread counters. |
| Search | Full-text search across all messages (indexed at ingestion). |
| Reply | Reply to any DM or group message from the inbox. |
Real-time updates
The inbox streams new messages over Socket.IO at wss://telegramos.net/ws. The connection is authenticated with your dashboard session — the access JWT in the Socket.IO handshake (auth.token), or the session cookie. API keys are not accepted on this transport.
Events arrive as named Socket.IO messages rather than a single envelope: system.connected when the socket is ready, then inbox.message for a new message, notification.new, account.power_changed and the rest. Subscribe to one account's stream with subscribe:account; the server refuses accounts your workspace does not own.
If you need events server-side, poll the REST endpoints described under API or point a scraping job at your own webhook URL.
Edit and delete handling
When a message is edited on Telegram, the inbox receives an update event and replaces the stored message text. The original text is discarded. Edit history is not retained.
When a message is deleted on Telegram, the inbox receives a delete event and removes the message from the feed. A tombstone placeholder is not shown; the message simply disappears.
Attachments
Attachments (photos, videos, documents, voice messages) sent and received through the inbox are stored in the platform's S3-compatible object storage.
| Property | Value |
|---|---|
| Storage backend | S3-compatible (AWS S3 or compatible) |
| Encryption at rest | AES-256 |
| Encryption in transit | TLS 1.3 |
| Max file size | 2 GB per file |
| Retention | Tied to account lifecycle. Files are deleted when the associated account is released or deleted. |
| Download | Direct S3 presigned URLs, valid for 1 hour. |
Login-code redaction for rentals
For rented accounts, messages from Telegram's system chat (peer ID 777000) are automatically redacted from the inbox. This includes login codes, 2FA recovery codes, and session confirmation messages. The redaction happens at ingestion time. The message is stored with a placeholder instead of the original content.
Why this matters: The 777000 chat is where Telegram sends one-time login codes. If a rental holder could view these, they could authenticate as the underlying phone number's owner from another Telegram client, breaking the rental isolation model. Redacting these messages is a core privacy and security boundary.
Inbox retention
Messages in the unified inbox are retained for the lifetime of the associated account. When an account is released (subscription end + grace period), all messages for that account are permanently deleted. There is no separate inbox-only retention period.