Notification Settings

Notification settings is a two-layer configuration: GHL’s internal notification preferences and the client’s phone-level push notification permissions. Inside GHL, you navigate to Settings, then My Staff, then edit the user’s notification preferences. On the phone, you confirm that the GHL mobile app has permission to send push notifications. Both layers must be configured correctly for the client to receive real-time alerts about new leads, messages, missed calls, and appointments.

Why This Matters

You can build the most sophisticated lead capture system in the world, and it is worthless if nobody sees the leads when they come in. Speed to lead is the single most important metric in local business marketing. Studies consistently show that responding to a lead within five minutes versus 30 minutes can increase conversion rates by ten times or more. The difference between five minutes and 30 minutes is often whether the business owner’s phone buzzed.

Notification settings are the last mile of your automation. The workflow fires. The contact enters the pipeline. The conversation appears in the inbox. But if the client’s phone does not make a sound, none of it matters. The lead sits. The prospect moves on. And the client, who is paying you for a lead generation system, never knew the lead existed until they opened the app three hours later.

This step is especially critical because there are two independent systems that must agree. GHL has its own notification settings that control which events trigger alerts. The phone’s operating system has its own permission system that controls whether any app can send notifications at all. If either one is misconfigured, the client gets silence. You need to check both.

How to Think About It

Start with the GHL side. Navigate to Settings, then My Staff. Find the client’s user account (or the user they designated as the lead responder during the Team Members step). Edit their profile and open the notification preferences. Turn on notifications for the events that matter: new conversations, missed calls, new opportunities, appointment bookings, and any other triggers relevant to the client’s package.

Be selective, not exhaustive. Turning on every notification type results in notification fatigue. The client’s phone buzzes every three minutes and they start ignoring all notifications. Focus on the high-value alerts: new leads, missed calls, and direct messages. Leave administrative notifications (workflow completions, system updates) turned off for the client.

Then switch to the phone side. Have the client open their phone’s settings and navigate to the GHL app’s notification permissions. On iOS, this is Settings, then Notifications, then the GHL app. On Android, it is Settings, then Apps, then the GHL app, then Notifications. Confirm that notifications are allowed, that sounds are enabled, and that the app can show notifications on the lock screen. Many phones have “Do Not Disturb” modes or “Focus” profiles that suppress notifications from certain apps. If the client uses these features, they may need to add the GHL app as an exception.

Common Mistakes

Only configuring one layer. The most common failure. You set up GHL notifications perfectly, but the phone’s OS is blocking push notifications from the app. Or the phone allows notifications, but GHL’s settings have everything turned off. Both layers must be verified.

Turning on too many notification types. A client who gets 50 notifications a day stops looking at any of them. Curate the notification types. New inbound conversations and missed calls are almost always the most important. Everything else should be evaluated based on the client’s role and what they actually need to respond to.

Skipping this step for team members. If you added Team Members earlier in the call, they need notification settings configured too. The receptionist who is supposed to respond to leads needs their own GHL notification preferences and their own phone-level permissions set up. Either do it on the call or provide clear instructions for the client to do it with their team.

Not testing notifications after configuration. The only way to confirm notifications work is to trigger one. Send a test message to the sub-account’s phone number or create a test conversation. The client’s phone should buzz within seconds. If it does not, troubleshoot immediately. Do not assume it will work.

Forgetting about email notifications. GHL can also send notification emails for certain events. Some clients prefer email alerts in addition to push notifications. Ask whether they want email notifications and configure accordingly. For some clients, especially those who live in their email inbox, this is a more reliable channel than push notifications.

Tools Involved

Notification configuration happens in two places: the GHL sub-account settings under My Staff (for GHL-level preferences) and the client’s phone settings (for OS-level permissions). The GHL Mobile App must already be installed for push notifications to work. Notification triggers are often connected to workflows that route leads and conversations. For agencies managing multiple sub-accounts, GHL MCP Users API can programmatically adjust notification preferences at scale.

Where This Fits

Notification settings sit at sequence position 14, near the end of the quick start call. They depend on the Mobile App being installed at position 12, because push notifications require the app. This step runs alongside the Integrations Sweep and Onboarding Form Preview. Notification configuration is one of the last technical steps before the call wraps up. Once notifications are confirmed working, the client is equipped to receive real-time alerts from the moment your automations go live.

Common Questions

What if the client has an older phone with limited notification capabilities? Most modern smartphones handle push notifications without issue. If the client has a very old device, email notifications may be a more reliable backup. Configure GHL to send email alerts for critical events and recommend they check the app manually at regular intervals.

Can notifications be customized per event type? Yes. GHL’s notification settings allow granular control. You can enable push notifications for new conversations but disable them for appointment confirmations, for example. Walk through the options with the client and decide together which events warrant real-time alerts versus which can be checked in the app at their convenience.

What about notifications during off-hours? This depends on the client’s preference and business model. Some businesses want 24/7 notification. Others prefer silence after business hours. GHL does not have built-in scheduling for notification suppression, so this is managed at the phone level using “Do Not Disturb” schedules or focus modes. Help the client configure their phone’s DND settings if they want off-hours silence without missing urgent alerts during business hours.