The billing detail that decides whether AI Employee is cheap or expensive

The pricing looks straightforward until you read one phrase in HighLevel’s documentation, and then it reads very differently.

AI Employee is billed per enabled location. Not per agency, per sub-account. That single detail is the whole cost model, and it is why agency owners describe the bill as creeping rather than jumping.

The per-location model

HighLevel’s guide to AI Employee access, rebilling and reselling lists two tiers, a Growth plan at 50 dollars per month and an Unlimited plan at 97 dollars per month, each per enabled sub-account.

Do the arithmetic against a real agency rather than a demo account. Ten client sub-accounts on the Unlimited tier is 970 dollars a month for the AI layer alone, before a single call is placed. That is frequently more than the agency plan those ten accounts sit inside, and the HighLevel pricing guide is the place to check current plan rates and compare against your own.

Nothing about this is hidden. It is simply a different shape from the rest of the platform: the agency plan gives unlimited sub-accounts, and this does not. An agency that grew comfortable with “unlimited” as the pricing metaphor will find AI Employee behaves like a per-seat product.

Prices as published at the time of writing. Rates for AI products change more often than platform plans, so verify against HighLevel’s own pages before quoting a client.

Voice calls cost twice

The second thing worth understanding: the AI subscription does not include telephony.

Phone system charges apply to calls regardless of the AI plan, which means a Voice AI conversation costs the subscription plus the underlying call minutes. HighLevel’s LC Phone pricing and billing guide covers that side.

This is not a criticism, every voice platform works this way, and our own Vapi and Retell builds have exactly the same structure: a per-minute cost for the conversation and a separate one for the phone line. It matters here because the AI Employee subscription reads as all-inclusive and is not.

The practical consequence is that per-minute cost, not the subscription, dominates the bill on any account with real call volume. A subscription is a floor.

The rebilling side, which is the actual opportunity

HighLevel supports fixed-rate rebilling for Conversation and Voice AI, letting an agency charge sub-accounts a predictable flat rate per AI minute rather than passing through variable usage.

That turns the cost model from a problem into a product, and it is the part most agencies underuse. A flat per-minute rate is easier for a client to understand than usage-based billing, easier to budget against, and the spread between wholesale and retail is where the margin lives.

Two things make it work rather than backfire:

Set the rate against measured usage, not a guess. Fixed-rate rebilling means you absorb the variance. If you have not measured what a typical client account actually consumes, you are pricing blind, and the account that adopts voice enthusiastically is the one that hurts.

Only enable what is used. Because billing is per enabled location, an account with the feature switched on and nobody using it is pure cost. Enabling AI Employee across every sub-account by default is the most common way agencies find the bill.

When native AI Employee is the right choice

It genuinely often is, and we build custom voice agents for a living, so take this as a preference rather than a pitch.

Choose native AI Employee when the requirement is standard, inside GoHighLevel, and you want it live this week. It is already wired to the CRM, there is nothing to integrate, and the rebilling machinery exists. For inbound answering and straightforward conversation handling across a portfolio of similar clients, that convenience is worth a lot.

Choose a custom build when the conversation needs logic the native product does not express, when it must reach systems outside GoHighLevel mid-call, when latency is competitive rather than adequate, or when per-minute economics at volume justify controlling the stack. Those are the conditions under which a Vapi or Retell build earns its cost, and outside them it does not.

The wrong reason to build custom is that native pricing surprised you. Run the arithmetic on both before deciding, because a custom agent has its own per-minute costs and its own maintenance.

The number to actually calculate

Before enabling anything across a portfolio, work out three figures for a single representative account:

1. Subscription for that sub-account at the tier you would use.
2. Expected minutes per month, from real call data rather than optimism.
3. Per-minute cost of those minutes, telephony included.

Multiply by the number of accounts you would enable. Compare that to what you would charge under fixed-rate rebilling.

If the spread is comfortable, enable it deliberately, account by account, on the ones that will use it. If it is not, the answer is not usually a different platform. It is enabling fewer accounts.