​
Overview

Linking your account, setting up actions and triggers, and capturing all the call data for your own workflows and automations has never been so easy, and we’ll show you everything you need to know to get started, right here. Let’s get started.

​
Terms & Definitions

  • GoHighLevel - (also referred to as GHL or just HL) defines a multi-purpose CRM system that allows users to organize their contacts and contact history, as well as define business logic via automations and workflows, but most importantly, define a custom version of the software, including tailored automations, workflows, contact management/customer journey, and share all of this to their clients/sub-accounts via “snapshot”, allowing for highly specific, highly tailored, and easily shareable GHL experiences.
  • Snapshot - defines an “instance” of GHL with all current configurations for the purposes of creating specific and customized business logic, which can then be shared to sub-accounts and installed in their view while maintaining read/write permissions and keeping a clear separation between an Agency Admin and all other sub-accounts (typically clients).
  • Primary Account - (a.k.a Admin Account) defines the main operating account for an Agency/Business. This is the Admin account that typically reserves all read/write permissions and manages all clients that the Agency/Business supports.
  • Secondary Account - (a.k.a Secondary Sub-account or Client Account) defines the account that represents the client of the Agency/Business. These accounts are typically linked to, visible to, and accessible by only the Primary Account. For example, it is common for an Agency/Business to operate and manage their own business in the Primary Account, create workflows and automations to install into Secondary Accounts, and provide troubleshooting and support by logging into their Client Account.
  • Location ID - defines the unique character string associated with a particular account in GHL, regardless of whether it is a Primary Account or Secondary Account. It is necessary for successfully connecting a GHL Secondary Sub-Account with AVA functionality for Partner Plan Agencies, and can be found by navigating to Settings > Business Profile > General Information.
  • Calendar ID - defines the unique character string associated with a particular GHL native calendar. This Calendar ID is necessary for successfully connecting a calendar in AVA, enabling your AI Agents to check for available time slots in your calendar and create bookings .

​
Details

AVA Voice AI was built to fit natively within GHL to afford maximum ease of use and advanced AI voice functionality for all GHL users. AVA can be added from the marketplace and easily inserted into your automations and workflows without having to make any modifications to your business logical. This is voice AI made simple, and built to be plug & play for any business. Let’s take a look at how this works.

​
FAQs & Troubleshooting

​
General Questions

​
Installation and Setup

​
Workflow Integration

​
Sub-Account Integration

​
Features and Limitations

For additional questions or guidance, try using our Virtual Support Agent! Available 24/7 to help resolve most issues quickly at thinkrr.ai/support.

If you still need assistance, visit our support site at help.thinkrr.ai and submit a Ticket or contact our team directly at hello@thinkrr.ai.