Every GoHighLevel sub-account starts life on a shared IP. GoHighLevel's LC – Email service is built on Mailgun, and by default your mail leaves through a pool of IPs shared with other GoHighLevel senders. GoHighLevel's own documentation is blunt about the trade-off: on shared infrastructure, other users' sending practices affect your reputation. For $59 per month at the agency level you can move a sub-account onto a dedicated IP and take back that control.
The reflex for a lot of agency owners is "dedicated IP = better deliverability, buy it." That is not always true. A dedicated IP is a tool with a specific shape, and for a large share of sub-accounts it will make placement worse, not better. This post is the decision framework: what the shared pool actually costs you, what a dedicated IP actually buys, and the volume threshold where the math flips.
What the shared pool actually is
LC – Email exists so agencies do not have to stand up their own Mailgun account or a third-party ESP. It is a fully hosted sending layer built into the platform. Under the hood, that layer routes most sub-accounts through shared IP pools.
Sharing an IP means sharing a reputation. Mailbox providers — Gmail, Microsoft, Yahoo — score the sending IP as one signal among several. When you are on a shared pool, that IP's score is the aggregate behaviour of everyone on it. Most of the time this is fine or even helpful: a well-managed pool has enough consistent, legitimate volume that no single small sender can move the number, and a brand-new sub-account gets to borrow the pool's established warmth instead of starting from zero.
The risk is the tail. If another sender on your pool imports a dirty list and triggers a blocklist, the listing is against the shared IP, and every sub-account on that IP inherits the degraded reputation until the platform resolves it. You did nothing wrong and you have no direct lever to fix it — you can only open a ticket and wait.
That is the real cost of shared sending: not day-to-day placement, but a correlated risk you do not control.
What a dedicated IP actually buys
A dedicated IP is exactly what it sounds like: an IP address used only by your sending. GoHighLevel prices it at $59 per month, charged at the agency level, and it changes three things.
You own the reputation — all of it. No bad neighbour can list your IP. The flip side is that there is no pool warmth to borrow either. The reputation is now entirely a function of your sending, good and bad.
Your sending ceiling goes up. GoHighLevel's shared-IP sending tops out well below the dedicated ceiling; a dedicated IP supports substantially higher daily volume once it is warmed. If a single sub-account is pushing serious volume, the shared limit itself becomes the reason to move.
You take on warm-up as a responsibility. A cold dedicated IP has no reputation at all, which to a mailbox provider looks more suspicious than a shared IP with history. GoHighLevel applies a ramp-up model to new sending — daily limits climb gradually over roughly the first week — and on a dedicated IP that ramp is load-bearing. Blast a cold dedicated IP with your normal volume on day one and you will land in spam faster than you ever did on the pool.
The volume threshold where it flips
Here is the decision in one line: a dedicated IP only works if the sub-account sends enough consistent volume to keep the IP warm.
Mailbox providers build IP reputation from a steady, predictable stream of engaged mail. A dedicated IP that sends a few hundred emails a week never accumulates enough signal to establish trust — it sits in a permanent cold state, and its placement is worse than it would have been on a warm shared pool. This is the single most common dedicated-IP mistake: an agency buys one for a low-volume client expecting an upgrade and gets a downgrade.
Rough guidance:
- Low, spiky, or seasonal volume → stay on the shared pool. The pool's borrowed warmth beats a perpetually cold dedicated IP.
- High, steady daily volume from one sub-account → a dedicated IP is worth it. You have enough throughput to keep it warm and enough at stake to want the correlated-risk insurance.
- Cold outreach specifically → be careful. High-volume cold sending is exactly the profile that gets IPs listed, and on a dedicated IP every consequence lands on you alone. That can be the point (isolation) or the trap (no pool to absorb variance) depending on how clean your lists are.
If you are not sure a sub-account clears the volume bar, it almost certainly does not. Stay shared.
How to decide, per sub-account
Run each sending sub-account through four questions:
- What is the steady daily volume? Not the peak — the floor. If the floor is low, a dedicated IP will starve.
- How clean is the list discipline? A dedicated IP concentrates the consequences of a bad list onto you. Only isolate sending you can keep clean. Verify lists before import — the bounce-rate breakdown covers the workflow.
- How correlated is your risk on the pool today? If you are repeatedly inheriting blocklist hits you did not cause, isolation is worth paying for even at moderate volume.
- Is authentication already correct? A dedicated IP does nothing for you if SPF, DKIM, and DMARC are misaligned. Fix authentication first — see the GoHighLevel SPF, DKIM, DMARC setup that lands — then decide on the IP.
Most agencies will find that the majority of their sub-accounts belong on the shared pool, and one or two high-volume clients justify a dedicated IP. That is the correct distribution, not a failure to upgrade.
Before you spend the $59, check what's actually broken
Deliverability problems get blamed on the shared IP far more often than the shared IP deserves. In practice most placement issues on GoHighLevel trace back to list quality and authentication, not the pool. A dedicated IP fixes neither — it just moves a clean-or-dirty reputation onto an address only you touch.
Before buying, confirm where the problem actually lives:
- Run the sending domain and IP through the blocklist checker separately. If the IP is clean, the pool is not your problem.
- Confirm SPF, DKIM, and DMARC with the DMARC checker. Misaligned auth degrades placement no matter which IP you send from.
- Look at your bounce rate. Above a few percent and the issue is the list, and a dedicated IP will simply give your dirty list a private address to burn.
What MailerMonk does at this layer
MailerMonk's agency reputation scorecard checks any sending domain and IP against Spamhaus ZEN, Barracuda BRBL, SpamCop SCBL, SORBS, and more, alongside SPF / DKIM / DMARC / MX status, in one view — so before you decide whether to isolate a sub-account you can see whether the IP is actually the thing dragging placement down. For agencies running many sub-accounts, the dashboard runs those checks daily so a shared-pool listing you did not cause surfaces in under an hour instead of from an angry client.
The dedicated-IP decision is a volume-and-cleanliness question, not a "more is better" one. Measure both before you spend.
Frequently asked questions
Does a dedicated IP guarantee better GoHighLevel deliverability?
No. A dedicated IP only improves placement if the sub-account sends enough steady volume to keep the IP warm and maintains clean list hygiene. A low-volume sub-account on a dedicated IP typically has worse placement than it would on a warm shared pool, because the IP never accumulates enough reputation signal. The IP is a tool for isolating and controlling reputation, not a deliverability upgrade on its own.
How much volume do I need to justify a dedicated IP on GoHighLevel?
Enough consistent daily volume to keep the IP warm — a steady stream, not occasional spikes. If a sub-account sends only a few hundred emails a week, it will not generate enough signal for a dedicated IP to establish trust. The exact number depends on the mix of mailbox providers you send to, but the principle is firm: low or spiky volume belongs on the shared pool.
If another sender gets our shared IP blocklisted, what can I do?
Confirm it first: check the IP and your domain separately on a blocklist checker. If only the IP is listed and your domain is clean, it is a platform-layer problem — open a GoHighLevel support ticket, because the shared infrastructure is theirs to resolve. While you wait, pausing high-volume sends avoids compounding the issue. Repeated inherited listings are themselves a reason to consider isolating that sub-account onto a dedicated IP.
Do I still need to warm up a dedicated IP?
Yes, and it is the step people skip. A cold dedicated IP has no reputation, which mailbox providers treat with more suspicion than a shared IP with history. GoHighLevel's ramp-up model increases daily limits gradually over roughly the first week; on a dedicated IP that ramp is essential. Sending full volume from a cold dedicated IP is one of the fastest ways to land in spam.