Billing Auto-Recharge Controls

Summary

Auto-recharge reduces downtime risk but should be enabled only when payment setup is stable and policy is understood. 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

• Prevent wallet depletion incidents.
• Automate recharge safely.
• Reduce manual intervention load.

Before you start

• Add payment method first.
• Decide recharge amount policy.
• Confirm your team agrees on auto-billing ownership.

Step-by-step workflow

1. Open Billing Overview.
2. Locate auto-recharge controls.
3. Set recharge amount.
4. Enable auto-recharge switch.
5. Save settings and verify no error toast.
6. Monitor first trigger behavior in history.

Key states and error handling

• Save failure fallback: 'Unable to update auto-billing'.
• Enable guard message: 'Add a payment method to enable auto-billing.'
• Auto-recharge logic is tied to wallet safety thresholds.

Best practices

• Use conservative recharge amount that covers peak fee windows.
• Review auto-recharge settings weekly.
• Validate transaction history after each configuration change.

Troubleshooting

• If enable fails, confirm payment method setup is complete.
• If settings do not persist, retry and watch for mutation error toast.
• If unexpected charges appear, audit history filters by type and status.
• 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.