GoHighLevel WhatsApp Messaging Limits: Setup and Traps

HighLevel just changed how WhatsApp messaging limits show up inside a sub-account, and the change matters more than a UI tweak. As of August 27, 2026, the Phone Numbers view no longer shows a per-number messaging limit at all — because per-number limits stopped being the real limit back in October 2025, when Meta moved WhatsApp quotas onto the business portfolio (WABA) itself. HighLevel’s UI is only now catching up to what Meta already changed.

If your agency runs more than one client’s WhatsApp number under a single business portfolio, this is not academic. The quota those numbers share is now visible in one place instead of hidden behind per-number displays that never told the real story, and understanding it is the difference between catching a throttled client before they notice and finding out when their appointment reminders stop sending.

What actually changed on August 27

Per HighLevel’s own changelog, two things shipped together. First, the per-number messaging limit column is gone from the Phone Numbers view, because individual numbers inside a portfolio no longer carry their own separate quota to display. Second, a new messaging limits panel appeared under WhatsApp Settings inside the sub-account, showing the true portfolio-level limit with tooltips explaining that the number is shared. The change is cosmetic in the sense that it doesn’t alter how Meta enforces limits — Meta already made that call in October 2025 — but it is the first time GoHighLevel’s own interface has told agencies the truth about where the ceiling actually sits.

How the shared quota works

A messaging limit, in Meta’s own definition, is the maximum number of unique WhatsApp user phone numbers a business can message outside of a customer service window within a moving 24-hour period. “Outside a customer service window” matters: replying to a customer who messaged you first inside the 24-hour service window doesn’t count against the limit. Broadcasts, reminders, and other business-initiated outreach do.

The part agencies miss is the word portfolio. Every business phone number connected under one WhatsApp Business Account draws from the same pool. HighLevel’s own documentation states it plainly: all business phone numbers within a portfolio share the same limit pool, so heavy usage by one number can impact the capacity available to others in the same portfolio. If you onboard five clients onto WhatsApp under one shared portfolio — a common setup for agencies that don’t want to manage five separate Meta Business verifications — all five are pulling from one shared ceiling, not five independent ones.

The trap: one client’s broadcast throttles everyone else

Here is the scenario that actually happens. Client A runs a Friday promotional broadcast to their full list. It’s business-initiated, it’s outside the service window, and it burns through a meaningful chunk of the portfolio’s 24-hour quota. Client B, sharing that same portfolio, has nothing to do with Client A’s campaign — but when Client B’s booking confirmations try to send that afternoon, the portfolio has already used its limit. Client B’s messages get blocked, not because of anything Client B did, but because of a campaign they never saw.

This is exactly the failure mode HighLevel’s changelog was written to head off. The old Phone Numbers view, by showing a number-level figure, implied each client had their own separate budget. They don’t, and they never did after October 2025 — the UI just hadn’t said so until now.

Quality rating and restricted status

Limits don’t only move up. HighLevel’s support documentation ties status changes directly to Meta’s quality rating system, which scores a number Green (high quality), Yellow (medium), or Red (low) based on recent recipient feedback — blocks, spam reports, and the reasons customers give for them.

• Flagged — the number’s quality rating dropped to Low and is on track to be downgraded to a lower tier. You cannot upgrade tiers during this seven-day window.
• After seven days, improved — status returns to Connected and the existing limit holds.
• After seven days, not improved — status returns to Connected but the messaging limit drops to the next tier down (100,000 to 10,000, for example).
• Restricted — triggered the moment the portfolio hits its messaging limit, regardless of quality rating. Outgoing business-initiated messages stop for 24 hours; customers who message you first can still get replies.

Because the pool is shared, one client’s low-quality sends — generic broadcast copy, poor list hygiene, content recipients report as spam — can drag the whole portfolio’s quality signal down, not just that client’s own standing.

How the tiers actually work — and where HighLevel’s own docs disagree

HighLevel maintains two separate support articles on this topic, and they don’t quite agree on the numbers. Treat the table below as directional and confirm the figure your own account shows in the new portfolio panel, since that live number is the one that governs you.

Getting to the first upgrade tier requires one of: completing Meta’s business verification, having a solution provider verify the business on your behalf, or sending 2,000 delivered messages to unique WhatsApp users outside service windows within a rolling 30-day period, using templates with a high quality rating. Past that point, increases happen automatically within roughly six hours once you’re sending high-quality messages across all business phone numbers and templates in the portfolio, and have used at least half of the current limit in the past seven days.

Work through a realistic case. A portfolio sitting at the 10,000-conversation tier is shared by four client sub-accounts. Three of them send low volumes of transactional confirmations — a few hundred messages a day between them. The fourth runs a Friday broadcast to an 8,000-contact list. That single broadcast alone can consume most of the day’s shared allowance, leaving the other three clients’ confirmations queued or restricted for the rest of that 24-hour window, even though none of them changed anything on their end. Multiply that by every Friday, and it becomes a recurring, predictable failure the agency could have avoided by placing the high-volume client on their own portfolio from the start.

New numbers inherit the portfolio’s limit — they don’t start fresh

This is the detail that trips up agencies onboarding a new client. HighLevel’s changelog states it directly: a new phone number instantly inherits the portfolio’s current limit. There is no grace period, no separate starter quota for the new number to build its own reputation on. If the portfolio is already sitting near its ceiling from existing clients’ volume, the number you just connected for a brand-new client walks straight into that constraint on day one — and if that new number sends low-quality content early, it can pull the shared quality rating down for every other number in the same portfolio.

What to actually do about it

Check the new panel under WhatsApp Settings for the real, current portfolio limit rather than trusting anything cached from the old per-number view. For clients with genuinely high send volume — frequent broadcasts, large lists, aggressive promotional cadence — put them on their own dedicated business portfolio instead of pooling them with lower-volume clients who have no visibility into, or control over, someone else’s campaign burning the shared ceiling. Reserve shared portfolios for clients whose WhatsApp usage is mostly transactional and low-volume, where the shared-pool risk is small. And treat quality rating as a portfolio-wide asset, not a per-client one: a single client running spammy broadcast copy is a risk to every sub-account sharing that number pool, so template quality and list hygiene deserve the same scrutiny you’d give a shared IP address for email.

Before onboarding the next client onto an existing shared portfolio, run through this short checklist:

• Open the new messaging limits panel and note the portfolio’s current tier and how much of it recent clients are already using.
• Ask what the incoming client’s expected send pattern looks like — transactional-only, or regular broadcast campaigns to a large list.
• If the answer is broadcast-heavy, price and provision a dedicated portfolio for that client rather than adding their number to the shared pool.
• Set a recurring internal check on quality rating for every number in a shared portfolio, since one number’s Yellow or Red rating can pull the whole portfolio toward a downgrade.
• Warn clients on a shared portfolio, in writing, that another business’s send volume can affect their own message delivery — it is a real limitation of the setup, not something the agency can fully insulate them from after the fact.

Frequently asked questions

See below.

Does replying to an inbound WhatsApp message count against the messaging limit?

No. The limit only applies to business-initiated messages sent outside the 24-hour customer service window. Replying to a customer who messaged you first, within that window, does not count against the portfolio's quota.

If I add a new phone number to my portfolio, does it get its own fresh messaging quota?

No. Per HighLevel's own changelog, a new phone number instantly inherits the portfolio's current limit rather than starting with a separate quota of its own. If the portfolio is already near its ceiling, the new number is constrained from day one.

Can one client's WhatsApp broadcast cause another client's messages to fail?

Yes, if they share a business portfolio. All numbers under one portfolio draw from the same 24-hour message pool, so heavy business-initiated sending by one number can leave less capacity available to every other number in that portfolio.

What happens when a portfolio's messaging limit is reached?

The affected numbers move to a Restricted status. Outgoing business-initiated messages stop for 24 hours, though customers who message the business first can still receive replies during that window.

Where do I see my portfolio's actual current messaging limit in GoHighLevel?

Under WhatsApp Settings inside the sub-account, in the messaging limits panel HighLevel added on August 27, 2026. The old per-number column on the Phone Numbers view has been removed because it no longer reflected how the quota actually works.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.