Rosi
All guides Telegram binding
Setup Guide

Finish Telegram
binding.

This is the second Telegram step for Rosi. Once the bot token is saved, you still need one trusted DM from your own Telegram account and one real group message so Rosi can bind the owner and start authorizing chats.

Owner first Send the first DM from the same Telegram account you entered during onboarding.
Groups later After the owner DM, add the bot to a group and send a real message there.
If it still misses messages Disable Group Privacy for the bot in BotFather.
Open BotFather Open Telegram
Overview

What happens in this step

Owner binding

The first direct message tells Rosi which Telegram account is the trusted owner.

Group authorization

Once the bot is inside a group, a real message there is enough for Rosi to discover and authorize that chat path.

Topics

If the group uses topics, send the first message in the topic you care about. Rosi can stay topic-aware there later.

Privacy mode

If BotFather still has Group Privacy enabled, ordinary group messages may not reach Rosi until you turn it off.

Step by step

How to finish Telegram binding

1

Send the first DM from your owner account

Open Telegram using the same account you entered in Rosi onboarding, search for your bot username, and send a simple direct message like hi.

2

Create or choose the first group

Pick the Telegram group where you want to use Rosi first. A brand-new group is fine if you want a clean test.

3

Add the bot to that group

Invite the bot you created earlier into the group. If the group uses topics, open the topic where you want Rosi to respond.

4

Send a real message in the group

Send a normal message after the bot is added. That is usually enough for Rosi to observe and authorize the group context.

5

If ordinary group messages still do not work, disable Group Privacy

Open BotFather, send /setprivacy, choose your bot, then choose Disable.

BotFather → /setprivacy → choose your bot → Disable
6

Return to Rosi

The shell should update from waiting-to-bind into a healthier Telegram state once the owner DM and first group message are seen.

You do not need to manually paste owner ids, chat ids, or topic ids into the app for the normal product flow.
Verification

How to know it worked

  • The dashboard should stop saying waiting for your first Telegram message.
  • After the first group message, the Telegram state should move toward group ready or another healthy authorized state.
  • If only DMs work but group messages do not, privacy mode is the first thing to check.
Common issues

What to check if binding still fails

You sent the first DM from the wrong account

Use the exact Telegram account whose username you entered during Rosi onboarding.

The bot is in the group but Rosi still waits

Make sure someone actually sent a message after the bot joined. The join event alone is not always enough.

DM works but group messages do not

Disable Group Privacy in BotFather and send another ordinary group message.

The app still shows stale status

Return to the Rosi app and refresh once. The shell also auto-refreshes while it is waiting for Telegram binding.