Business Connection and AI Prerequisites

Summary

AI state is gated by business connection validity, plan status, and wallet readiness. This guide maps each blocker to its corrective action. 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

• Diagnose blocked AI enable actions quickly.
• Reduce false debugging in downstream modules.
• Standardize readiness checks before launch.

Before you start

• Know current plan status of the bot.
• Check wallet balance and top-up status.
• Validate Telegram business connection health.

Step-by-step workflow

1. Open /dashboard/bots and locate target bot.
2. Inspect readiness indicators and warnings.
3. If wallet gate exists, fund wallet in /dashboard/billing.
4. If plan inactive, activate required plan for the bot.
5. If business connection invalid, reconnect in Telegram business settings.
6. Retry AI toggle after all prerequisites are green.

Key states and error handling

• Wallet gate is enforced for non-admin paths.
• Business connection invalid blocks downstream inbox reliability.
• Plan inactivity prevents full automation behavior.

Best practices

• Run readiness checklist before campaign launch.
• Document prerequisite failures in ops notes.
• Retest AI enable immediately after each fix.

Troubleshooting

• If AI stays off, verify all three gates at once (plan, wallet, connection).
• If connection is invalid repeatedly, re-link and test with real inbound message.
• If wallet is funded but blocked persists, reload billing and bots 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)

• Bot name is a workspace label used by operators; token validity is handled by backend verification.
• Connect action creates the bot record and triggers availability in other modules.
• AI toggle is constrained by plan, wallet, and business connection prerequisites.
• Rename is inline and should be committed only after checking bot identity.
• Delete is permanent and should be treated as irreversible operational cleanup.
• Wallet readiness for non-admin paths is tied to funded state and minimum thresholds.
• Business connection health directly impacts downstream Fan Inbox usage.
• Toast messages are the fastest failure classifier during onboarding incidents.

Operator checklist (before shipping changes)

• Validate token source before connect (BotFather-issued token only).
• Send /start in Telegram immediately after connection to complete handshake.
• Set an unambiguous bot display name for multi-bot workspaces.
• Check business connection and plan status before enabling AI.
• Do not delete a bot still used by active scripts or welcome flows.
• Record high-impact bot lifecycle changes in your internal changelog.

Real-world scenario

A bot appears connected but AI cannot be enabled. The operator checks wallet readiness, confirms plan state, and validates business connection. After prerequisites are fixed, AI toggle succeeds and inbox behavior normalizes.

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.