Telegram

Telegram is the richest chat integration. It supports:

• Bidirectional chat — message a bot, agent replies.
• Per-bot profile binding — one bot per agent flavor (@VZFinance_bot → VZFinance profile, @CodingBot → coding profile).
• Multi-bot — pair as many bots as you want, each independently bound.
• One-tap pairing with the shared @VonzioBot (no BotFather setup needed).
• Thread-claim — playbook nudges include inline buttons so your replies route back to the right session.

Option 1 — One-tap with @VonzioBot (recommended)

1. Click Settings → Integrations → “Pair @VonzioBot”.

2. Open the t.me link the dashboard returned. The pair code is prefilled.

3. Send the code. You’re linked.

This uses Vonzio’s shared bot. Good for general agent use.

Option 2 — Bring your own bot

If you want a custom bot username (e.g. @VZFinance_bot) or per-agent binding:

1. Create a bot with @BotFather. Save the token.

2. Click Settings → Integrations → “Add Telegram bot”. Paste the token. Optionally select a profile to bind it to.

3. Open the t.me link the dashboard returned. Send /link <code> (code is auto-prefilled).

4. Linked. Your bot now routes to your bound profile (or your first profile if unbound).

You can pair @VonzioBot AND bring your own bots. Each row is independent.

Bot routing

When a message arrives:

1. If the message starts with @<slug>, route to that profile.
2. Else if the bot is bound to a profile (bound_profile_id), use it.
3. Else use your default profile.

Bot commands

Command	Effect
/new	Start a fresh session. Optional <prompt> to send in one shot. Optional @slug to target a profile.
/clear	Alias for /new.
/end	End the active session.
/web	Get a dashboard link to the active session.
/model	Switch the model for the active session. Inline picker.
/sessions	List your recent sessions.
/agents	List your profiles.
/help	Show command help.

Plain text continues the active session.

Thread-claim (playbook nudges)

When a playbook nudge arrives with claim_thread enabled, the Telegram message ends with two inline buttons: 📎 Reply here and 💬 Keep my chat.

• Tap “Reply here” → next reply routes to the playbook’s session (full context).
• Tap “Keep my chat” → reply routes to your existing chat, playbook session ignored.
• Just type a reply (no tap) → defaults to claim. Agent’s first response prefixes “[Switched to <label> thread]” so the context switch is visible.
• 24h TTL on the auto-claim window.

This means: when a playbook tells you “reply with the PDFs”, you can just reply on Telegram and the agent will have full context of what it was asking for.

Disconnect

Use the Disconnect button on the bot’s row. BYO bots have their webhook removed; the platform-shared bot just unlinks you.

Note

For multi-bot users: end the active session on bot A (/end) before switching to bot B with a fresh /new — otherwise messages on bot A go to bot A’s session, on bot B to bot B’s session, and you may lose track.