If you're running an agency on GoHighLevel, you know how critical communication is. Team members need to stay informed about snapshot outcomes—but not drowning in email notifications. That's where Snapshot Notification Preferences come in.
This powerful feature gives Agency Admins precise control over who gets notified, when they get notified, and what information they receive. Whether you're managing one sub-account or dozens, snapshot notifications eliminate manual status checks and keep your team aligned without inbox chaos.
In this guide, I'll walk you through everything you need to know about configuring snapshot notifications in GoHighLevel—from setup to best practices that actually work for growing agencies. And if you haven't tried GoHighLevel yet, grab your free 30-day trial here to follow along hands-on.
What Are Snapshot Notification Preferences?
Snapshot Notification Preferences is a feature in GoHighLevel that empowers Agency Admins with enhanced control over email notifications triggered by snapshot pushes. When you push snapshots to sub-accounts—whether it's funnels, automations, campaigns, or settings—the system automatically notifies relevant team members about the outcome.
Instead of random notifications or complete silence, you get granular control. You decide:
- Which team members receive notifications
- What type of snapshot events trigger notifications (success, failure, pending)
- How notifications are grouped and delivered
- Whether notifications are sent in real-time or batched
This isn't just a convenience feature—it's a operational necessity for agencies managing multiple client accounts. Without it, you either miss critical failures or suffer from notification fatigue.
Why Your Agency Needs Snapshot Notifications
Here's the reality: snapshots are one of the most powerful features in GoHighLevel for agencies. They let you clone entire campaigns, funnels, and workflows between accounts in seconds. But when something goes wrong—or even when something succeeds—your team needs to know immediately.
Consider this scenario: You push a snapshot to 15 client accounts. Without notification preferences configured, you either:
- Get overwhelmed with 15 individual emails about each push, making it impossible to scan important information quickly
- Miss critical failures because you're not actively monitoring the system
- Waste time manually checking the status of each snapshot push
Snapshot Notification Preferences solve this by:
- Grouping notifications intelligently—rolling notifications compile multiple pushes into digestible updates
- Alerting the right people—only admins or designated team members get notified, not everyone
- Reducing manual work—your team always knows status without checking the UI constantly
- Improving response time—when failures happen, the right person is notified immediately
How to Access and Configure Snapshot Notifications
Setting up snapshot notification preferences is straightforward if you know where to look. Here's the step-by-step process:
Step 1: Log into Your Agency Account
You must be logged in as an Agency Admin to access these settings. If you're a sub-account user, you won't see these options.
Step 2: Navigate to Settings
From the main dashboard, click on your profile icon or settings menu. Look for the "Agency Settings" or "Preferences" section.
Step 3: Find Notification Preferences
Within Settings, locate "Snapshot Notification Preferences" or "Email Notification Settings." This section controls all snapshot-related email alerts.
Step 4: Configure Your Preferences
You'll see options for:
- Notification Type: Choose between real-time, rolling (batched), or disabled
- Recipient List: Select which team members receive these notifications
- Event Types: Toggle notifications for successful pushes, failed pushes, or both
- Frequency: Set how often batched notifications are sent (if using rolling notifications)
Step 5: Save Your Settings
Click "Save" to apply your configuration. Changes take effect immediately for all future snapshot pushes.
💡 Pro Tip
Start with rolling notifications enabled for success events only. This keeps your team informed without notification overload. Then, enable failure notifications immediately—you want critical issues noticed right away.
This is built into GoHighLevel. Try it free for 30 days →
Setting Up Rolling Notifications for Multiple Sub-Accounts
Rolling notifications are a game-changer when you're managing dozens of sub-accounts. Instead of receiving a separate email notification for every location or client account that receives a snapshot, GoHighLevel groups updates into consolidated notifications.
Here's how they work:
Traditional Approach (Without Rolling Notifications):
- You push a snapshot to 20 client accounts
- You receive 20 separate emails—one for each account
- Your inbox is flooded; important information gets buried
Rolling Notification Approach:
- You push a snapshot to 20 client accounts
- GoHighLevel groups the results and sends 1–3 batched notifications
- You get a clean summary: "15 successful, 5 pending review"
To enable rolling notifications, toggle the "Rolling Notifications" option in your Snapshot Notification Preferences. You can set the roll-up frequency (typically 15, 30, or 60 minutes) to batch updates at the interval that works for your team.
Best Practices for Reducing Notification Clutter
Even with snapshot notifications enabled, you need a strategy to avoid inbox overload. Here are the practices that work best for agencies:
1. Segment Your Team by Role
Not every team member needs every notification. Create different notification preferences for:
- Admins/Managers: Get all notifications (success and failure)
- Specialists: Get only failure notifications for snapshots they own
- Junior Staff: Get weekly summaries instead of real-time alerts
2. Use Rolling Notifications for Non-Critical Updates
Successful snapshots can wait 15–30 minutes to be batched. Failed snapshots should still trigger immediate alerts.
3. Create a Dedicated Notification Email
Set up a shared team email (like [email protected]) instead of sending to individual inboxes. This keeps snapshot alerts centralized and prevents personal email fatigue.
4. Review and Prune Regularly
Every month, audit who's actually reading these notifications. Remove team members from the list if they're not acting on the information.
5. Document Your Notification Protocol
Create a simple one-page guide showing your team what different notifications mean and what action (if any) they should take.
Common Snapshot Notification Scenarios
Scenario 1: You're Deploying a New Campaign to Multiple Clients
Push the snapshot to all accounts, enable rolling notifications for success events, and set failure alerts to trigger immediately. Your team gets one clean summary email showing which accounts received the campaign successfully and which need manual intervention.
Scenario 2: A Client Experiences a Failed Snapshot
With notifications enabled, your team is alerted within seconds. They can investigate the issue—usually a missing integration or custom field mismatch—and resubmit the snapshot without the client even knowing something went wrong.
Scenario 3: You're Onboarding a New Sub-Account
Use snapshots to clone your entire agency's templates and workflows to the new account. Rolling notifications keep your onboarding team in sync without spamming their inbox during the process.
The key in all scenarios: your team stays informed and responsive without manual work.