Every GoHighLevel number we could verify at the source, and the ones we could not

Most of the GoHighLevel figures circulating online come from affiliate reviews, and a good number of them are wrong. When we researched AI Employee pricing for an earlier post, the first pass returned prices from seven affiliate sites and not one of them was a primary source. Several disagreed with the vendor.

So this page is the other thing. Every number below was read off the publisher’s own page on 10 September 2026, and every row links to where we read it. Where a source would not load for us, the number is absent and the reason is written down, because a reference page that quietly fills gaps from memory is worse than one with holes in it.

HighLevel platform pricing

From HighLevel’s pricing page, read 10 September 2026.

Plan	Monthly	Sub-accounts	SaaS Mode
Starter	$97	3	Not included
Unlimited	$297	Unlimited	Not included
Agency Pro	$497	Unlimited	Included
Enterprise	Custom	Custom	Speak with their team

All four list unlimited contacts and unlimited users. Annual billing is offered at a ten-month price point, so Starter annual is published as $970 per year.

The line that catches people out is SaaS Mode. It appears only on Agency Pro at $497. An agency planning to rebill sub-accounts is on the $497 plan whatever its sub-account count says, and the $297 tier does not become a SaaS business by adding locations to it.

AI Employee is billed per location, not per agency

From HighLevel’s AI product pricing article, read 10 September 2026.

AI plan	Monthly, per enabled location
AI Employee Growth	$50
AI Employee Unlimited	$97

“Per enabled location” is the whole point and it is the detail most often dropped. This is not an agency-level add-on. Ten enabled sub-accounts on the Unlimited plan is $970 per month for the AI layer, on top of the platform subscription, and that is arithmetic on a published price rather than an estimate. Phone charges apply separately on top of the subscription.

AI pricing moves faster than platform pricing. Re-read the source before you quote it to a client.

A2P 10DLC throughput, for US SMS

From Twilio’s A2P 10DLC documentation, read 10 September 2026. This governs the SMS underneath GoHighLevel, so it applies whether or not you think of yourself as a Twilio customer.

Registration is two steps, a brand (who is sending) and a campaign (how recipients opt in, opt out and get help, plus what the messages are for). Twilio states that “anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC.”

Brand type	Daily SMS segments to T-Mobile	Approx. across US carriers
Sole Proprietor	1,000	~3,000
Low-Volume Standard	Up to 2,000	~6,000
Standard Brand	From 2,000 to unlimited	Varies by trust score

Unregistered 10DLC traffic is not simply blocked. Twilio’s wording is that senders “will receive additional carrier fees for sending unregistered traffic,” while registered senders get “lower message filtering and higher messaging throughput.” The practical failure mode is therefore a bill plus quiet filtering, not an error message, which is why it goes unnoticed for weeks.

Sole Proprietor at 1,000 segments a day to T-Mobile is the tier that surprises people. A segment is not a message. A long SMS is several segments, so a reminder campaign to a few hundred contacts can reach the ceiling in one send.

Gmail bulk sender requirements

From Google’s email sender guidelines, read 10 September 2026.

Threshold	Figure
Bulk sender definition	More than 5,000 messages per day to Gmail accounts
Spam rate, required	Below 0.3% in Postmaster Tools
Spam rate, recommended	Below 0.10%, never reaching 0.30%
In force since	1 February 2024

Senders above the threshold must set up SPF and DKIM for the sending domain plus DMARC, and marketing messages must support one-click unsubscribe with a clearly visible unsubscribe link in the body.

0.3% is roughly three complaints in a thousand delivered messages. That is a small number, and it is measured in Postmaster Tools rather than in your GoHighLevel dashboard, which is the usual reason a deliverability problem is invisible from inside the CRM.

What we could not verify, and did not quote

This section exists because it is the honest version of a statistics page. Three sources we wanted are cited across this site and pass a link check, but would not return readable content to us on 10 September 2026.

Source	What we wanted	Why it is absent
HBR, “The Short Life of Online Sales Leads”	The lead response multipliers this study is famous for	Paywalled. The figures are widely repeated second hand and we will not repeat a number we could not read
FCC ruling on AI-generated voices in robocalls	The exact ruling date and statutory language	Returned HTTP 403 to us. The ruling exists, the language is not quoted here
CTIA Messaging Principles and Best Practices	Stated consent and opt-out requirements	TLS certificate chain would not verify from our environment

The lead response study in particular is quoted constantly in this industry, usually as a bare multiplier with no year and no sample size attached. If you need it, buy it and read it. We would rather link to a paywall than pass on a number we have not seen.

Using these figures

Everything above is someone else’s published number, so quote the original rather than us. If this page is useful as the place they are collected and dated, link to it and we will keep the dates current.

Prices and thresholds change. Every figure carries the date we read it, and a figure without a date is not a figure you should put in a client proposal.