Skip to main content

​
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.
  1. First, we need to install the AVA application from the GHL marketplace. To do this, ensure that you are signed into your GHL Agency account/view. This is the higher level admin account from which you manage your agency and clients within GHL. Navigate to App Marketplace in the side-panel and then search for AVA. Click it, then click install and you will have the AVA GHL integration available.
  2. Navigate to ava.thinkrr.ai to sign into AVA and link your account. You will be redirected to the GHL Account Selector page. Please select and login with your Primary Account FIRST and NOT your Agency Account. Your account selector page drop-down menu will most likely have an Agency section, and a Sub-Account section. DO NOT select any account that appears within the Agency section.
    GHL Account Selector
    It is imperative that you sign into AVA with your Primary Account first and not your Agency Admin Account, otherwise the sign-in will fail and the integration will not work
  3. Follow the on-screen setup instructions in AVA which includes getting one free gift phone number from us! Alternatively, you have the option to import Twilio phone numbers as well. You can always add additional Twilio phone numbers later by navigating to Phone Numbers > Setup Phone Number.
    AVA Setup
  4. Please note that for Partner Plan Agencies, the integration of AVA with additional Sub-Accounts incurs a fee. In order to link a new Sub-Account with AVA, make sure that you are logged into the Sub-Accounts and grab the Location ID. Navigate to Settings > Business Profile and copy the Location ID from the General Information. Our support team will ask you for this information to assist you in adding a new Sub-Account.
    Location ID
Using AVA within GHL is as simple as grabbing the AVA feature from the Actions & Triggers sidebar within your GHL workflow builder. You can use AVA as both an Action and a Trigger dependent on your needs. Let’s take a look at that.
  1. First, you want to ensure you have AVA properly installed in your working account. Simply navigate to App Marketplace in the GHL side-panel and then click on Installed Apps and look for AVA Voice AI. If you do not find it, you can click on All Apps and search for AVA and install it.
    AVA Installation
  2. You can go into any Workflow you may have, or even create a new one, and add AVA into it. We will demo two workflows; one where AVA is an action, and the other where AVA is a trigger.
    1. AVA as an Action - We will create a simple workflow where an outbound call goes out to a contact who has just filled in a form.
      1. Go ahead and create your workflow with the Form Submitted trigger.
      2. Then, hit the “+” to add an action and scroll down until you find AVA Voice AI - Dynamic Outbound Call
      AVA Action
    2. AVA as a Trigger - We will create a simple workflow where an outbound call has occurred and we would like to collect the Call Summary and Sentiment of that call and add it as notes to the contact.
      1. Click “Add New Trigger” and scroll down until you find AVA Voice AI - Contact Called.
      AVA Trigger
      1. This trigger works just like any other GHL trigger and so we will add a filter on the Call Status and select only calls that have the status Meeting Booked.
      AVA Trigger
      1. We will then search in our database for the contact that was called using AVA’s response payload. We will use the contact phone number as the ID as it is a unique value between contacts.
      AVA Trigger
      1. Next, we will tag the contacts that were identified with a unique tag so that we can segment them appropriately. You can use any tag you want. We advise to make it super clear and descriptive.
      AVA Trigger
      1. Now comes the fun part; the conditional logic. We’ll introduce an if/else branch that checks through the tags of the contacts and if they have the tag we set, we can separate them in a bucket to extract the summary and sentiment, and if they don’t, we will do nothing for now.
      AVA Trigger
      1. And for the final step, we will just update the contact information with the AVA payload call summary and call sentiment. You can add the information to any contact field you want. It’s advisable to have dedicated contact fields for this information, like depicted in the image.
      AVA Trigger
      And that’s it! In a few easy steps, we were able to create 2 simple, yet incredibly powerful workflows that completement each other very well; if someone fills out a form, they immediately get called by AVA Voice AI, and from that call, key pieces of information are extracted, such as the call summary and the sentiment analysis, and appended to the contact in question.
      AVA Trigger
    There are many options which you can configure within AVA, allowing you to create incredibly detailed and tailored automations, and most of the fields can inherit data from previous steps.
    AVA Actions & Triggers are Premium Features and will not be accessible to users and accounts which do not have Premium Feature access within GHL

​
FAQs & Troubleshooting

​
General Questions

The AVA integration allows users to leverage AVA’s advanced AI voice capabilities directly within GHL. Users can link their accounts, set up workflows, and capture call data to create seamless automations and workflows.
Yes, AVA can integrate with both Primary (Admin) and Secondary (Client) Accounts. However, additional fees apply for integrating with additional Secondary Sub-Accounts under the Partner Plan.
Yes, you must have access to the Primary or Secondary Account you wish to integrate, and you’ll need the Location ID for setting up Secondary Sub-Accounts (for Partner Plan Agencies).

​
Installation and Setup

  • Navigate to the App Marketplace in the GHL side-panel.
  • Search for AVA Voice AI and click Install.
  • Follow the instructions to connect your GHL account to AVA.
The Location ID is a unique identifier for each GHL account. You can find it by navigating to Settings > Business Profile > General Information in GHL.
If you select the Agency Admin account instead of the Primary Account, the integration will fail. Always select the Primary Account first.

​
Workflow Integration

  • AVA as an Action: Initiate dynamic outbound calls directly from a workflow.
  • AVA as a Trigger: Capture call summaries, sentiment analysis, and meeting outcomes to use in automations or update contact records.
  • Create a workflow with your desired trigger (e.g., Form Submitted).
  • Add an action and select AVA Voice AI - Dynamic Outbound Call from the list.
  • Configure the action parameters to suit your needs.
  • Add a new trigger and select AVA Voice AI - Contact Called.
  • Filter by specific Call Status values, such as Meeting Booked.
  • Use the call data in conditional logic or update contact fields with details like call summary and sentiment.

​
Sub-Account Integration

Yes, AVA supports integration with Secondary Sub-Accounts. You’ll need the Location ID for each Sub-Account and may incur additional fees under the Partner Plan.
Yes, workflows and automations built with AVA can be shared via GHL snapshots, allowing easy replication across multiple Sub-Accounts.
Yes, each Sub-Account must be linked individually using its unique Location ID for Partner Plan Agencies.

​
Features and Limitations

AVA’s Actions & Triggers require Premium Feature access in GHL. Without this, you will not be able to use AVA in workflows.
Yes, AVA’s response payload can be used to update contact records with call summaries, sentiment analysis, and meeting outcomes in GHL workflows.
AVA is highly customizable within GHL, but its functionality depends on the parameters set in your workflows and the availability of Premium Features.
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.
⌘I