diff --git a/apps/docs/automations.mdx b/apps/docs/automations.mdx
index 9a38cac79..98a8c2d50 100644
--- a/apps/docs/automations.mdx
+++ b/apps/docs/automations.mdx
@@ -169,9 +169,9 @@ Create arbitrary scheduled agent runs with:
   has an explicitly verified account email
 
 Each custom automation row summarizes its cadence, workspace target, report
-destination, creator, and most recent run. Its runs also appear as Sessions in
-the normal Session history. Blank slate runs do not clone repositories or
-require source-control credentials.
+destination, creator, next scheduled run, and most recent run. Its runs also
+appear as Sessions in the normal Session history. Blank slate runs do not clone
+repositories or require source-control credentials.
 
 When creating an automation through Roomote chat, ask for **suggested tasks** or
 **launchable follow-ups** if qualifying findings should become tasks that
@@ -209,8 +209,8 @@ the Session is what talks to the report destination.
 Runs deliver to every custom-automation report destination: Slack, Discord,
 Microsoft Teams, Telegram, or Email. Chat providers support a channel/chat or
 a direct message to the automation owner; Email is private only. Each run keeps
-a distinct Session, and the report links
-back to that Session in the web app. The Session transcript shows the
+a distinct Session, and each Email run starts a separate mail thread. The report
+links back to that Session in the web app. The Session transcript shows the
 automation's configured prompt and any delegated task cards, and its normal
 composer lets a signed-in teammate continue the run from the dashboard. Replies
 on chat providers continue the Session directly there, and replies to an Email
diff --git a/apps/docs/providers/communications/telegram.mdx b/apps/docs/providers/communications/telegram.mdx
index bcc8246ca..ad1efdf47 100644
--- a/apps/docs/providers/communications/telegram.mdx
+++ b/apps/docs/providers/communications/telegram.mdx
@@ -128,6 +128,13 @@ naturally.
 Telegram does not support native drafts in group chats, so groups use
 Telegram's standard typing status and receive completed replies instead.
 
+When Fast delegates coding work, Roomote posts one separate live task message
+in the same chat or topic. It edits that message with compact, expandable
+progress and settles it as completed, failed, stopped, or waiting for input
+instead of posting a stream of status messages. **Open in Roomote** opens the
+selected task inside its Session; the Session still sends the final result as a
+normal reply.
+
 Existing task chats and topics keep their active-task, `request_user_input`,
 and resumable-snapshot behavior. If Fast cannot start a conversation, Roomote
 says so in the chat instead of starting a task another way. Fast automation