Summary\nWhen configuring Telegram multi-account via , if is not explicitly set, it's easy to end up with confusing default routing behavior (inbound/outbound) when only a non-default account (e.g. ) is configured.\n\nIn a real setup, adding without also defining led to: \n- Confusion about which bot identity was used for sends\n- Periods where DM messages appeared not to be consumed by the expected bot\n\n## Expected\nDocs should strongly recommend (or enforce) defining whenever is used, and clarify how top-level interacts with accounts.\n\n## Suggested docs patch\n- In and , add a warning:\n - If any accounts are configured, define explicitly.\n - Consider aligning top-level to the same token as for clarity.\n\n## Environment\n- Clawdbot: 2026.1.24-3\n- Telegram provider (long polling)\n