Fan Inbox Bot and Thread Selection Flow

Summary

Most inbox errors start with wrong bot context. This guide enforces the right selection order for safe operations. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Prevent cross-bot reply mistakes.
• Keep context integrity per fan thread.
• Improve triage speed under load.

Before you start

• Know which bot owns current campaign.
• Check top utility bar bot context.
• Confirm thread belongs to selected bot.

Step-by-step workflow

1. Select target bot context first.
2. Open conversation sidebar and locate fan.
3. Enter thread and verify identity context.
4. Compose or review message actions.
5. Return to list and continue queue.
6. Repeat after bot switch only when necessary.

Key states and error handling

• Active bot mismatch can hide expected threads.
• Thread content depends on selected conversation id.
• Context switching too often increases operator error rate.

Best practices

• Batch work by bot whenever possible.
• Annotate priority threads in internal process.
• Avoid mid-reply bot switching.

Troubleshooting

• If expected thread missing, verify selected bot.
• If wrong history appears, close and reopen the thread.
• If queue seems stale, refresh and validate inbound activity.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Active bot context drives visible conversations and available thread actions.
• Conversation sidebar is the queue entrypoint and must be triaged continuously.
• Thread view is the context source for safe manual interventions.
• Composer can be disabled by wallet or gating states.
• Business connection required state blocks normal inbox operations.
• Invalid business connection banner indicates reconnection is mandatory.
• Top utility area is the place to verify bot context before replying.
• Toolbar controls should be used with explicit thread intent, not random experimentation.

Operator checklist (before shipping changes)

• Confirm active bot before sending any message.
• Read latest thread context before manual intervention.
• Check for banners (connection/wallet) before assuming AI issue.
• Prioritize high-intent conversations first during load.
• Escalate repeated failure patterns into config or script changes.
• Retest after each incident fix with a fresh inbound message.

Real-world scenario

Inbox becomes partially unavailable for one bot. The operator detects business connection warning, reconnects the bot in Telegram business settings, then validates recovery with a fresh fan message and thread response test.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.