Setting the disclosure and the opening message
The disclosure and your intent message are heard together, as one greeting, so write and review them as a pair. The intent message is the reason for the call. Keep it to the one thing you want the person to know before they decide whether to stay on the line.
- In the voice agent's outbound settings, pick a disclaimer style: Concise, Standard or Conversational.
- Preview the disclaimer, then add your intent message.
- Read the combined greeting out loud, start to finish, the way the contact will hear it.
- In the workflow that places the call, add the Voice AI Outbound Call action and choose the AI Agent and the From Phone Number.
- Accept the outbound terms if the action asks for them. HighLevel lets you do that inside the call action.
- Before publishing the workflow, review who it will call, how they agreed, how opt-outs are handled and when the calls will go out.
What we've seen on the settings screen
HighLevel's help center lists the three styles above. In the builds we've done, the outbound settings have shown a bit more: an Enable AI Disclosure switch, a fourth Custom option for your own wording, and a switch to play the disclosure on every call.
None of those three appear in the public article we checked, and HighLevel has changed this screen before, so check what yours shows before you plan around them. If you write Custom wording, keep it plain: who is calling, that it's an AI, and how to stop the calls.
Opt-outs during the call
We've also seen the agent listen for a spoken opt-out, such as a caller saying “stop” or “don't call me again,” and switch the contact's calling consent off when it hears one. That is useful, but treat it as one route in, not your whole opt-out process.
Test it on your own phone with the phrases your contacts are likely to use. Then make sure opt-outs that arrive another way, by text, through a form or told to your team, end up on the same contact record, and that your workflow checks that record before it dials.
A setting that plays a disclosure is not a record that the person agreed to be called.
Rather have it set up for you?
We'd write the disclosure and opening message for your outbound agent and set its calling rules, starting with a 30-minute 1:1 with Rob.
When HighLevel lets the agent dial
HighLevel's compliance article sets limits on outbound Voice AI calls. They are the platform's rules, not a legal standard, and they explain why a call can go out later than you expected, or not at all.
- A calling window of 8 AM to 8 PM in the time zone of the contact's phone number. A call queued outside the window is moved to a time inside it.
- One call per number per day, and no more than 14 calls in 14 days to the same number.
- No unsupported cross-country calls. A destination that isn't supported from the account's country is ineligible and won't be dialed.
What HighLevel does not check for you
HighLevel documents no platform-level check that a contact gave permission before an outbound AI call. Accepting the outbound terms for the sub-account doesn't create that permission either, and passing the platform's eligibility checks is not a legal finding that a call is allowed.
So the consent record has to exist before the workflow runs: where each contact agreed, what wording they saw and when. Keep it on the contact, and build the workflow so it only reaches people who have it.
This page is not legal advice. Calling rules differ by country and by state, so check the ones that apply where you call, with your own attorney where it matters.