Billing Tabs and Navigation Overview

Summary

Billing centralizes wallet, plans, and financial activity. This article helps operators navigate each tab with the right intent. 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 billing quickly during operations.
• Use the right tab for each task.
• Reduce accidental financial mistakes.

Before you start

• Know which bot is impacted by planned changes.
• Define whether action is funding, plan, or audit.
• Ensure account has billing permissions.

Step-by-step workflow

1. Open /dashboard/billing.
2. Start in Overview for wallet status.
3. Use Subscriptions for per-bot plan management.
4. Use History for transaction investigation.
5. Use Information for policy reminders.
6. Return to Overview to confirm final wallet state.

Key states and error handling

• Billing view may show loading state before data hydration.
• Each tab has independent controls and side effects.
• Subscription actions affect bot-level feature availability.

Best practices

• Confirm tab context before executing action.
• Record major billing actions in internal logs.
• Review overview after every financial mutation.

Troubleshooting

• If tab content is missing, refresh and re-open billing.
• If action context is unclear, return to Overview and restart flow.
• If values seem stale, wait for query refresh then re-check.
• 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.