Credits and usage
Finance and ops monitor paid capacity through Credits Dashboard, AI Usage Analytics, Invoices, and Subscription Plans. Marketing and AI modules consume credits—check balance before large email, SMS, calling, or agent campaigns.
Video
Who can do this
Owner/Admin typically; some usage views for ops.
Before you begin
- Active subscription
- Internal alert threshold for low balance
What you'll accomplish
- Current credits known
- Usage trend reviewed
- Invoices archived
Step-by-step procedure
| Page | Path | When to open |
|---|---|---|
| Credits Dashboard | /credits-dashboard-management | Before bulk sends |
| AI Usage Analytics | /ai-usage-analytics | After AI spikes |
| Invoices | /invoice-management | Monthly accounting |
| Subscription Plans | /subscription-management | Upgrades / limits |
Weekly checklist
- Open Credits Dashboard; note balance vs planned campaigns.
- Scan AI Usage Analytics for anomaly (runaway agent loops).
- Download latest Invoices for finance.
- Confirm Subscription Plans limits (WhatsApp instances, seats) before launches.
Extended guidance
Finance should reconcile Invoices with Credits Dashboard debits monthly. Ops leads watch AI Usage Analytics after enabling new tools on multiple agents. Pre-purchase credits before holiday campaigns—payment delays can pause sends mid-flight.
Practice scenarios
Before a marketing week, snapshot Credits Dashboard, estimate email+SMS+voice spend, confirm headroom. Download the latest Invoices PDF and match line items to campaign send dates in your runbook.
Sandbox validation
Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.
Team rollout checklist
Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.
Keep learning
Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.
Verify your work
- Balance covers planned send
- Invoice PDF downloads
- Usage chart matches known campaign dates
Tips
Set an internal Slack/email alert when credits cross your safety threshold.
Compare AI Usage Analytics spikes with Command Centre incident timelines.
Troubleshooting
| Sudden zero balance | Failed payment—open Subscription Plans | | Usage spike unknown | Review calling + email campaign dates | | Feature locked | Plan limit—upgrade or disable module |