Charlie AI- GHL Snapshot Overview

The primary function of the GHL snapshot is to activate or deactivate Charlie AI.

You can also view conversations within the platform, but the rest of the work happens on custom-built servers managed by Charlie’s team.

Go to Settings and select Custom Values.

There, you will see a custom value called Char API Key.

In other videos, you'll find instructions on how to enter the API key, but it's a simple process. The API key allows you to connect Charlie AI to your system.

Head over to Automation and locate the Charlie Voice folder.

Inside, you'll find one workflow designed to manage Charlie Voice. The setup is easy and user-friendly.

The key condition to check for is whether there is a Charlie Kill Switch Tag.

A custom webhook is required to complete the setup, ensuring Charlie’s voice feature works correctly.

If you use custom values to input information (like submitting an application), Charlie can grab and process this data.

Some customization may be required for your specific use case, but this option is available and can be adjusted to fit your needs.

Charlie includes fail-safe Do Not Disturb (DND) workflows for GHL to ensure that unsubscribe requests or keywords like “stop” are caught.

These workflows are backups and not directly related to Charlie AI, but they ensure that GHL deactivates Charlie when necessary by adding the Charlie Kill Switch Tag.

The Native Kill Switch automatically deactivates Charlie based on specific triggers, such as booking an appointment.

This feature is already set up, but you can customize it further to only deactivate Charlie for certain calendar events if needed.

In the automation setup, you do not need to enter additional numbers for custom values. The API key, as set in earlier steps, will automatically handle the connection for Charlie.

You can deploy up to four different instances of Charlie AI for various use cases.

For instance, you might have a VSSL opt-in Charlie. Each instance operates based on its specific triggers and conditions.

In each use case, there is typically a wait time that you can adjust based on your needs.

These adjustments can be done either manually or during pre-launch calls.

Each workflow checks for the Charlie Kill Switch Tag. If this tag is present, Charlie will be deactivated.

If no kill switch tag is found, the workflow proceeds, and Charlie continues to perform its designated actions.

Once integrated, select the appropriate use case for Charlie (e.g., SMS, Instagram, Facebook, etc.).

After integration, everything will function automatically based on the conditions and triggers you’ve set up.