Fan Inbox Composer and Toolbar Operations

Summary

Composer and toolbar are the operator execution layer. This article focuses on safe intervention patterns during ongoing AI conversations. 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

• Send precise manual interventions.
• Use toolbar controls during escalations.
• Prevent accidental low-quality replies.

Before you start

• Open correct thread and read latest context.
• Check if wallet or connection banners are present.
• Define objective for the next reply.

Step-by-step workflow

1. Open thread in Fan Inbox.
2. Review latest fan message and negotiation stage.
3. Draft response in composer with clear CTA.
4. Use toolbar functions when thread needs manual override.
5. Send response and monitor immediate reaction.
6. Adjust script/persona only after observing pattern, not one message.

Key states and error handling

• Composer may be disabled when wallet blocked state is active.
• Toolbar appears only with selected conversation.
• Manual interventions should be reflected instantly in thread.

Best practices

• Keep replies concise and intent-driven.
• Use manual override for high-value edge cases only.
• Escalate recurring issues into scripts/config updates.

Troubleshooting

• If composer is disabled, verify wallet and billing prerequisites.
• If toolbar action has no visible effect, reload thread state.
• If replies feel off-tone, review bot configuration and script context.
• 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.