GHL Snapshot Default Dashboard: Set It Once

Wait Action Enhancement: TikTok DM Replies  

What’s New:
Instead of continuing after a fixed delay, your workflow can pause until someone replies to your TikTok DM.

Where in GHL:
Found in Automation → Workflows using the Wait action after sending a TikTok DM.

Impact:
Your automation responds when someone actually joins the conversation, rather than after a timer runs out.

Recommended For:
Anyone using TikTok DMs to start conversations with potential customers.

---

India Recurring Mandate Support for Affiliate Indian Signup Pages  

What’s New:
Supports recurring payment mandates for Indian affiliates, helping subscriptions comply with local banking requirements.

Where in GHL:
Available on Affiliate Program signup pages for users in India.

Impact:
Creates a smoother signup experience while reducing payment failures for recurring subscriptions.

Recommended For:
Agencies, SaaS businesses, and affiliate programs onboarding customers in India.

---

Housecall Pro – More Workflow Actions & Triggers  

What’s New:
Adds new workflow triggers and actions for the Housecall Pro integration, giving you more ways to automate field service processes.

Where in GHL:
Inside Automation → Workflows when using the Housecall Pro integration.

Impact:
Expands automation possibilities between HighLevel and Housecall Pro, reducing manual work and improving operational efficiency.

Recommended For:
Home service businesses, field service companies, and agencies managing Housecall Pro clients.

---

Email Services Dashboard for Agencies  

What’s New:
Introduces a centralized dashboard where agencies can monitor email services across their accounts.

Where in GHL:
Found in the Agency View under the new Email Services Dashboard.

Impact:
Makes it easier to monitor email health, identify issues, and manage deliverability from one place.

Recommended For:
Agency owners, support teams, and admins managing multiple client email services.

---

Email Sequences Now Available in Beta Labs  

What’s New:
Introduces Email Sequences as a Beta Labs feature, providing another way to create structured email follow-up campaigns.

Where in GHL:
Enable it from Settings → Labs, then access Email Sequences after activation.

Impact:
Cuts down the time spent checking different areas just to see how your email services are performing.

Recommended For:
Marketers, agencies, coaches, and businesses running nurture campaigns or onboarding emails.

---

Group Your Contacts by Source in Dashboards & Reporting  

What’s New:
Lets you organize contact reports based on where your leads originated.

Where in GHL:
Available within Dashboards & Reporting when viewing contact analytics.

Impact:
Makes it easier to compare lead sources and identify which marketing channels are producing the best results.

Recommended For:
Marketing teams, agency owners, and businesses tracking campaign performance across multiple lead sources.

---

MMLite Adoption Banner in Conversations  

What’s New:
Displays a helpful banner inside Conversations to encourage users to adopt the new MMLite messaging experience.

Where in GHL:
Appears within the Conversations module for eligible accounts.

Impact:
Helps users discover and transition to MMLite while highlighting its benefits directly inside the messaging interface.

Recommended For:

Current HighLevel users exploring the latest messaging experience and teams preparing to migrate to MMLite. 

GHL has made the Snapshot loading process a little easier by adding a new default dashboard choice.

While choosing which dashboards to bring into a sub-account, you can now decide which one should open first for users.

Before this change, that usually meant finishing the Snapshot load, opening the sub-account, and adjusting the dashboard setting afterward.

Now, you can take care of it before the load is complete.

You can only have one default dashboard selected. If you change your mind and pick another one, GHL will switch the default to your new choice.

You don’t have to use the option either. If you leave it alone, the default dashboard already saved in the Snapshot will stay in place.

For agencies, this is mainly about cutting out another small setup task. And when you manage a lot of accounts, those small tasks add up fast.

This update cuts out a job that used to feel small until you had to do it over and over.

Before now, the default dashboard had to be changed inside each sub-account. So after loading a Snapshot, you still had to go into the destination account and sort out the dashboard setting manually.

That’s fine when you’re dealing with two or three accounts.

It’s a different story when you’re rolling out the same Snapshot across 50, 100, or 500 locations.

Now the default dashboard can be chosen during the Snapshot Load itself.

That means less jumping between accounts, fewer setup steps, and a better chance of every location starting with the same dashboard.

For agency teams that repeat the same setup across client accounts, this is a handy improvement.

It also helps keep the client experience more consistent. When someone opens the account, they’re more likely to land on the dashboard you actually intended them to use.

It’s not a massive feature on its own, but at scale, it can save a surprising amount of time.

The Snapshot Default Dashboard is set during the GoHighLevel Snapshot Load process. You’ll first choose the dashboards you want to include, then select which one should become the default inside the destination sub-account.

You’ll then complete the Snapshot Load and check the destination account to make sure the correct dashboard is being used. Here are the steps to set up and confirm the Snapshot Default Dashboard in GoHighLevel.

• Open the Destination Sub-Account.
• Start the Snapshot Load.
• Select the Dashboards to Copy.
• Set the Snapshot Default Dashboard.
• Complete the Snapshot Load.
• Confirm the load snapshot.

To start, make sure you are logged in to your GoHighLevel agency account.

• Start by opening the sub-account where you want to load the Snapshot.

1.1 Go to the Sub-Accounts area inside Agency View.

• This is where you can access and manage the locations connected to your GHL agency.

1.2 Select the destination sub-account.

• Choose the account where you want the Snapshot and dashboard settings to be applied.

• Use the sub-account actions to begin loading the Snapshot.

2.1 Open the Actions menu.

• Look for the available account-level actions in the sub-account details area.

2.2 Select Load Snapshot.

• This opens the Snapshot Load process for the destination sub-account.

• Choose the dashboard assets you want included in the Snapshot Load.

3.1 Open the Dashboard section in the asset selection area.

• This shows the dashboards available inside the selected Snapshot.

3.2 Select the dashboards you want to copy.

• Choose the dashboards you want available inside the destination sub-account.

• Choose the dashboard you want users to see first after the Snapshot is loaded.

4.1 Click Set as default on the dashboard you want to use.

• This marks that dashboard as the Snapshot Default Dashboard for the destination account.

• Review your selected assets and finish loading the Snapshot into the destination sub-account.

5.1 Continue through the Snapshot Load process.

• Follow the remaining steps shown in GHL until you reach the final confirmation.

• Open the destination account and confirm the correct dashboard is being used.

6.1 Type “CONFIRM” to the Snapshot Load.

• GoHighLevel will apply the selected Snapshot assets and settings to the destination sub-account.

The changelog confirms the new Set as default option, the one-default limit, and that the existing Snapshot default remains in place if you don’t make a new selection. It also recommends checking view permissions for users in the destination sub-accounts.

The Snapshot Default Dashboard update is simple to use, but a few setup checks can help you avoid problems when loading Snapshots across multiple sub-accounts.

Start with permissions. Before you make a dashboard the default, make sure the users inside the destination sub-account can actually view it. A default dashboard isn’t very useful if the right people can’t access it.

Clear naming helps more than you might think. When you’re working with multiple dashboards in one Snapshot, it makes the right default much easier to identify.

Before pushing the Snapshot across a big batch of sub-accounts, run a small test. A couple of accounts is usually enough to catch any setup issues before they spread.

Pay attention to the assets used inside your dashboard too. If a dashboard depends on other settings or data inside the Snapshot, make sure those assets are included in the load. Missing pieces can create a poor experience for users after the Snapshot is applied.

And don’t change the default just because the option is there. If the Snapshot already has the correct default dashboard, leave it alone and keep the existing setup.

This feature works best when you use it to keep things uniform. Pick the right dashboard, make sure it works, and use that same choice across the rest of your Snapshot loads.

For agencies, this update is really about cutting down on repeat work.

If you use the same Snapshot across a lot of GHL sub-accounts, changing the default dashboard after every load gets old fast.

Before this change, that could mean going into each account one by one just to make the same dashboard adjustment.

Now you can deal with it while the Snapshot is loading.

That makes the whole setup a bit cleaner, especially if your agency follows the same onboarding process for every client.

Let’s say you’re setting up 100 sub-accounts. Even a tiny manual step becomes a lot of extra clicking when you repeat it 100 times.

With this update, the default dashboard can be part of the Snapshot setup from the start.

That also helps keep accounts from drifting into slightly different setups.

For agencies offering a repeatable service or white-label SaaS package, that kind of consistency is useful.

Less cleanup. Less checking. Fewer chances for someone to miss a step.

This update takes one more small job off your onboarding checklist.

Before, loading the Snapshot was only part of the process. If the default dashboard needed to change, someone still had to open the destination account and fix it afterward.

Now you can make that choice while the Snapshot is loading.

This becomes a bigger deal once you’re setting up accounts in bulk. Doing one small job 50 times is still 50 jobs.

If every client should land on the same dashboard, you can now make that part of your regular Snapshot setup.

Just check that the right users have access to the dashboard you choose.

And if the Snapshot already has the right default, leave it alone. There’s no need to change something that’s already working.

It’s not a huge update, but it does make onboarding cleaner.

If you manage a lot of sub-accounts, this one is worth using.