Set usage limits on resold HighLevel Voice AI

On October 30 HighLevel put SaaS Usage Limits into Labs for agencies on its Pro plan. You can now give each SaaS client a ceiling on Voice AI and Conversation AI, and choose what happens when they reach it: bill them for the extra use, or stop the action. If you resell an AI receptionist or chat agent under your own name, set a limit and an overage rule for your three busiest clients this week, and test what “stop” does to a phone line before choosing it.

HighLevel’s changelog entry, SaaS Usage Limits: Keep Client Usage in Check, and Get Paid When They Need More, puts the purpose plainly: “You can now set a usage limit for each of your SaaS clients and decide what happens when they reach it, for example bill them for the extra usage or stop the action.” It also says where the feature stops today: “Usage limits are available for Voice AI and Conversation AI today. Other products are not covered yet.”

Why one busy client can eat the margin

A resold AI receptionist is often sold at a flat monthly figure, while the work underneath is metered. A towing company that gets forty calls on a snowy night and a bookkeeper who gets four a week can sit on the same plan, and only one of them is profitable to serve.

Until now the fix was a conversation after the fact: an invoice line the client never agreed to, or an email asking them to move up a tier. Usage limits move it to the day the client signs.

What the Labs release does today

	Covered now	Announced, not yet released
Products	Voice AI and Conversation AI	Phone system, email, automations and more
What happens at the limit	Bill for the extra use, or stop the action	No change announced
Who sees usage	The client’s billing page, with color cues near the limit and reset dates; your Manage Client view, filtered by product or by share of limit used	Alerts at 50, 80 and 100 percent, in app and by email, to you and the client
Where limits are set	An optional step when you set up a new client with rebilling	The Enable Rebilling flow and the bulk action
Who can use it	Pro agencies, through Labs	No change announced

Two details in the notes change how you set it up:

• Only sub-account admins can view usage on the billing page and request a higher limit. If the office manager who would notice the warning is a regular user, they will never see it.
• Approving a request changes the limit only. It does not change what happens when the new limit is reached, so a client set to stop still stops, just later.

Bill the overage or stop the action

For a chat widget, stopping at the limit is a reasonable default: a visitor who cannot chat can still fill in the form or call. For an AI receptionist, stopping means missed calls on the busiest day of the month, which is the day the client remembers.

Our working rule for receptionist clients is billed overage, so a spike costs the client money rather than jobs. Stop belongs on trial accounts and on clients who told you in writing that a hard ceiling matters more than coverage.

The changelog does not say what a caller hears when Voice AI is stopped at the limit. Before choosing stop, set a tiny limit in a test sub-account, call until it trips, and listen. Then make sure that caller can still reach a person.

Turn heavy use into an upgrade, not an argument

“Request higher limit” appears only for clients who cannot upgrade their SaaS plan; clients who can upgrade see the upgrade option instead. So the plan you sold decides which conversation happens:

• Give every receptionist plan a bigger plan above it, with a higher limit, so a growing client meets an upgrade button rather than a wall.
• Keep the request path for your top tier, where a client asking for more becomes a one-off decision you approve, set a number on, or turn down with a reason.
• Answer requests the same day. Each one reaches you in Manage Client, on the agency dashboard and in the SaaS Configurator, with an in-app and email notification, and the client hears back when you decide.

Doing it yourself or handing it to a team

Usage limits are a setting. Tuning the agent so it does not burn minutes on wrong numbers, reading the usage view and answering requests is weekly work, and someone has to own it.

	Run it in-house	Hand fulfillment to Beyaoshy
Who builds and tunes the agent	Your team, with full control of every prompt and setting	One Beyaoshy team builds and supervises it; nothing is subcontracted
Whose brand the client sees	Yours	Still yours: agencies deliver our work under their own brand
Accounts and logins	Wherever you set them up	Set up in the client’s name, so nothing needs untangling if anyone leaves
Clinic and practice clients	Your own business associate agreements	We sign HIPAA business associate agreements with clinics and practices, the AI receptionist included
Before you commit	Your own time to learn it	A free consult and a written plan you keep whether or not you hire us

In-house suits an agency with someone who lives in HighLevel and enjoys tuning agents. If your edge is selling and keeping clients, the handoff column protects your evenings.

What to do this month: the new-client checklist

For every SaaS client you set up with Voice AI or Conversation AI from now on:

1. Turn on SaaS Usage Limits in Labs and add the limit during the new-client rebilling setup.
2. Set the limit a little above an expected normal month, with billed overage for receptionist clients unless they asked in writing for a hard stop.
3. Make the person who should watch usage a sub-account admin.
4. Put a higher plan above theirs, so the first time they need more it is an upgrade, not a request.
5. For clients already on rebilling, check where Labs lets you add a limit before promising one; the Enable Rebilling flow and the bulk action do not support it yet.
6. Write the limit and the overage rule into the client’s agreement, so the billing page never tells them something you did not.

Beyaoshy builds and supervises the AI receptionist for agencies that resell it under their own name. The partner model explains how the handoff works and what you send us to start.