Integrating Multiple Calendars with AI Goals

Understanding Calendar ID Configurations in GHL

While it may appear that there’s only one Calendar ID Custom VALUE, it’s important to understand that multiple calendars can still be managed. The key element used by the AI is not the Custom VALUE, but rather the Custom FIELD. These Custom Fields dynamically interact with the system on the contact level.

Key Definitions:

Custom VALUES: These are assigned based on the location or subaccount details.

Custom FIELDS: These are dynamic and operate at the contact level.

Practical Example:

Imagine a dental clinic offering four different services:

Whitening

Smile Makeover

Bridges

Check-up

Each service is linked to its own calendar.

Form Submission Scenario:

When a contact submits a form, it is straightforward to assign the correct calendar:

The form submission indicates the service the contact is interested in.

You then update the Calendar ID Custom FIELD in the workflow that is triggered post-submission.

For example:
If they come in through a form, it is very easy, because you already know what service they are interested in.

Here, the Calendar ID Custom FIELD remains constant (Calendar ID) but alters based on the service selected when the form is filled out. This scenario benefits from prior knowledge of the contact’s service interest.

Inbound Contact Scenario:

When a contact reaches out directly without specifying their service interest, the process involves:

1. Implementing AI  GOALS  to inquire about the service of interest.
2. Setting up TAG Goals for each service with a specific tag and a brief goal description.
3. Ensuring these tags are configured in GHL.
4. Triggering the workflow with a new trigger when a tag is added.

This approach ensures that even if the service interest isn’t known before the conversation, the appropriate tag and corresponding calendar ID will be assigned once the bot identifies the service interest.

AI goals allow your AI to inquire about the service a customer is interested in. Once the service is identified, you can utilize these goals to initiate a specific tag related to that service.

Steps to Implement:

1. Create TAG Goals: Set up a unique tag for each service, accompanied by a brief goal description.
2. Configure Tags in GHL: Ensure these specific service tags are created within GHL.
3. Workflow Integration: Once a tag is added, it triggers the existing workflow, now enhanced with an additional trigger: ‘Tag Added’.

4. This process ensures that even without prior knowledge of a customer’s service preference, the system can dynamically assign the correct tag and update the calendar ID accordingly once the service interest is determined by the bot.”