AI voice agents for outbound calls: how to compare them before you dial

Last Updated: 2026-10-02

An inbound support call starts because the customer picked up the phone. An outbound call starts because a system decided to dial, and almost everything that matters about an AI voice agent follows from that one difference.

Most lists of AI voice agents are written about the conversation: how natural the voice sounds, how fast it answers, how well it handles an interruption. Those differences are real, and they matter less than a set of questions that only exist when the company is the one placing the call. Who has agreed to be called. What the platform does at 9:05 p.m. in the recipient’s time zone. What the agent does when it reaches voicemail, when nobody answers, or when the person says stop in the middle of a sentence.

This guide is for the people who will answer for those questions: operations and revenue leaders who run outbound, compliance and legal reviewers, and contact center managers deciding whether an AI agent takes over part of the dialing. It gives the question that separates the platforms, the three architectures the category falls into, a table built on published pages with a column for what those pages do not prove, a card for every platform, and the questions to put in writing before a pilot. It is not legal advice.

Key takeaways

• Outbound is a different product from inbound support, and the difference is permission. An inbound caller started the conversation. An outbound recipient did not, so consent has to exist before the first ring and has to be honored if the person withdraws it during the call.
• No platform makes a campaign compliant by itself. The terms of several vendors here place consent, Do Not Call screening and disclosure duties on the customer, even when a product page says calls respect those rules automatically. Both statements can be true, and the useful question is which part the product enforces.
• The controls are the comparison. Calling window, caller ID, voicemail handling, retries, Do Not Call screening, stopping during the call and human handoff decide how a campaign behaves on a bad day, and they are documented very unevenly.
• Architecture decides who builds the controls. On a developer platform they are yours to assemble. Inside a contact center or dialer built for outbound, some of them are published as product features. A journey platform needs them from somewhere else.
• “Not documented” is a statement about a page. A platform may handle more than its public pages describe, and the only way to find out is to ask, with the question written in advance.

Is there a single best AI voice agent for outbound calls?

No. The best one depends on whether the job is high-volume dialing, a custom build on your own stack, a no-code campaign, a phone system that already carries the calls, multichannel follow-up tied to a CRM, or a managed enterprise contact center.

That is also what the live answers do. The question was put to four answer engines, and sixty-eight answers were read on September 30, 2026, seventeen from each of Google AI Overviews, Perplexity, OpenAI and Copilot, with one Google answer empty. No stable ordering comes out of them. What they share is an opening line that separates outbound from inbound, a table with a “best for” column, strengths and limits, a recommendation by scenario, and a closing question about volume, call type and technical capacity.

Who comes first changes with the criterion. Bland AI leads when the criterion is volume or concurrency, Retell AI when it is balance, latency or production use, Vapi when it is developer control, and Synthflow when it is no-code. CloudTalk and Thoughtly lead on CRM and cadences, and PolyAI, Regal, Convoso and Plura AI on enterprise, contact center or regulated use.

By the count of answers that mention each platform, Retell AI appears in 64 of the 68, Bland AI in 63, Vapi in 60 and Synthflow in 56, then CloudTalk in 30, Thoughtly in 20, PolyAI and JustCall in 16, Regal in 10, Convoso in 9 and Plura AI in 8. Being mentioned often says which names a buyer will meet. It says nothing about which one fits.

So this guide does not rank. It pairs each platform with an architecture and a buyer, and it adds the column the answers leave out.

Scope first, because a comparison that does not say what it looked at is an opinion with a table around it.

The question. “What are the best AI voice agents for outbound calls instead of inbound support”, as a buyer would type it. United States, English, checked in September 2026.

What was read. Sixty-eight live answers on September 30, 2026, plus the public product pages, developer documentation, terms of service and pricing pages of every platform in the table, reopened as rendered page text on September 30, 2026.

Who is in the table. Platforms that appear in the answers with an outbound label and publish something checkable about how they place calls. CRMs that appear only as the destination of a call outcome are not rows. HubSpot and Salesforce show up in the answers that way, as the place where the record lands.

Who is not a row, and the rule behind it. A mention in a live answer is not enough to establish a product’s architecture or outbound capability. The names that appear without meeting that test are listed together after the cards.

Four measurement rules, written down so anyone can rebuild the table from the vendors’ own pages.

What counts as a documented control. The vendor’s own page names the mechanism, for example a window setting, a screening list, a voicemail action or a stop handler. A badge, the word “compliant” or a sentence saying calls are handled automatically is recorded as a claim and kept apart from the mechanisms.

What counts as a customer responsibility. A clause in the terms or a legal page that places consent, screening, disclosure or lawful use on the customer. It is recorded next to the claim, because the two often sit on the same vendor.

What the price column means. Rates as published on September 30, 2026. A platform with no public rate is recorded as not publishing one.

What “Not documented on the pages read” means. The pages reviewed for that row do not describe the control, and nothing is concluded about the product.

indigitall is included because its public page documents outbound voice as a step in a customer journey. It is assessed with the same columns as every other platform, and any missing control remains a question for the vendor.

What is different about an outbound call compared with inbound support?

The call starts somewhere else. In inbound support the customer initiates, so the open questions are mostly about recording, disclosure and how well the agent resolves the request, the same things that make customers give up on a phone menu. In outbound the company initiates, so permission has to exist before the first ring, and every other control has to work without the recipient having asked for anything. One platform’s own legal page puts the split in a sentence: the Telephone Consumer Protection Act primarily governs outbound calls and texts, and does not generally apply to communications the consumer initiates.

Nine things change when the agent dials, and each one is a question a platform either answers in writing or leaves to you. The first five have to hold before the phone rings:

• Consent. Who has agreed to be called, in what form, recorded where, and whether the platform checks that record before dialing or only assumes it.
• Who initiates. A system, a schedule or a journey trigger starts the call. The platform needs a way to show why this number was dialed at this moment.
• Calling hours and time zone. A campaign started at 2 p.m. in one state reaches recipients at different local times. The question is whether the platform enforces a window per recipient or only a start time for the batch.
• Caller ID. The number shown has to be real, consistent and recognizable, and some platforms sell a branded caller ID as a separate add-on.
• Do Not Call screening. Against which lists, how often, and whether the platform does it or expects the customer to upload a clean list.

The last four shape what happens during and after the call:

• Stopping during the call. A person can ask to stop in the middle of a sentence. The agent has to recognize it, end the call and pass the request to the system that decides the next call.
• Voicemail and answering machines. Hang up, leave a message or navigate a menu, and whether the choice is configurable.
• Retries. How many times, how far apart, and what ends the sequence.
• Handoff. When a person answers and wants a human, what travels with the transfer.

What the FCC said about AI voices. In a declaratory ruling adopted on February 2, 2024, and released on February 8, 2024 (FCC 24-17), the FCC stated that the restrictions the Telephone Consumer Protection Act places on an “artificial or prerecorded voice” cover technologies that generate human voices with AI. That brings the prior consent requirement to these calls, and prior express written consent when the call introduces an advertisement or contains telemarketing. The text is on the FCC’s document server, and the FCC’s own summary is shorter.

What the FTC says about timing, lists and opt-outs. The FTC’s guidance on the Telemarketing Sales Rule sets calling-time restrictions, including a general prohibition on calls before 8 a.m. or after 9 p.m. in the recipient’s time zone, and separately addresses the National Do Not Call Registry and the seller’s own list, the automated opt-out required for prerecorded telemarketing calls, the ban on cold prerecorded calls and the transmission of caller ID. The category of call and any exemption still need to be checked for each campaign.

What is still moving. The rules on revoking consent are being adjusted. On January 6, 2026, the FCC (DA 26-12) extended until January 31, 2027, the waiver of the requirement that a revocation made in response to one type of informational message apply to all future communications. An FCC fact sheet dated September 9, 2026 describes changes that would let a revocation apply only to the category of message and would set an exclusive means of revocation. All of this is as of September 30, 2026. A rule that keeps changing is a reason to ask a vendor how the product follows it.

Which category a given call falls into, a reminder or a marketing call, is a decision for the company and its counsel. What a comparison can do is show which platforms publish how the product handles the mechanics, and which leave them to the customer.

What do the live answers compare, and what do they skip?

They compare the controls as side notes. Of the sixty-eight answers, 25 mention the TCPA, 23 mention Do Not Call, 19 mention consent, 18 mention human handoff, 10 mention voicemail or an answering machine, and 7 mention calling hours, calling windows, time-zone scheduling or related timing rules, all of them from OpenAI.

None of them has a matrix of which platform documents which control, or a comparison of what happens when a person, an answering machine or nobody answers. None treats permission, timing, recipient, outcome and next action as the unit of a call. One OpenAI answer comes closest with a single sentence: the platform may provide controls, but it does not make the campaign compliant by itself.

That gap is why this page exists, and why the table below ends with a column about what a platform’s published pages do not prove.

Three, and the architecture decides who builds the controls discussed above.

A voice agent or infrastructure platform built for developers. Vapi, Retell AI and Bland AI sit here, with Bland AI positioned for outbound at scale, and Synthflow as the no-code builder of the same kind. You assemble the campaign: the list, the schedule, the number, the screening and the voicemail behavior. The platform gives you the parts, and the terms say whose job it is to use them lawfully.

A phone system, communications platform or contact center with an AI agent. CloudTalk, JustCall, Plura AI, Regal, Convoso and PolyAI. The agent is part of a wider communications or dialing operation. Some of these publish outbound compliance features as part of the dialer, while others publish workflows, concurrency or communications channels without documenting the controls that run before the AI dials.

A CRM or customer journey with a voice step. Thoughtly, with voice, SMS and email inside CRM flows, and indigitall, where the call is one channel in a journey. The call is triggered by what the customer did.

The comparison table

Read the last two columns first. The controls column is where vendors differ most, and the last column is what decides the pilot.

One row has no engine label, and that is deliberate. indigitall does not appear in the live answers to this question, so there is no wording from an engine to put in that cell. Writing one would falsify the whole column, so the cell says what it is.

Each card says where its cells come from. It names the public pages used to build the comparison and the date they were checked, and its claims stay within what those pages document. When a control is not described, the card says so and leaves it as a question for the vendor.

The last column describes published pages. “Not documented on the pages read” means the pages reviewed for that row did not describe the control. It does not show that the product cannot perform it, and a platform may handle consent, hours and screening in ways it has not published. The only way to find out is to ask, with the question already written, which is what the closing sections are for.

The platforms, one by one

The twelve platforms are grouped by architecture, in the order of the table, and each card draws only on the platform’s own public pages for what that platform does. The wider category they sit in is mapped in the guide to AI agent software. The groups describe who builds the controls, which is the decision underneath the others, and they rank nothing.

Bland AI

A programmable voice platform with an API, batch endpoints and self-serve plans, positioned for outbound at volume.

Best for: high-volume outbound campaigns, the label the answers repeat most for it.

What it does well: it publishes its economics and its limits on one page. Per-minute rates, daily and hourly call caps and concurrency for each plan sit side by side, so volume can be modeled before a conversation with sales. Batches accept many call objects, each with its own start time.

Key features:

• A batch endpoint that takes a list of call objects, each with a start time
• Daily caps of 100 calls on Start and 2,000 on Build, and hourly caps of 100 and 1,000
• 10 concurrent calls on Start, 50 on Build and custom on Enterprise
• A separate transfer rate per minute for calls handed to a person

Watch out for: the terms make the customer solely responsible for lawful use, in general terms, and the pages read describe no consent, Do Not Call or calling-window mechanism. The batch example also treats the time zone of a start time as optional, defaulting to UTC, so a scheduled start that leaves it out is read in UTC.

Pricing: published. 0.14 US dollars per minute on Start with no platform fee, and 0.12 plus a 299 US dollar monthly platform fee on Build. Transfers are priced at 0.05 and 0.04 per minute. Enterprise is custom. Rates as published on September 30, 2026.

Doesn’t fit if: you need more than 2,000 calls a day without an enterprise contract, because the top self-serve plan caps there.

What the source does not prove: that a scheduled start respects the recipient’s local time, or how voicemail and a request to stop are handled, which the pages read do not describe.

Public evidence: the Bland AI pricing page, the batch create API reference and the terms of service. Checked September 30, 2026.

Retell AI

Voice infrastructure sold to developers, with batch calls, voicemail handling and a published concurrency model.

Best for: best overall balance and low-latency outbound campaigns, in the engines’ words.

What it does well: the batch page covers the operating parts of a campaign in one place. A CSV carries per-recipient columns, the agent has a from number, time windows are configured for the batch, and a reserved concurrency setting keeps a batch from taking every line. Voicemail detection lets the agent hang up, leave a message or navigate a menu, and it can be tested without dialing by playing a recording into a web call.

Key features:

• CSV batch calls where extra columns reach the agent as variables
• Time windows configured for each batch
• Reserved concurrency for other calls, so a batch does not take every line
• Voicemail and IVR detection with hang up, leave a message or navigate the menu
• A branded call ID as a paid add-on

Watch out for: the terms place compliance with telemarketing and recording laws on the customer and require screening against Do Not Call lists at least every 31 days. The batch page does not say whether the time windows follow each recipient’s time zone.

Pricing: published. Voice agents from 0.07 to 0.31 US dollars per minute depending on the voice and model, with 20 concurrent calls included. Batch calls add 0.005 per dial and a branded call ID adds 0.10 per outbound call. Rates as published on September 30, 2026.

Doesn’t fit if: you want a finished campaign manager that applies your compliance rules for you, because the terms leave those checks with the customer.

What the source does not prove: that time windows follow each recipient’s time zone, and how consent records are kept.

Public evidence: the Retell AI pricing page, the batch call and voicemail documentation and the terms of service. Checked September 30, 2026.

Vapi

A platform for developers creating voice agents, with campaigns built from a caller, a number, contacts and a schedule.

Best for: custom and engineering-heavy outbound systems, and developer-led outbound.

What it does well: a campaign is made of a caller, an outbound-capable number, contacts and a schedule that sets when dialing starts, when it must stop and how many calls run at once. Contacts begin pending and every attempt has a result to review in one place. The outbound documentation is also direct about the stakes: it says automated dialing without consent breaks FCC law, and it points to its own consent guide.

Key features:

• Campaigns that call a list with an assistant or a squad
• A schedule with a start, a stop and a concurrency limit
• Values per contact to personalize each conversation
• An imported outbound-capable number, since free Vapi numbers are not supported for campaigns
• A result for every attempt, reviewable in the campaign

Watch out for: no consent-capture feature appears on the pages read, and the stop time is a campaign setting, not a per-recipient one. Models, transcription and voice are billed at provider cost on top of the hosting fee, and outbound needs a number imported from a telephony provider.

Pricing: published. A pre-paid hosting fee of 0.05 US dollars per minute with models passed through at cost. The free tier allows 4 concurrent calls, a Core plan at 29 US dollars allows 10, and a Pro plan at a 999 US dollar monthly minimum allows 30. Rates as published on September 30, 2026.

Doesn’t fit if: you want one invoice for the whole call, because hosting, model, transcription and voice are separate lines.

What the source does not prove: how consent gets recorded, and whether the stop time works per recipient.

Public evidence: the Vapi pricing page and the outbound calling and campaigns documentation. Checked September 30, 2026.

Synthflow

A no-code voice agent platform sold on enterprise contracts, with outbound campaigns started through an API.

Best for: no-code outbound workflows, for nontechnical sales and operations teams.

What it does well: a campaign is a list, an agent and the hours you allow. It dials through the list as fast as the account’s concurrency permits. Every dialed recipient becomes a regular call with transcripts, recordings and webhooks, and a campaign can be paused, resumed, canceled and extended with more recipients.

Key features:

• A campaign created with one request to the Platform API, returning an id to follow it
• Dialing inside the hours you allow
• Pause, resume, cancel and add recipients later
• Every call in the same history, with transcripts and recordings

Watch out for: campaigns are documented on Enterprise plans and activated through support, which makes the no-code builder a platform whose campaigns are started through an API. The transparency statement leaves the AI disclosure to the customer to configure in line with the law that applies.

Pricing: published as a floor. Enterprise contracts start at 30,000 US dollars annually, and the final price depends on volume, concurrency, telephony setup, integrations, security and launch support. As published on September 30, 2026.

Doesn’t fit if: you want to start small and self-serve, because campaigns sit on the Enterprise plan.

What the source does not prove: how the allowed hours relate to each recipient’s time zone. The transparency statement has a section on consent and legal compliance for outbound AI calls, and it is the first page to read before a pilot.

Public evidence: the Synthflow pricing page, the campaigns documentation and the AI transparency statement. Checked September 30, 2026.

Thoughtly

An engagement platform with voice, SMS and email agents inside CRM-connected flows.

Best for: multichannel cadence, automated follow-up and speed-to-lead follow-up.

What it does well: the call is part of a cadence. Outbound runs from a CSV upload. Voice, SMS and email sit in the same workflows, and two-way CRM sync with HubSpot, Salesforce and Zoho, among others, returns the outcome of a call to the record.

Key features:

• Bulk upload from CSV to run outbound calls
• Voice, SMS and email in the same workflows
• Two-way CRM sync, with HubSpot, Salesforce and Zoho among the named systems
• 200 or more integrations and a REST API
• A quoted tier with 100 or more concurrent calls and a TCPA review

Watch out for: the terms make compliance the customer’s sole responsibility, name the TCPA, the Telemarketing Sales Rule and Do Not Call rules, and require a truthful caller ID and the legal disclosures. The Flex plan is described for inbound conversion and lists 10 concurrent calls.

Pricing: partly published. Flex starts at 500 US dollars a month and the Tailored tier is a quote. No per-minute rate appears on the pricing page. As published on September 30, 2026.

Doesn’t fit if: outbound volume is the main job and you want published per-minute rates.

What the source does not prove: what a campaign enforces before dialing, since the pages read show the upload and the terms but not the controls.

Public evidence: the Thoughtly pricing page, the terms of service and the bulk upload documentation. Checked September 30, 2026.

CloudTalk

A business phone system with AI voice agents that handle inbound and outbound calls.

Best for: sales teams wanting a phone system plus AI, and small and mid-size companies that want the phone system integrated.

What it does well: the agent runs inside a system that already has numbers, users and CRM sync. The agent page says it handles inbound and outbound calls in more than 70 languages and accents without code, and bundles of voice agent minutes are priced separately from the seats.

Key features:

• AI voice agents for inbound and outbound calls in 70 or more languages and accents
• A business phone system that syncs with your CRM
• A branded caller ID as an add-on
• Bundles of voice agent minutes starting at 200 a month

Watch out for: prices are shown in euros, with seat plans billed per user and per year, and the pages read do not describe consent, Do Not Call screening or calling hours for the AI agent.

Pricing: published. Seat plans start at 25 euros per user per month on Starter and 29 on Essential, billed annually, with a minimum of one license. Voice agent bundles start at 99 euros for 200 minutes a month. As published on September 30, 2026.

Doesn’t fit if: you have no use for a business phone system, because the AI agent is positioned as part of a business phone system rather than as a standalone voice agent.

What the source does not prove: which outbound controls the AI agent uses and which belong to the human dialer, and what happens when the agent reaches voicemail.

Public evidence: the CloudTalk pricing page and the AI voice agents page. Checked September 30, 2026.

JustCall

A business phone system and dialer with an outbound AI voice agent as a product of its own.

Best for: outbound calling inside a full phone system, and lead qualification plus booking.

What it does well: it states the compliance promise in the plainest words of any vendor here. The product page says every call respects consent, time-of-day and Do Not Call rules automatically. It also says call summaries, outcomes and next steps sync to the CRM in real time.

Key features:

• An outbound AI voice agent with its own product page
• Automatic respect for consent, time-of-day and Do Not Call rules, as the page states it
• Call summary, outcome and next steps synced to the CRM
• Business phone system, messaging and call center software on the same platform

Watch out for: the page also says the agent is only available for compliant use cases, that every call trigger includes built-in consent and that the agent calls only opted-in contacts. It still does not describe the mechanism, where the list comes from or how a stop during the call is handled. Ask what “automatically” covers and which consent record the product checks.

Pricing: partly published. Business phone plans start at 29 US dollars a month according to the pricing page, and the AI voice agent is listed there as an add-on. As published on September 30, 2026.

Doesn’t fit if: you want only an agent and not a phone system, because the engines describe it as outbound calling inside a full phone system.

What the source does not prove: what “automatically” covers, who supplies the consent record, and whether the same controls apply to AI calls and to human ones.

Public evidence: the JustCall outbound AI voice agent page and the pricing page. Checked September 30, 2026.

PolyAI

An enterprise conversational AI vendor with a documented API for placing outbound calls.

Best for: enterprise managed deployments and complex outbound conversations.

What it does well: the public API reference includes a call that places a programmatic outbound call to a target number and tracks its status, next to conversation, handoff, messaging, SMS and webhook APIs. That is concrete, checkable outbound documentation from an enterprise vendor.

Key features:

• An API that triggers an outbound call and tracks its status
• Handoff, messaging, SMS and webhook APIs in the same reference
• Keys provisioned to a region, with a different host for each API family

Watch out for: the pages read describe a single-call API and not a campaign manager, and the product is sold through a demo request.

Pricing: no rate appears on the pages read. The documentation offers a demo request.

Doesn’t fit if: you want to self-serve a campaign, because the positioning the engines repeat is managed enterprise deployments.

What the source does not prove: campaign controls, calling windows, consent or Do Not Call handling.

Public evidence: the PolyAI API reference. Checked September 30, 2026.

Regal

An AI agent platform for contact centers, with agents that staff progressive and predictive dialer campaigns.

Best for: B2C outbound sales and collections, and regulated industries, as the engines label it.

What it does well: it is built around the dialer. A post from the vendor, last updated on March 17, 2026, says its AI agents now staff progressive and predictive dialer campaigns, reducing time lost to rings and voicemails. The home page names a layer of built-in safeguards for privacy, compliance, hallucination control and escalation.

Key features:

• AI agents that staff progressive and predictive dialer campaigns
• A safety layer for privacy, compliance, hallucination control and escalation, as the home page names it
• A business context layer that draws on customer data, knowledge and workflows
• A vendor guide titled Outbound Campaign Compliance 101, which names the Telemarketing Sales Rule, the TCPA and Do Not Call

Watch out for: the compliance material is a named layer and a set of vendor posts, with no mechanism described on the pages read. Ask which checks run before the AI agent dials.

Pricing: no rate appears on the pages read.

Doesn’t fit if: your use case is inbound support, because the engines place it in outbound sales and collections.

What the source does not prove: which checks run before an AI agent dials, and whether the safety layer enforces a calling window.

Public evidence: the Regal home page and its blog post on progressive dialing for AI agents. Checked September 30, 2026.

Convoso

An outbound contact center and dialing platform that offers a voice AI agent to qualify leads.

Best for: compliance-heavy industries and contact-center scale, per the engines.

What it does well: it lists compliance among its product features. A compliance page describes state dialing rules tracked against each lead record, Do Not Call screening against internal, federal and state lists, and a reassigned numbers database. The voice agent qualifies leads at scale and hands sales-ready prospects to sellers.

Key features:

• State dialing rules tracked per lead record
• Do Not Call screening against internal, federal and state lists
• A reassigned numbers database
• A voice AI agent that qualifies leads and hands them to sellers

Watch out for: the compliance page describes the platform and does not say whether the voice agent runs inside those controls. A response-time figure on the agent page is a vendor claim and is not repeated here.

Pricing: by request. The site offers a path to pricing and no public rate.

Doesn’t fit if: you want a standalone voice agent without a dialing platform, because the agent is presented as part of Convoso’s outbound platform.

What the source does not prove: whether the compliance controls apply to calls the voice agent places, and how the agent handles voicemail.

Public evidence: the Convoso compliance page and the voice AI agent page. Checked September 30, 2026.

Plura AI

A communications platform with AI agents for voice, SMS and RCS, sold on annual contracts.

Best for: enterprise compliance-heavy teams, in the engines’ words.

What it does well: its plan limits are public, so a buyer can test them. The Multi plan lists 5 concurrent outbound calls and 8 concurrent inbound calls, unlimited workflows, and caller ID monitoring among its features.

Key features:

• Voice, SMS and RCS agents on one platform
• Separate concurrency limits for outbound (5) and inbound (8) calls on the Multi plan
• Unlimited workflows
• Caller ID monitoring listed among the plan features

Watch out for: a glossary page on its site says the company operates as an FCC-licensed carrier. It is the vendor’s claim about itself. The pages read give no license number, and the claim does not appear on a product page, so it stays a question for the vendor. Plans are annual contracts.

Pricing: published. The Multi plan is 5,000 US dollars a month plus overages on a yearly contract billed monthly, with agent talk time at 15 US dollars an hour, transfer time at 0.02 per minute, SMS at 0.06 per message and phone numbers at 3 US dollars a month. As published on September 30, 2026.

Doesn’t fit if: you need month-to-month flexibility or a small pilot, because the published plans start at 5,000 US dollars a month on annual contracts.

What the source does not prove: the license claim, and how campaigns, calling windows and consent are handled, which the pages read do not describe.

Public evidence: the Plura AI pricing page and a glossary page on licensing. Checked September 30, 2026.

indigitall

Outbound voice as one step inside a customer journey.

Best for: organizations already running reminders and follow-ups over several channels that want the call to share the same customer profile and the same rules. There is no engine label for indigitall, so this is an editorial fit.

What it does well: the trigger comes before the call. A journey step or a churn or no-show prediction triggers it, and the page describes it as a next best action placed automatically when a text has not landed, not a blast to a list. It documents three uses, retention when email and WhatsApp do not convert, operations such as confirming or rescheduling an appointment and reducing no-shows, and proactive alerts such as renewals or a delivery change.

Key features:

• Outbound calls triggered by a journey step or a churn or no-show prediction
• Actions on connected systems through MCP, listed as calendar, CRM, SMS and booking
• A handoff to a person that carries the transcript, the detected intent and the steps already taken
• The same customer profile across push, email, SMS, WhatsApp and in-app
• A published outcome split of 84 percent resolved by the agent and 16 percent escalated with context, shown without a sample, period or method and not stated as a measure of outbound calls

Watch out for: the page does not describe consent, Do Not Call screening, calling hours, AI disclosure or voicemail detection, and those questions apply to indigitall exactly as they do to every other row. It also publishes no concurrency, latency, answer rate or price. There is a second surface with the same family name: the reporting connector is documented as read-only by design, which is the opposite of the actions described above.

Pricing: not published. The route in is a demo and a contract, with no self-service tier.

Doesn’t fit if: the phone is the only channel you use, because the value of this shape is that the call shares a profile with the messages. It also does not fit an organization with no owned channels and no opted-in contact base, one that wants a high-volume dialer with campaign tooling built for outbound, one that wants public pricing and card signup, or one that needs a sales CRM or a storefront and not an engagement platform.

What the source does not prove: that consent, calling hours and screening are handled, that the 84 percent applies to outbound, or that any customer runs outbound voice today, since no published case covers it.

Public evidence: the AI voice and AI agents product pages and the MCP integration page, all linked above. Checked September 30, 2026.

Several names appear in the answers, but no public page that was read establishes their architecture or outbound capability. Under the rule that a mention is not enough, they get no card. Goodcall, 11x, Aloware, Cognigy, Replicant and Observe.AI appear as agents, contact center software or analytics, in answers that do not agree on what they are for. Plivo, Telnyx, SignalWire and LiveKit appear as communications infrastructure, the part under an agent rather than the agent itself. A long tail of single mentions, among them AiSA-X, Leaping AI, Brilo.ai, Air AI, LuMay, Orum, Sierra, Regie.ai and Commplify, appears once or twice each. A name in this paragraph shows how much of the answers’ evidence could be checked on a public page, and tells you nothing about the product.

What should you ask a vendor about consent, Do Not Call and calling windows?

Put these in writing before a pilot, and ask every vendor on the shortlist the same ten, including the ones whose pages sound reassuring. The answers decide more than any demo. The first five apply before the first ring.

1. Who records consent, and does the platform check it before dialing? Ask for the field where the consent record lives and for what blocks a call when it is missing. A platform that assumes the list is clean and a platform that refuses to dial a number without a record are different products, and the pages read rarely say which one it is.
2. Which Do Not Call lists does it screen, and how often? One vendor’s terms require screening at least every 31 days and leave the job to the customer. Another publishes screening against internal, federal and state lists as a feature. Ask whether the product does it or expects you to upload a clean list.
3. Whose time zone sets the calling window? The FTC guidance sets a general prohibition on calls before 8 a.m. or after 9 p.m. in the recipient’s time zone, subject to the category of call and any exemption. Ask whether the window is enforced for each recipient or set once for the batch, and what happens to the calls still queued when the window closes.
4. What does the recipient see as the caller ID? A consistent, recognizable number is a requirement in the FTC guidance, and some platforms sell a branded caller ID as a separate add-on. Ask who is responsible for the number’s reputation.
5. What does the agent say first? One vendor’s transparency statement leaves the AI disclosure to the customer to configure. Ask where the disclosure is set, what the default is and who can change it.

The last five cover the call itself, the contract and the test.

6. What happens when the person says stop? A recipient can withdraw consent by any reasonable means, and the campaign must recognize and process it during the call. Ask how the agent detects it, how fast it reaches the list and how the vendor follows the revocation rules that are changing in 2026.
7. What happens at voicemail and when nobody answers? One documentation page lets the agent hang up, leave a message or navigate a menu. Ask for the cap on retries, the spacing between them and what ends the sequence.
8. What travels with the handoff? When a person answers and asks for a human, ask whether the transfer carries the transcript, the detected intent and the steps already taken, and what the agent does if nobody is free.
9. Which part is the product and which part is the customer? Set the product page and the terms side by side. A page that says calls respect the rules automatically and a clause that makes compliance the customer’s sole responsibility are both on record at the same vendor, and you want to know what each covers.
10. What can be tested without dialing a real person? One documentation page describes testing voicemail behavior by playing a recording into a web call. Ask for a test that exercises each control above with a list of numbers that have consented.

Who is responsible when an AI outbound call breaks a rule?

Two statements sit side by side in the vendors’ pages. A product page says every call respects consent, time-of-day and Do Not Call rules automatically. The terms of other vendors say compliance is the customer’s sole responsibility, name the laws, and put the duty to screen, to obtain consent and to disclose on the customer. Several of these clauses are general, as in a platform that makes the customer solely responsible for lawful use.

Neither rules out the other. A platform can enforce a calling window and still leave the consent record to you. The split decides the risk: which controls the product applies on its own, which it offers as settings, and which it leaves entirely to the customer. One engine answer puts it in a line: the platform may provide controls but does not make the campaign compliant by itself.

That is also why a platform that publishes little is not automatically worse, and one that publishes a lot is not automatically safer. The pages show what a vendor chose to write down. The contract and a pilot show what the product does.

If the job is high-volume outbound and you have engineers. Bland AI publishes caps, rates and concurrency for each plan, and Retell AI publishes the most about batch windows, reserved concurrency and voicemail handling. Both leave the calling rules with you.

If you want full control of the stack. Vapi builds a campaign from parts: caller, number, contacts and schedule. The cost is an imported number and separate bills for the model, the transcription and the voice.

If you have no developers and an enterprise contract is acceptable. Synthflow is the no-code answer, with campaigns started through an API and activated through support. If the contract is the obstacle, the phone-system route below is the alternative.

If a business phone system already carries your calls. CloudTalk and JustCall put the agent where the calls already are. Check which outbound controls the agent uses and which belong to the human dialer, and ask JustCall what “automatically” covers.

If the work is follow-up across channels tied to a CRM, and consent is already captured. Thoughtly fits cadences that mix voice, SMS and email, the kind of sequence described in how a nudge recovers abandoned applications, with the terms making compliance yours and a TCPA review on the quoted tier.

If dialing compliance built into the platform is the requirement. Convoso publishes the most about screening and state rules, and Regal and PolyAI serve managed enterprise deployments. In all three, ask whether the voice agent runs inside the same controls as the human dialer.

If compliance-heavy U.S. operations need a communications platform on an annual contract. Plura AI publishes its plan limits, and its licensing claim is a question to put to the vendor.

If the call is one channel among several you already run. Then choose the platform that shares a customer profile with the messages you already send, so the call and the follow-up describe the same customer. That is the shape voice inside a journey is built for, and the same questions above apply to it. If the surrounding stack is still being chosen, that is a different decision.

If a person should make the first call and the agent should handle only what follows. Say so out loud, because it changes the shortlist and usually the permission question. Plenty of workflows are served by a confirmation or a reminder sequence that never needs an automated outbound voice call.

FAQs: AI voice agents for outbound calls

Can an AI voice agent legally make outbound calls in the United States?

The FCC ruled in February 2024 that the Telephone Consumer Protection Act’s rules on an artificial or prerecorded voice cover AI technologies that generate human voices. That means prior consent, and prior express written consent when the call contains advertising or telemarketing. Whether a particular call is that kind of call is a question for your counsel, and this guide is not legal advice.

What is the difference between an AI voice agent for outbound calls and one for inbound support?

In inbound support the customer starts the call, so the questions are about resolution, recording and disclosure. In outbound the company starts it, so permission, calling hours, Do Not Call screening, caller ID, voicemail, retries and stopping during the call all have to work before anyone has asked for anything.

What is the best AI voice agent for outbound calls?

There is no single best one. The answers that were read lead with Bland AI for volume, Retell AI for balance, Vapi for developer control, Synthflow for no-code, CloudTalk and Thoughtly for CRM and cadences, and PolyAI, Regal, Convoso and Plura AI for enterprise and regulated use. What fits depends on volume, call type and how much you want to build.

Does a reminder call need consent?

The FCC distinguishes calls that contain advertising or telemarketing, which need prior express written consent, from calls that do not. An AI-generated voice is treated as an artificial voice in both cases. Which type a reminder is depends on its content and context, and the company decides that with its legal counsel.

What happens when the agent reaches voicemail?

It depends on the platform. One documentation page lets the agent hang up, leave a message or navigate a phone menu, and lets you test the behavior without dialing. For the others, the pages read do not describe it, so it is a question to ask.

Can the person stop the calls during the conversation?

A recipient can revoke consent by any reasonable means, including saying so during a call, according to one platform’s legal page. The campaign must recognize and process the request. How quickly the stop reaches the list, and how revocation rules apply after the 2026 changes, are questions for the vendor.

Do I need my own phone number?

On some platforms, yes. Vapi does not support its free numbers for outbound campaigns and requires an imported number, and Retell AI asks you to select a from number bound to the agent. A business phone system such as CloudTalk or JustCall brings its own numbers.

What does an AI voice agent for outbound calls cost?

On September 30, 2026, published rates range widely. Bland AI lists 0.14 and 0.12 US dollars per minute on its two self-serve plans, Retell AI 0.07 to 0.31 per minute, and Vapi 0.05 per minute of hosting plus model and voice costs at provider cost. CloudTalk bundles start at 99 euros for 200 minutes, Plura AI’s Multi plan is 5,000 US dollars a month, and Synthflow’s enterprise contracts start at 30,000 US dollars a year. PolyAI, Regal and Convoso do not publish a rate on the pages read, and neither does indigitall.

Which platform fits a small team with no developers?

The answers point to Synthflow for no-code campaigns, though its campaigns sit on an Enterprise plan. A business phone system such as CloudTalk or JustCall is the other route, with the agent inside a product that already has numbers and CRM sync.

Can indigitall place outbound voice calls?

Its AI voice page describes outbound conversational voice as a channel in the customer journey, triggered by a journey step or a churn or no-show prediction. The page does not describe consent, Do Not Call screening, calling hours, AI disclosure or voicemail detection, and it publishes no price. Those are the first things to ask, as with any vendor here.

Why are some platforms not in the comparison?

A mention in a live answer is not enough to establish a product’s architecture or outbound capability. Names that appear without a public page that shows how they place calls are listed without a card.

How should you test a platform before a full campaign?

Start with a small list of numbers that have consented, run every control from the ten questions above against it, and check the results in the platform’s own call history. Where the documentation allows it, test voicemail and menu behavior without dialing, and read the terms next to the product page before the first real call.

About the Authors