Learn which compliance and eligibility safeguards apply to outbound Voice AI, how contact consent differs from location-level outbound calling terms, which call limits are enforced, and how to configure an eligible outbound workflow using the current setup experience.

Location-level outbound calling terms and contact consent are separate requirements. Accepting the platform’s outbound calling terms does not establish permission to call an individual contact. Businesses remain responsible for determining whether contacts can legally receive outbound AI calls and for following applicable laws, consent requirements, opt-outs, and DND preferences.

Voice AI Outbound Calling Compliance refers to the platform safeguards, location requirements, and business responsibilities that apply when using Voice AI to place outbound calls. These requirements help businesses scale AI-powered outreach while controlling call volume, timing, supported destinations, and location eligibility.

The platform continues to enforce safeguards such as applicable KYC requirements, location eligibility, call limits, call-hour rules, same-country restrictions, and Acceptable Use Policy controls. Businesses remain responsible for determining whether contacts can legally receive outbound AI calls.

Outbound safeguards help teams scale Voice AI campaigns while keeping calling activity within supported operational limits. The current workflow experience also reduces setup friction by bringing required location-level terms into the same action used to configure the outbound call.

• Flexible Consent Management: Manage contact consent using your organization’s own systems, documentation, and compliance process.
• Inline Terms Acceptance: Complete required location-level outbound calling terms directly from the Voice AI Outbound Call workflow action when prompted.
• Location Eligibility Controls: Applicable verification, KYC, policy, and configuration requirements continue to protect outbound access.
• Higher Calling Capacity: Each eligible location can place up to 5,000 outbound Voice AI calls per day.
• Faster Call Throughput: Calls can be placed at up to 10 calls per minute per location.
• Phone-Number Protection Limits: Each phone number can be called once per day and up to 14 times within a 14-day period.
• Time-Zone-Based Calling Windows: Calls are scheduled between 8:00 AM and 8:00 PM based on the contact’s phone-number timezone.
• Same-Country Domestic Calling: Outbound Voice AI calls are limited to supported domestic numbers in the same country as the location.
• AUP Safeguards: Outbound calling may be paused when a location exceeds applicable Acceptable Use Policy thresholds.

The Flexible Outbound Calling Framework allows businesses to manage contact consent using their own systems, records, and compliance workflows. Removing platform-level contact consent validation from the call flow reduces unnecessary workflow interruptions while keeping compliance responsibility with the business running the campaign.

• The platform does not perform contact-consent validation before placing outbound Voice AI calls.
• Businesses are responsible for ensuring contacts can legally receive outbound AI calls.
• Consent records can be maintained using the business’s preferred systems and compliance process.
• Location-level outbound calling terms do not replace contact-level consent.
• Other platform safeguards, including applicable KYC, eligibility, calling limits, calling hours, same-country restrictions, and AUP thresholds, continue to apply.

Location-level eligibility helps ensure outbound Voice AI calls originate only from accounts that meet the supported verification, policy, and configuration requirements. Completing outbound terms inside the workflow does not bypass any other eligibility controls.

To use Voice AI outbound calling, the location should:

• Complete applicable KYC or location-verification requirements.
• Remain eligible for outbound Voice AI calling.
• Remain within applicable platform usage and Acceptable Use Policy thresholds.
• Use an eligible Voice AI agent and From Phone Number.
• Accept required location-level outbound calling terms when prompted in the workflow action.

Businesses are responsible for determining whether each contact can legally receive an outbound AI call. A consistent consent-review process helps teams avoid treating workflow eligibility or location-level terms acceptance as permission to call an individual contact.

Your organization’s consent process should account for factors such as:

• Whether the contact agreed to receive phone calls.
• Whether consent for automated, prerecorded, or AI voice calls is required for the applicable use case.
• Whether the contact has opted out or requested not to be called.
• Whether the contact remains eligible to be called under applicable laws and the business’s policies.

Clear disclosure language helps contacts understand what communications they are agreeing to receive. Businesses can continue reviewing consent text across forms, surveys, calendars, external systems, and other lead-capture experiences even though Voice AI does not perform platform-level contact consent validation before dialing.

Depending on your legal and compliance requirements, consent language may address:

1. Agreement to receive phone calls and other communications when applicable.
2. Disclosure that calls may be automated, prerecorded, or use an AI voice when required.
3. Identification of the business or communication purpose where appropriate.
4. Instructions or processes for opting out of future communications.

AI disclaimer configuration controls how an outbound Voice AI agent introduces the call and presents supported disclosure or opt-out language. Reviewing the greeting before publishing helps ensure the opening message matches the business’s intended calling experience.

• Choose an available disclaimer style, such as Concise, Standard, or Conversational.
• Preview the disclaimer message.
• Add the agent’s intent message.
• Review the complete greeting before publishing.

Outbound calling limits control how quickly campaigns can dial, how many calls a location can place each day, and how frequently the same phone number can be contacted. These safeguards remain in place with the higher 5,000-call daily capacity.

Call-hour safeguards keep outbound Voice AI attempts within the supported calling window for the contact. The contact’s phone-number timezone is used to determine when the workflow can place the outbound call.

Calls that fall outside the supported calling window are scheduled for the next eligible time.

Same-country calling restrictions limit outbound Voice AI to supported domestic destinations associated with the location. This prevents the outbound workflow from being used for unsupported cross-country calling.

Outbound Voice AI calls can only be placed to supported phone numbers in the same country as the calling location. Unsupported international destinations are not eligible for outbound Voice AI calling.

Required outbound calling terms can now be handled inside the Voice AI Outbound Call workflow action. This keeps the location-level acknowledgement, AI Agent, and From Phone Number configuration together so users do not need to leave the workflow builder for a separate terms flow.

If the location has not yet accepted the required outbound calling terms, the action drawer can include:

• AI Agent
• From Phone Number
• Required outbound calling terms checkbox
• Terms & Conditions
• Calling guidelines

Review the available terms and Calling guidelines, select the required checkbox, and save the workflow action. Required acceptance is recorded once for the location rather than being repeated for each workflow.

Proper configuration combines location eligibility, the correct Voice AI workflow action, required location-level terms, and the business’s own contact-consent process. Reviewing these items before publishing helps avoid preventable call restrictions while keeping compliance responsibilities clear.

Step 1: Confirm Location Eligibility

Verify eligibility before launching an outbound workflow so terms acceptance does not get confused with other required location controls.

Step 2: Create or Open the Workflow

The outbound Voice AI call is initiated from a workflow, so select the trigger and audience conditions that match the campaign you intend to run.

Create a new workflow or open an existing workflow before adding the outbound Voice AI action.

Step 3: Add the Voice AI Outbound Call Action

The Voice AI Outbound Call action is where the outbound agent, calling number, and required location-level acknowledgement are configured.

Step 4: Configure the Outbound Action

Selecting the appropriate Voice AI agent and calling number ensures the workflow uses the intended conversation configuration and eligible outbound number.

Step 5: Accept Outbound Calling Terms When Required

If the location has not yet completed the required outbound terms acknowledgement, it can now be completed directly from the workflow action.

Step 6: Review Compliance and Publish

Reviewing the campaign before publishing helps ensure the workflow follows supported platform limits and the business’s own consent and compliance requirements.

If outbound Voice AI calls are not being placed as expected, first confirm that the location meets applicable eligibility and verification requirements. Verify that the workflow contains the Voice AI Outbound Call action, an eligible AI Agent and From Phone Number are selected, and any required outbound calling terms have been accepted.

If calls are being delayed, confirm that the location has not reached the 5,000-call daily limit, the contact has not exceeded the supported phone-number frequency limits, and the call falls within the 8:00 AM to 8:00 PM calling window for the contact’s phone-number timezone.

If the configuration appears correct and outbound calling is still unavailable, review the location’s verification status, applicable Acceptable Use Policy restrictions, workflow execution details, and Voice AI call logs. Contact your account administrator or support team if additional assistance is needed.