Fan Inbox Business Connection Required State

Summary

When business connection is missing or invalid, Fan Inbox cannot operate normally. This guide maps the exact UI states and recovery path. 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

• Recover inbox availability quickly.
• Understand required connection state.
• Reduce false debugging in unrelated modules.

Before you start

• Confirm the exact warning message displayed.
• Identify affected bot.
• Coordinate reconnection owner.

Step-by-step workflow

1. Open /dashboard/conversations.
2. If blocked, read the exact connection warning state.
3. Go to /dashboard/bots and inspect business connection status.
4. Reconnect bot in Telegram business settings.
5. Return to inbox and retest thread visibility.
6. Ask fan to send a fresh message if needed.

Key states and error handling

• Blocking state title: 'Business Connection Required'.
• Invalid banner: 'Business connection invalid. Reconnect your bot in Telegram Business settings, then ask the fan to message again.'
• Inbox access depends on valid business connection.

Best practices

• Treat connection warnings as P1 operational blockers.
• Retest with real inbound message after reconnection.
• Log reconnection timestamp for incident tracking.

Troubleshooting

• If state persists after reconnect, verify you fixed the same bot.
• If only some threads fail, request new inbound message from fan.
• If issue recurs, audit Telegram business linkage stability.
• 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.