The wallet is not a second subscription. It is a usage meter.
HighLevel uses the Agency Wallet to pay for supported variable services. The platform charges the agency card to add credits, deducts activity from the wallet, and automatically recharges when the balance falls below the configured minimum.
Common wallet-funded activity includes the Phone System, Email System, email validation, AI pay-per-use, address autocomplete, and premium workflow features. A quiet account may use little. An active multi-client operation can create frequent deductions.
A blank usage estimate is unknown, not $0. Start with a documented allowance, then replace it with the first month of actual transaction history.
Usage draws down credits; the card restores them.
- 01
The agency funds the wallet. HighLevel charges the card on file to load credits.
- 02
Supported activity uses credits. Charges are deducted as phone, email, AI, validation, or premium events occur.
- 03
The balance reaches its minimum. HighLevel's automatic recharge logic can charge the card again.
- 04
The agency reviews attribution. Billing tools break down charges so the operator can identify the sub-account and service.
The official path is Agency View → Settings → Billing → Wallet & Transactions. Review the balance, transaction history, recharge amount, and minimum balance there.
Some rates are fixed; others depend on actual activity.
Long SMS messages can contain multiple billable segments. Phone and messaging rates vary by geography and product. Voice AI subscriptions can cover supported AI usage while phone charges still apply.
Passing a cost to a client does not remove agency risk.
HighLevel says supported rebilling without markup is available on the $297 Unlimited and $497 Agency Pro plans; markup is associated with Agency Pro and SaaS Mode. Product-specific requirements can still apply.
The agency is charged through its wallet first, then the sub-account is charged when rebilling is enabled. That sequence creates exposure to failed client payments, refunds, disputes, configuration mistakes, and spikes that occur before recovery.
- Client price and included usage.
- Card-on-file and failed-payment process.
- Markup or at-cost policy.
- Refund and dispute ownership.
- Charges by sub-account and service.
- Wallet recharge frequency.
- Unexpected message segments or calls.
- AI and workflow overages.
Turn the first 30 days into a real operating baseline.
- 01
Estimate before enabling. Use the HighLevel cost calculator to record the assumptions.
- 02
Launch one complete path. Limit the first test to one sub-account and one measurable workflow.
- 03
Review transactions weekly. Attribute every material line to a service and sub-account.
- 04
Replace estimates. Use actual phone, email, validation, AI, and workflow activity in the next budget.
- 05
Set an exception threshold. Investigate a recharge, service, or account when it exceeds the approved operating range.
The base subscription buys access. The wallet reflects activity. Budget and review them as separate lines so growth in usage does not look like an unexplained invoice.
What we checked
Prices and program details change. These official pages were checked on August 30, 2026; verify the checkout price before buying.