Billing Subscriptions per Bot

Summary

Subscriptions are applied at bot level. Correct plan assignment is required for AI and operational features to stay available. 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

• Activate the right plan per bot.
• Understand starter/pro display values.
• Prevent plan-related outages.

Before you start

• Identify bot(s) requiring plan changes.
• Check current wallet balance.
• Understand current displayed prices (Starter $19.90, Pro $39.90 coming soon).

Step-by-step workflow

1. Open Subscriptions tab in /dashboard/billing.
2. Select target bot from list.
3. Review current plan and billing cycle context.
4. Choose desired plan action.
5. Confirm plan change and wallet charge impact.
6. Return to bot-dependent feature page and validate availability.

Key states and error handling

• Plan update success should reflect in bot-level capabilities.
• Plan update failure fallback: 'Unable to update plan'.
• Pro can be displayed as coming soon in current UI context.

Best practices

• Apply plan changes during monitored windows.
• Validate bot feature gates right after subscription change.
• Keep one operator owner for plan changes per shift.

Troubleshooting

• If plan update fails, verify wallet sufficiency and retry.
• If feature remains locked, refresh target page and verify bot plan status.
• If wrong bot updated, immediately correct subscription selection.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Overview tab shows wallet balance and funding controls.
• Subscriptions tab applies plan changes per bot.
• History tab supports status/type filtering for financial audits.
• Information tab provides policy context and operational reminders.
• Top-up validation enforces minimum amount requirements.
• Auto-recharge requires payment method readiness and explicit settings save.
• Displayed plan pricing is visible in UI and should guide operator expectations.
• Billing toasts are primary diagnostics for top-up and subscription failures.

Operator checklist (before shipping changes)

• Keep wallet above safety margin before high-volume campaigns.
• Validate bot selection before changing subscription tier.
• Use preset top-up values when rapid funding is required.
• Enable auto-recharge only after payment method is confirmed.
• Review history filters weekly for anomaly detection.
• Re-test Bots/Fan Inbox behavior after major billing actions.

Real-world scenario

AI actions stop during a high-traffic period. The operator finds low wallet balance, tops up using a preset amount, confirms subscription health per bot, and verifies inbox composer availability returns immediately.

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.