Continue Telegram-linked conversations and inspect outbound channel delivery from the Channels workspace.
Channels is the workspace for conversations and deliveries that cross Atoi's boundary. It brings Telegram-linked threads into the product and shows the state of connected Telegram or Slack destinations. Use it to continue work while away from the web app, then return to the underlying Atoi thread when you need full context.
Open a channel conversation
Open Channels and choose a conversation. Telegram conversations backed by an Atoi chat open directly into that chat, where the complete message history and project context remain available. The Channels list shows a recent message preview, the connection state, and the latest delivery result.
Atoi filters revoked and superseded Telegram sessions that have no meaningful history. Archived conversations with real history remain available. This keeps the list focused without erasing useful records.
A Telegram conversation may appear before proactive delivery has been configured. Replies still work in that conversation. Link a Telegram delivery destination when you also want Atoi to send approval requests and run updates without waiting for a new inbound message.
Coordinate from Telegram
Telegram exposes a compact operating menu for chat, tasks, delegations, approvals, and status. You can send normal text to continue the linked conversation and use the menu to inspect current work.
Supported low-risk approval requests can be approved or denied from Telegram. Requests that need a fuller review direct you to Atoi on the web before approval. This boundary prevents a compact channel action from bypassing the context required for a consequential decision.
Telegram delivery state appears with the relevant conversation. A delivery can be sent, delivered, failed, skipped, or have no recorded result. Failed deliveries remain visible so that an absent message is not mistaken for a successful handoff.
Understand Slack delivery
A linked Slack destination currently receives outbound Atoi updates. Replies written in Slack are not received by the Channels surface. Treat Slack here as a delivery destination, not as a two-way Atoi conversation.
This is separate from the Slack connector used by chats and projects for authorized workspace context. Connecting Slack under settings does not change the inbound limitation of linked Slack delivery in Channels.
Inspect and repair a connection
Linked destinations show whether they are linked, pending, or not linked. Verified links provide a test-send action. If a test fails, the failure is recorded in recent delivery activity; retry after correcting the connection.
Use Open to return to a conversation when one exists. For an unlinked or incomplete destination, open connection settings and finish the provider flow. Recent delivery activity shows outbound messages and errors, giving you a concrete record of what Atoi attempted to send.
When no channel has been connected, Channels shows No channels connected. When connections exist but have no message history, it shows No channel messages.