Skip to main content

​
Overview

The Dynamic Outbound Call is a premium action available inside GoHighLevel (GHL) and NIKO that lets you trigger outbound voice calls using AVA. Once you’ve connected AVA to your GHL/NIKO account, you can use this action in any workflow to launch an AI-powered call that’s fully personalized to your use case. This action is ideal for instantly reaching out to leads who complete a form, opt into a campaign, or enter a particular stage in your funnel. Instead of relying on manual follow-up, AVA can call the contact, deliver your message, ask questions, and even schedule meetings — all automatically. Let’s walk through how to use and configure the Dynamic Outbound Call action step by step.

​
Adding the Action to a Workflow

To get started, open GHL or NIKO and go to the Workflows section. Create a new workflow from scratch, or edit an existing one where you’d like to add the call. Once you’re inside the workflow builder:
  • Click the + icon to add a new step
  • Scroll down to the AVA Voice AI section
  • Select Dynamic Outbound Call
This adds the action to your workflow. Now you’re ready to configure it.

​
Configuring the Call

The configuration panel for the Dynamic Outbound Call contains several fields that define how the call works, who it targets, and what happens during the conversation.

​
Contact Details

You’ll begin by entering the contact’s information. Do not hardcode static values — use the tag icon to insert dynamic GHL variables like {{contact.first_name}}, {{contact.phone_raw}}, and {{contact.email}}. This allows the workflow to call different contacts with their personalized details pulled from the CRM.
  • Name – Use the contact’s full name (e.g. {{contact.full_name}})
  • Email – Useful for context but not required by AVA
  • Phone Number – Always use the Raw Phone Number field (e.g. {{contact.phone_raw}})
  • Time Zone – Optional, but highly recommended. If left blank, AVA will default to your account’s main time zone.
These values help AVA personalize the call and determine when to place it.

​
AI Agent Settings

Next, choose the voice and identity of your AI caller.
  • AI Assistant – This is the voice that AVA will use. The dropdown pulls from voices already available in your AVA account.
  • Agent Name – This is what the AI will call itself during the call. It should be a short label or name (e.g. “Sarah” or “Receptionist”). Do not enter a full introduction or sentence — the agent will handle its own phrasing based on scenario logic.
⚠️ Voice previews are not available inside GHL. If you’d like to hear how each voice sounds, log in to your AVA dashboard and test them there.

​
Customer Insight (Optional)

This field lets you pass additional context to the AI, such as:
  • A summary of past interactions
  • Details about the lead’s business
  • Key talking points or objections
While not required, this can help the AI tailor its responses more effectively.

​
Caller Number

Use the dropdown to select the outbound number AVA will use when placing the call. These are phone numbers already connected to your AVA account.
If you don’t see any numbers listed, go back into the AVA platform and add at least one phone number. Then return here and try again.
The number you select here is what your contact will see as the caller ID.

​
Scenario Selection

Now choose the Scenario that defines the purpose and content of the call. Each AVA scenario comes with its own set of fields and logic, such as:
  • Opening scripts
  • Meeting pitch and value proposition
  • Location fields
  • Scheduling options
For example, if you’re running appointment outreach, you might select the Standard Scheduler scenario. This gives you fields for calendar links, introductions, and call reason.

​
Filling in Scenario-Specific Fields

Once you’ve selected a scenario, you’ll be asked to fill in its required fields. These vary based on the scenario you chose, but usually include:
  • Greeting – The first thing your AI will say on the call
  • Introduction – How the agent introduces themselves, the company, and their reason for calling
  • Representative Name / Business Info – These values help the AI build credibility and clarity
  • Closing Statement – A friendly sign-off to end the call on a good note
  • Reason for Appointment – Why you want the contact to book time with you (e.g. consultation, product demo)
Make sure each field is clearly written and conversational — AVA uses these inputs as guides, not as verbatim scripts. The AI will rephrase or blend fields to deliver the message naturally based on the context of the call.

​
Calendar Configuration

If your scenario involves booking a meeting, you’ll need to link a calendar.
  1. In the Calendar field, paste the Calendar ID from GHL
  2. To find this ID:
    • Go to Calendars in GHL
    • Click the three dots on your chosen calendar
    • Select Settings
    • Copy the ID listed under the calendar name
📌 Double-check that your calendar is active. If it’s paused, click the three-dot menu and reactivate it before using it here.

​
Voicemail Message

Even if you don’t plan to use voicemail, this field cannot be left blank.
  • If you want AVA to leave a voicemail, write out the message you want delivered
  • If you don’t want to use voicemail, simply enter NA
This is necessary to avoid errors when publishing your workflow.

​
Finalizing and Testing

Once you’ve filled in all fields:
  1. Save your workflow
  2. Publish the automation
  3. Test it using a contact with valid phone details
A good first test is to trigger the workflow manually using a test contact who meets all the criteria. This will help you confirm the call is placed, the agent speaks correctly, and any meetings are booked as expected.

​
FAQs & Troubleshooting

​
General Questions

Dynamic Outbound Call lets you trigger full voice calls from a workflow using a selected AVA scenario. It’s ideal for automating outreach, follow-ups, appointment scheduling, and lead qualification.
Inside the action step, you’ll choose the agent’s voice (pulled from AVA) and assign them a name. If you want to preview the voices, you’ll need to do that inside your AVA account — GHL doesn’t support in-platform voice previews.

​
Configuration

That means you haven’t yet added a phone number in AVA. Go to the Numbers section in your AVA dashboard, add one or more outbound numbers, and return to GHL to refresh the list.
Use the ID from the calendar you’ve already created inside GHL. Open your calendar, click the three-dot menu, choose Settings, and copy the ID shown under the name. Make sure it’s set to “Active.”
Yes. Even if you don’t want AVA to leave a voicemail, the field must contain something (like NA) or your workflow won’t publish.

​
Usage and Results

AVA initiates the call almost immediately after the workflow reaches the action step. Timing may vary slightly based on time zone handling and agent load, but it’s near-instant for most setups.
All call results — transcript, sentiment, call status, recording URL — are pushed back to AVA and visible inside the Call History section. You can also use the Contact Called trigger in follow-up workflows to act on the results.
Absolutely. Just add it wherever you need AVA to place a call — as long as your scenario, calendar, and number are still valid, the action will work across any automation.
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