Configure Phone Preferences in GoHighLevel — Sub-Account Setup

Managing phone preferences across multiple sub-accounts in GoHighLevel can feel overwhelming—especially when you're scaling an agency and need consistency without sacrificing flexibility. The good news? GoHighLevel's default phone preferences system automates the heavy lifting, letting you configure settings once and apply them across all new sub-accounts instantly.

In this guide, I'll walk you through exactly how to set up and customize phone preferences for sub-account creation, ensuring your team stays compliant, your calls route correctly, and your messaging limits align with your business needs. Whether you're managing five sub-accounts or fifty, these settings will save you hours of manual configuration.

Understanding Default Phone Preferences in GoHighLevel

Default phone preferences are settings you establish at the account or agency level that automatically apply to new sub-accounts when they're created. Think of them as a blueprint—once configured, every new sub-account inherits these settings without you having to manually set them up one by one.

This matters because phone configuration touches multiple critical functions: call routing, SMS compliance, call recording, message limits, and integration with your phone system. When you get these defaults right, new sub-accounts are immediately operational. When you get them wrong, you're either over-restricting your teams or exposing yourself to compliance risks.

The default preferences include:

• Automatic Phone System Linking — whether new sub-accounts automatically connect to the phone system
• A2P Registration Permissions — who can submit A2P registration and under what conditions
• Number Intelligence — caller ID and number lookup capabilities
• Messaging Limits — daily or monthly SMS/messaging caps per sub-account

How to Access and Configure Phone Preferences for Sub-Accounts

To set up default phone preferences for new sub-accounts, you'll navigate to your agency settings from the main GoHighLevel dashboard.

Step-by-step:

1. Log into your GoHighLevel agency account (the parent/master account, not a sub-account)
2. Click Settings in the bottom left corner
3. Select Sub-Accounts or Phone Settings (depending on your account version)
4. Look for Default Phone Preferences or Phone Defaults for New Sub-Accounts
5. Configure each setting according to your needs
6. Click Save

These preferences will now apply to every new sub-account created after this point. Existing sub-accounts keep their current settings unless you manually update them.

Automatic Phone Linking and What It Means for Your Workflow

The Automatically Link Phone System setting is pre-enabled by default, and for most agencies, you'll want to keep it that way.

When enabled, every new sub-account is automatically connected to GoHighLevel's phone system. This means:

• Sub-account users can send and receive SMS immediately
• Voice functionality (calls, voicemail, call recording) is accessible right away
• No separate manual activation step is needed
• Phone numbers can be purchased and assigned without delays

Disabling this setting would require you or your sub-account managers to manually enable the phone system for each account, which slows deployment and creates friction. Only disable it if you have a very specific reason—such as offering phone features only to premium-tier clients.

This is built into GoHighLevel. Try it free for 30 days →

A2P Registration Settings: Compliance and Sub-Account Control

A2P (Application-to-Person) registration is a compliance requirement imposed by carriers like Twilio, Bandwidth, and others. It confirms that you're using phone numbers for legitimate business communications, not spam or fraud.

GoHighLevel gives you control over whether sub-account users can submit A2P registration themselves or if they need approval from you (the agency).

Two key settings:

Allow Sub-Account Users to Submit A2P Registration (if Re-Billing is Disabled)

If you've disabled re-billing for sub-accounts (meaning they don't pay GoHighLevel directly), you can optionally allow them to submit their own A2P registration. This is helpful if you want to offload that administrative task but still maintain oversight.

Require Agency Approval for A2P Submissions

Keeping this enabled means you review and approve all A2P registrations before they're submitted to carriers. This is the safer default for agencies managing multiple sub-accounts, as it ensures compliance standards are met before submission.

Enabling Number Intelligence for Better Call Management

Number Intelligence (also called Caller ID Lookup or similar depending on your GoHighLevel version) enriches incoming call data by showing you information about who's calling before you answer.

When enabled, your team can see:

• Caller name and company (if available in public databases)
• Location information
• Call history in your GoHighLevel CRM
• Previous interactions with that contact

This feature improves call handling quality and reduces response time because your team knows who they're talking to before picking up. For lead generation and sales agencies, this is invaluable.

However, Number Intelligence may incur additional costs depending on your GoHighLevel plan tier. Check your pricing to see if it's included or add-on before enabling it as a default.

Setting and Adjusting Messaging Limits Across Your Team

Messaging limits cap how many SMS or other text-based messages a sub-account can send per day or per month. These exist to prevent accidental mass-sends, control costs, and manage carrier reputation.

How to set messaging limits:

1. In the Default Phone Preferences section, locate Messaging Limits
2. Choose your limit type: Daily or Monthly
3. Enter the number of messages allowed (e.g., 5,000 per day)
4. Decide if sub-accounts can request higher limits or if they're hard-capped
5. Save your configuration

Most agencies set daily limits between 1,000 and 10,000 messages depending on their client base. If a sub-account hits the limit, messages queue and send once the next period begins (or they're rejected, depending on your configuration).

You can always override these limits for individual sub-accounts after creation, so defaults don't have to be one-size-fits-all forever.

Best Practices for Phone Preference Configuration

1. Start Conservative, Then Adjust
Enable automatic phone linking and A2P oversight by default. You can always relax restrictions later for trusted sub-accounts. Starting strict prevents compliance headaches.

2. Set Messaging Limits Based on Your Smallest Client
If your smallest client only needs 500 messages per month, don't set a default of 10,000. Use conservative defaults and upgrade individual sub-accounts as needed.

3. Document Why Each Setting Exists
Write brief notes on your agency SOP explaining why you chose each default. When a sub-account owner asks why they can't do something, you'll have a clear answer.

4. Review Defaults Quarterly
As your agency grows and GoHighLevel adds features, revisit these settings. What made sense at 10 sub-accounts might need adjustment at 50.

5. Communicate Limits to Sub-Account Owners
Make it clear upfront what phone features and limits are included with their plan. This reduces support tickets and sets expectations early.

Configuring default phone preferences is one of the quickest wins for agencies scaling on GoHighLevel. A few minutes of setup now saves hours of repetitive configuration later, and it ensures every new sub-account launches with your compliance standards already baked in. Start with automatic phone linking and A2P oversight enabled, set realistic messaging limits, and adjust as your agency grows.