Fan Inbox Layout and Navigation

Summary

This article explains core layout so operators can move quickly between fan list, thread context, and reply actions. 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

• Navigate inbox efficiently.
• Reduce missed messages.
• Speed up operator handoffs.

Before you start

• Select active bot context.
• Ensure conversation list is loaded.
• Know target fan segment you want to review.

Step-by-step workflow

1. Open /dashboard/conversations.
2. Use conversation sidebar to locate fan thread.
3. Open thread and review context history.
4. Use toolbar to inspect conversation controls.
5. Use composer for manual responses.
6. Return to list and repeat triage loop.

Key states and error handling

• Desktop shows split layout; mobile can switch focus states.
• No selected thread shows guidance placeholder.
• Top utility area reflects global bot context.

Best practices

• Process high-intent threads first.
• Use consistent operator notes externally when handing off.
• Avoid multitasking too many active threads.

Troubleshooting

• If layout seems empty, verify selected bot and conversation availability.
• If thread panel is blank, select a conversation explicitly.
• If mobile behavior feels inconsistent, re-enter thread from list state.
• 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.