In the sources we checked on October 18, 2026 we found no lawsuit or FTC action that names HighLevel, the company behind GoHighLevel, as a defendant. The case people usually mean is a TCPA class action certified in March 2026 against a Las Vegas real estate agent who used GoHighLevel to send ringless voicemails; the platform was the tool, not a party. The difference matters, because HighLevel's terms put responsibility for consent and message content on the account holder. This page gives the facts we could verify, what we could not, and a short checklist if you send texts, calls or voicemails from GoHighLevel. It is information, not legal advice.
Has GoHighLevel (HighLevel) itself been sued?
We searched for lawsuits, class actions and FTC actions naming HighLevel and found none. That is a statement about one round of searches, not a guarantee. Court dockets are the authority: search CourtListener or PACER for "HighLevel", and the FTC's cases and proceedings list for the company name, before you rely on this page. The legal entity to search for is HighLevel LLC (see who owns GoHighLevel).
- May 3 and 16, 2023Prerecorded ringless voicemails to expired listings (1,983 calls at issue)
- Mar 13, 2026Court certifies the class against the agent in Garvey v. Gaitan
- Oct 18, 2026No lawsuit or FTC action naming HighLevel found in our searches
Source: TCPAWorld report, March 17, 2026; our searches
What is the GoHighLevel TCPA class action everyone mentions?
The GoHighLevel TCPA class action people mention is a case against an individual agent who used the software, Garvey v. Gaitan, in the U.S. District Court for the District of Nevada. According to the TCPAWorld report, the court certified a class on March 13, 2026 over ringless voicemails sent to expired real estate listings. The defendant is an individual agent. The report says she exported contact information into GoHighLevel and used it to send prerecorded ringless voicemails. It quotes the court noting that she had no documentation of the plaintiff's consent to prerecorded messages.
| Detail | What the report says |
|---|---|
| Court | U.S. District Court, District of Nevada |
| Defendant | An individual real estate agent, not HighLevel |
| What was sent | Prerecorded ringless voicemails to expired and withdrawn listings |
| Class | People who received prerecorded calls to cell numbers on May 3 and 16, 2023 |
| Size and exposure | 1,983 calls at issue; "just under $3MM" is the report author's estimate, not a court finding |
| Is HighLevel a party? | The report does not name it as one |
We read the TCPAWorld report, not the court order itself. If the details matter to you, read the order.
Who is responsible when a GoHighLevel user breaks texting or calling rules?
The GoHighLevel user is responsible when texting or calling rules are broken, not HighLevel. HighLevel's terms treat you as the sender of every message and make you solely responsible for its content, your consent records and the laws that apply. The platform gives you tools (A2P registration, opt-out handling, do-not-disturb settings on contacts) but it does not decide whether you had permission to contact someone. That is why the case above ended up against the agent who sent the voicemails and not against the software company.
A compliance checklist for anyone sending from GoHighLevel
- Keep proof of consent. Store where and when each person opted in, and what they agreed to. "We bought the list" is not consent.
- Do not use prerecorded voice or ringless voicemail without written consent. The case above turned on exactly that. Ask a lawyer before using these tools for cold outreach.
- Register for A2P 10DLC before texting US numbers, and send only what you registered. Our guide to A2P rejections lists the usual causes.
- Honour opt-outs everywhere. STOP must end texts across every workflow that can reach that person.
- Respect call and text hours for the recipient's time zone, and keep a do-not-call check in the workflow for outbound calling.
- Audit your workflows. We read every active workflow in our GoHighLevel audit and flag anything that can message people without a recorded opt-in.
Industries with extra rules (law firms, clinics, insurance) have their own pages: GoHighLevel for law firms, HIPAA and insurance agencies.
What we could not verify
- Whether any sealed, older or foreign proceedings name HighLevel. Our search covered public web results only.
- The current status of the Nevada case after March 2026.
- Any dollar figure for damages. The "just under $3MM" number is an estimate in a trade blog.
Frequently asked questions about GoHighLevel lawsuits
Is there a GoHighLevel lawsuit?
We found none naming HighLevel as a defendant. We found a TCPA class action certified in March 2026 against a GoHighLevel user, where the platform was the tool used to send the messages.
Can GoHighLevel get me sued?
The platform cannot, but how you use it can. Sending texts, calls or voicemails without documented consent is what creates TCPA exposure, whichever software sends them.
Is GoHighLevel responsible for my TCPA compliance?
No, HighLevel's terms put responsibility for content, consent and legal compliance on the account holder. Use its registration and opt-out tools, and keep your own records.
Are ringless voicemails allowed in GoHighLevel?
The tool may let you send them, but that does not make them lawful for your list. The March 2026 case concerned prerecorded ringless voicemails sent without documented consent. Get legal advice before using them.
Has the FTC taken action against HighLevel?
We found no FTC action naming HighLevel, the company behind GoHighLevel. The FTC's case database is the place to check; the link is above.
How do I avoid a TCPA problem with GoHighLevel?
Record opt-ins, register A2P, honour opt-outs, avoid prerecorded voice without written consent, and audit your workflows. We cover this in our account audit.
Where can I read about whether GoHighLevel is trustworthy?
Start with whether GoHighLevel is legit and the company profile with source grades.