Skip to main content

Overview

AVA Voice AI connects directly with GoHighLevel (GHL) to let you automate phone-based workflows using intelligent voice agents. This integration works through Smart Actions and Smart Triggers that you can use inside GHL’s automation builder to launch calls, respond to outcomes, and update your CRM — all without touching the phone yourself. Whether you’re sending outbound calls to fresh leads or processing incoming calls through an AI receptionist, AVA’s tools make it easy to plug voice automation into your existing GHL setup. The goal is simple: reduce manual follow-ups, capture every call detail, and ensure no contact slips through the cracks.

How It Works

In GHL, every workflow starts with a Trigger — a real-time event that kicks things off. Once a trigger fires, the system executes one or more Actions — tasks like sending a text, tagging a contact, or launching an AVA call. AVA introduces its own unique set of Triggers and Actions, designed specifically for AI phone interactions. These aren’t generic automations — they’re tightly connected to AVA’s outbound and inbound calling systems, which means they can respond to call outcomes, deliver pre-scripted messages, and route data directly into your workflows. If you’re using AVA with GHL or NIKO (our custom version of GHL for business users), you’ll be working with three core workflow tools: two Triggers and one premium Action.
Note: AVA now includes two new and improved workflow tools — AI Voice Studio Smart Call and AI Voice Studio Smart Trigger.
These are direct upgrades to Dynamic Outbound Call and Contact Called, offering tighter integration with AVA projects and campaign-level automation.
If you’re a new user building workflows, we recommend starting with the new smart call and smart trigger instead of the older versions.

Available AVA Smart Actions & Triggers

Actions

Triggers


AVA as an Action

Actions are about doing. When a workflow is triggered, you can tell AVA to launch a phone call to the contact. These actions make it possible to automate outbound calls directly from workflows in GoHighLevel or NIKO.

1. AI Voice Studio Smart Call

The AI Voice Studio Smart Call is a premium workflow action that lets you launch fully configured outbound calls using your existing AVA projects and campaigns.
It’s designed to give you advanced control and ensure every call follows the same parameters you’ve defined inside AVA — from the AI agent’s voice and language to its greeting, objectives, and tone.
Unlike the older Dynamic Outbound Call, which required setting call details manually in GHL, Smart Call connects directly to your campaign-level configuration in AVA.
That means every Smart Call uses the exact voice, accent, and call behavior already defined in the campaign — no extra setup required.
When the workflow runs:
  • AVA retrieves your selected Project and Campaign from the dropdown inside GHL.
  • It automatically syncs contact data such as name, email, and phone number.
  • The AI performs the call using your campaign’s configuration and returns full post-call data to GHL.
Use Smart Call when:
  • You want campaign-level accuracy and multilingual voice options.
  • You’re running multiple outbound campaigns with different AI agents.
  • You want tighter synchronization between AVA’s reporting and GHL automations.

2. Dynamic Outbound Call

The Dynamic Outbound Call is the legacy action that still allows you to trigger outbound calls from a workflow using any AVA Scenario you’ve set up (like a scheduler, follow-up, or data collection script).
It’s a flexible tool for launching one-off or simplified outbound calls directly from automations.
When a workflow reaches this action:
  • AVA calls the contact using the defined scenario and agent voice.
  • You can personalize the agent’s name, tone, and introduction, and set a voicemail message if needed.
  • Key fields include the outbound number (from your AVA account), your calendar ID (for scheduling), and optional Customer Insight text for context.
  • If the contact’s time zone isn’t known, AVA defaults to your account’s primary time zone.
Once the call finishes, AVA pushes all call results — transcript, sentiment, appointment status, and recording — back into GHL, where you can use them for follow-up workflows. While it remains supported, new workflows should use AI Voice Studio Smart Call instead.
Smart Call handles configuration automatically and syncs directly to campaigns for better reporting and cleaner automation.

AVA as a Trigger

Triggers are about listening. When something happens — a call ends, an agent receives a ring — AVA can notify your workflow and pass along important data.
You can then automate next steps based on call outcomes, contact information, or campaign performance.

1. AI Voice Studio Smart Trigger

The AI Voice Studio Smart Trigger is a premium workflow trigger that activates whenever a Smart Call from AVA completes.
It’s designed for campaign-based workflows, giving you much greater precision than the older Contact Called trigger.
While Contact Called reacts to any completed AVA call, the Smart Trigger listens specifically for events from chosen projects or campaigns — letting you decide exactly which automations should run. You can filter the workflow start conditions by:
  • Call Status — such as Completed, No Answer, Meeting Booked, or Failed.
  • Outcome — like Meeting Confirmed, Rescheduled, or Canceled.
  • Campaign Name — to target a specific AVA campaign.
  • Project Name — to narrow down triggers from larger multi-campaign setups.
When a Smart Call completes, AVA sends the event back to GHL, including full metadata: project name, campaign name, call status, and results.
If the event matches your configured filters, the workflow executes automatically — ensuring only the intended automations run.
Use Smart Trigger when:
  • You’re running multiple outbound campaigns and need to isolate each one’s automation logic.
  • You want precise filtering by project, campaign, or call outcome.
  • You’re replacing Contact Called in complex GHL workflows.

2. Inbound Agent Call

The Inbound Agent Call trigger activates when someone calls an AVA receptionist or inbound AI agent — for example, a virtual assistant that answers live inquiries, books appointments, or provides information. When the call starts, this trigger captures key details such as the caller’s phone number, call time, and any context AVA collected during the conversation.
You can then design your workflow to handle what happens next — whether that means logging the call, following up, or creating new contacts.
Typical workflow logic includes:
  • Checking if the caller already exists in your CRM.
  • If found: updating contact fields, tagging, or adding notes.
  • If not found: automatically creating a new contact with details such as time zone, state, or lead source.
This trigger is perfect for keeping inbound leads organized and logged automatically, ensuring every call gets tracked without manual effort.

3. Contact Called

The Contact Called trigger is the legacy version that fires whenever AVA completes an outbound call.
It works well for simple automations, letting you branch your workflow based on Call Status (such as Meeting Booked, Voicemail, or No Answer) or other payload values like Sentiment, Transcript, or Call Duration.
You can use it to:
  • Tag contacts and log notes after calls.
  • Send confirmation emails when a meeting is booked.
  • Trigger reminders or retries when no one answers.
Although still fully functional, it doesn’t support project or campaign-level filtering.
For any new setup, you should use AI Voice Studio Smart Trigger instead — which provides more granular control and prevents overlapping automations.

How They Work Together

You can combine AVA actions and triggers to create seamless voice automation workflows.
For example:
  • A form submission in GHL triggers a Smart Call, launching a call from your chosen AVA campaign.
  • Once the call completes, the Smart Trigger activates and processes the result — updating contact tags, sending follow-ups, or logging summaries.
Or, for inbound automation:
  • A caller reaches your AI receptionist → the Inbound Agent Call trigger fires → contact data and call summaries flow into your CRM automatically.
This approach keeps your lead management and follow-up fully automated — from first contact to final result.

Setup Recommendations

  • Use Smart Call and Smart Trigger for any new outbound workflows.
    They provide the most accurate data synchronization and campaign-level automation.
  • Keep Dynamic Outbound Call or Contact Called only for existing workflows to avoid reconfiguration.
  • Always map fields using dynamic tags (like {{contact.phone_raw}}) to prevent errors.
  • Use If/Else conditionals with triggers to branch workflows by call outcomes.
  • Test new Smart workflows on sample contacts before publishing.

FAQs & Troubleshooting

General Questions

Smart Call connects directly to AVA campaigns and uses their exact configuration, while Dynamic Outbound Call uses a simplified setup.
Smart Call offers tighter integration, language and voice control, and full campaign syncing.
Smart Trigger can filter workflows by project name, campaign name, call status, and outcome, while Contact Called only supports status and outcome filters.
Smart Trigger provides more precise control and prevents overlapping automations.
Yes. Existing workflows using Dynamic Outbound Call or Contact Called will continue to work.
However, all new workflows should be built using the Smart Call and Smart Trigger for best performance and accuracy.
No. As long as your AVA and GHL accounts are already connected, the Smart Call and Smart Trigger options will appear automatically in your workflow builder.

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.