AI outbound calling is automated outbound calling with a voice agent on the line: software places the call, talks with whoever answers, completes a task on that call and records the outcome. In a contact center, an AI outbound calling system works through the confirmation, reminder and follow-up lists your team never finishes, and it transfers the call to a person when the conversation needs one.
Most writing on the subject is aimed at developers building a voice bot from scratch or at sales teams chasing cold leads. This guide is for people who already run their company's contact center and have a dialer and a team in place. It covers the parts an AI-powered outbound calling system needs, what the agent does on each call, which calls to give it first, what it will not do, and the federal rules it has to follow, including the opt-out changes that take effect on November 25, 2026. If you are still working out which kind of AI your center needs, what AI agents handle in a call center covers the inbound side and the three different products sold under that name.
What is AI outbound calling?
AI outbound calling uses an automated voice agent to dial a number from a list or a trigger, speak with the person who answers, complete a defined task such as confirming an appointment or qualifying a lead, and log the result. Unlike a recorded message, the agent listens, answers questions and responds to what the person says.
It differs from the outbound tools most centers already run in two ways:
- A predictive or power dialer paces calls from a list and connects the answered ones to a human agent, but the dialer itself never speaks. An AI agent does the talking.
- A recorded broadcast plays the same audio to everyone. An AI agent holds a two-way conversation, so the person can reschedule, ask where to park or say they want to speak to a human.
That changes what you manage. Dial rate stops being the main number to watch, and your attention moves to the script, the rules for when the agent hands off, and the queue of outcomes that someone on your team has to work.
For the person who answers, a conversation with an AI agent is a different experience from a robocall. US law still puts it in the same category: the FCC counts an AI-generated voice as an artificial voice, so the consent, identification and opt-out rules for prerecorded calls apply to it, as the rules section below sets out.
What does an AI outbound calling system include?
The voice agent gets most of the attention, but it is one of eight parts in an AI outbound calling system. Check each part on its own when you compare platforms or plan a build, because a gap in any of them turns into manual work for your team. The last column is the question that shows how a given platform handles that part.
| Part | What it does | What to ask |
|---|---|---|
| Numbers and caller ID | Sets the number people see when you call, and the number your team sees on a transferred call | Which number do outbound calls come from, which countries can it call, and on a transfer does your team see the customer's number or the agent's? |
| List and CRM sync | Decides who gets called and puts each result back on the record | Can a change in your CRM trigger a call, or only an uploaded list? Where does each result land, and in what form? |
| Dialing and retry rules | Decides when calls go out and what happens to the numbers nobody reached | Does anything call an unreached number again on its own, or does your team or your own system decide who is called again and when? |
| Opt-outs and do-not-call | Records a request not to be called and keeps that number off every later call | When someone tells the agent to stop calling, which outcome does the call get, and does the number come off every list you call from? |
| The voice agent | Holds the conversation and completes the task the call is for | Can the script use details your system sends with each call, such as a first name or a pickup time? Which languages does it speak? |
| Transfer to a person | Hands the call to your team when the conversation needs one | Who sets the transfer rules, where does the call land, and does the person who picks up get the conversation so far? |
| Follow-up texts | Reaches people by text, alongside a call or instead of one | Can the voice agent send a text itself, or is texting a separate channel with its own setup and price? |
| Outcomes and reporting | Shows what happened on each call and across the whole program | Is every call recorded, transcribed and tagged with an outcome, and can you see pickup and transfer rates by day? |
Most of the planning sits in three of those rows: who gets called again, who gets a text and who is never called again. Settle all three before the first campaign, and decide which outcome tags put someone on each list. If nobody owns the retry rules, the people you missed stay in the dashboard as tagged calls and nobody tries them again. If nobody owns opt-outs, a request to stop calling sits in a transcript while the number stays on your list.
How an AI-driven outbound call works, step by step
An AI outbound call runs through the same six stages every time: a trigger, a dial inside your calling window, an opening, the conversation itself, a write back to your systems, and an outcome tag. At each stage you decide how your own systems connect and where your team takes part.
- A trigger starts the call. You either upload a contact list and run it as a campaign, or your own systems call an API when a record changes, for example when an appointment is booked or a lead comes in. Trigger-based calling is usually the better choice, because the call goes out while the reason for it is still current.
- The call goes out inside your calling window. You set the days and hours when calls are allowed, and nothing dials outside them.
- The agent opens with your script, saying who is calling, why, and what it needs from the person. No other line in an outbound program affects results as much as the opening, so write it yourself instead of accepting a template.
- The agent handles the conversation. It asks your questions, answers theirs from your knowledge base and completes the task the call is for, whether that is a confirmation, a reschedule, a cancellation, a qualification or a booking.
- It writes the change back. When your scheduling or CRM system is connected, a reschedule or booking goes straight into the record in that system, so nobody has to retype it from a note.
- It ends the call and tags the outcome. Every call is recorded, transcribed, summarized and tagged, so the next morning your team works from a list of outcomes rather than a list of calls. A request not to be called again needs a tag of its own, because that tag is what takes the number off your list.
When a call needs something the agent should not handle, it transfers the call to a number you choose, under rules you set. Find out whether that transfer arrives with a briefing or cold, because it changes what your team does in the first few seconds after picking up.
Which outbound calls should you automate first?
Start with one call type rather than your whole outbound operation. The best first candidate has high volume, follows the same path every time, has one clear outcome and still works if the call ends in a transfer to a person.
Score your own call types against these four criteria. The scores are a way to choose a starting point, not a benchmark:
| Criterion | What good looks like | Why it matters |
|---|---|---|
| Volume | Enough calls a week that finishing the list is currently a problem | Low-volume programs never produce enough calls to tune the script |
| Script stability | The call follows the same path almost every time | Calls that branch or need judgment take longer to build and still end in transfers |
| Single clear outcome | You can name the one thing a good call produces | Outcome tags are of little use if nobody agrees on what a successful call looks like |
| Safe to hand off | A transfer to a person is an acceptable ending rather than a failure | Keeps a person on the calls where the relationship itself is what matters |
Applied to the call types most contact centers already run, the criteria sort out like this:
| Outbound call type | Fit | Notes |
|---|---|---|
| Appointment and delivery confirmations | Strong | High volume, repetitive and with a clear outcome, which makes this the usual first program. See confirmations and reminders, and start from a confirmation call script with a line for every answer. |
| Reminder calls before a visit, pickup or service window | Strong | The same pattern as confirmations; the main value is the reschedules they catch |
| New lead follow-up | Strong | On the first contact, speed matters more than polish, and interested people transfer to your team. See outbound campaigns. |
| List calling to reactivate or re-engage | Good | Works well when the ask is simple and the list is clean |
| Satisfaction surveys after a visit or a closed ticket | Good | Short, scripted and the same every time, and the answers themselves are the outcome |
| Collections and payment reminders | Careful | Extra rules apply and mistakes are costly, so do not make this your first program |
| Cold calls to a purchased list | Only with written consent | A sales call in an AI voice needs the prior express written consent of each person called (see the rules below) |
| Retention and save calls | Weak | These calls depend on judgment, negotiation and an existing relationship, so keep them with your people |
| Complaint and escalation follow-up | Weak | The customer has already been let down once, so a person should make this call |
A good first program is usually the list your team already fails to finish, rather than the list that would be most impressive to automate.
What AI outbound calling does not do
Vendor pages say little about limits. The ones below change how you design a program, so get a straight answer on each before you build. Planning around them costs less than finding them in production.
- If nothing calls an unreached number back on its own, or the redials you set have run out, an unreached call is only a tagged outcome in the dashboard until someone on your team decides what happens next.
- Some setups identify voicemail from the transcript after the call instead of detecting it while dialing. Ask which you have, and plan your outcome tags around it.
- On a plain transfer, the person who picks up gets the call without a briefing or the conversation so far, and has to open the recording, transcript and summary to catch up.
- If the agent has no outcome for a request to stop calling, that request stays in a transcript and the number stays on your list. Ask how a spoken opt-out is recorded and how soon it reaches your do-not-call list.
- If the voice agent cannot send a text, a written confirmation is a separate SMS program that you set up on purpose.
- The agent writes only to the systems you connect. A system that is not connected does not get updated.
- It does not have to take every call. Give it the call types where it is strong, route the rest to your team and judge the program on the calls you gave it.
What rules does outbound AI calling have to work inside?
In the United States, calls that use an AI-generated voice are treated as artificial voice calls under the Telephone Consumer Protection Act. The FCC said so in a February 2024 Declaratory Ruling, so these calls need the prior express consent of the person called unless an emergency purpose or an exemption applies.
In that ruling, the Commission confirmed that the TCPA's restrictions on the use of "artificial or prerecorded voice" encompass current AI technologies that generate human voices (FCC 24-17, CG Docket No. 23-362, released February 8, 2024).
The same ruling goes on to the rest of the robocall rules. Every artificial or prerecorded voice message has to identify who is responsible for the call, a telemarketing message also has to offer a way to opt out, and the FCC wrote that these requirements "are applicable to any AI technology that initiates any outbound telephone call using an artificial or prerecorded voice to consumers." These are the federal rules an AI outbound program runs into most:
| Rule | What it requires | Source |
|---|---|---|
| Consent for sales calls | A call that includes an advertisement or is telemarketing, made in an artificial or prerecorded voice, needs the prior express written consent of the person called. The rule lists a few exceptions, such as some health care messages | 47 CFR 64.1200(a)(2) and (a)(3) |
| Who is calling | At the start of the message, the name of the business responsible for the call, as it is registered with the state. During or after the message, a telephone number for that business | 47 CFR 64.1200(b)(1) and (b)(2) |
| Opt-out on telemarketing calls | An automated voice or key-press opt-out, with brief instructions, within two seconds of that identification. Using it records the number on the caller's do-not-call list and ends the call | 47 CFR 64.1200(b)(3) |
| Calling hours | No telephone solicitation to a residential subscriber before 8 a.m. or after 9 p.m., local time at the called party's location | 47 CFR 64.1200(c)(1) |
| National Do Not Call Registry | No telephone solicitation to a residential number on the registry. A registration lasts until the person cancels it or the number is removed | 47 CFR 64.1200(c)(2) |
| Honoring opt-outs | A person may revoke consent by any reasonable method, and the caller honors it within ten business days. A telemarketer records a do-not-call request when it is made and honors it within the same ten business days | 47 CFR 64.1200(a)(10) and (d)(3) |
Abandonment limits, ring time and the other rules that cap how fast a dialer may call apply as well, and the outbound call center guide cites each of them clause by clause.
What changes for opt-outs on November 25, 2026?
The FCC adopted new revocation rules on September 30, 2026, published them on October 26 and set them to take effect on November 25, 2026 (FCC 26-67, 91 FR 67214). Two of the changes matter for an AI outbound program:
- You may name one exclusive way to opt out. The choices are an automated voice or key-press opt-out on the call, a reply text using a standard word such as "stop," or a website or phone number you designate, and you have to disclose the method clearly on the call or in the text. A caller that names none keeps processing requests made by any reasonable means. Either way, the ten-business-day limit stays.
- An opt-out can be narrower. A request made on an informational call, meaning one with no advertising or telemarketing, can be treated as covering only that category of informational calls. The FCC's own example is a customer who opts out of payment reminders: the rule being replaced would also have stopped that caller's fraud alerts and appointment reminders, and the new one does not have to. A request made on a telemarketing call still covers all of that caller's telemarketing calls.
For an outbound program, all of this has five practical consequences:
- Consent is your responsibility rather than your vendor's. You own the list, so you own the basis for calling it, and the standard you already apply to your team's outbound calls applies here too.
- Set your campaign's calling window narrower than the federal 8 a.m. to 9 p.m. range in the table.
- Put the identification in the opening line. The agent names your business as it is registered and gives a number people can call back, and if you designate an opt-out method, the opening is a natural place to say what it is.
- Give opt-outs an outcome of their own. Someone who wants no more calls may simply tell the agent so. Tag that request, send it to your do-not-call list the same day, and keep any manual step well inside ten business days.
- Disclosure rules may get stricter. In September 2024 the FCC proposed requirements for AI-generated calls, including disclosure to consumers, and that proceeding is still a proposed rule rather than a final one (Federal Register, CG Docket No. 23-362, FCC 24-84). Having the agent identify itself at the start of each call costs nothing and is a reasonable step to take now.
This section summarizes public FCC material and is not legal advice. States add their own requirements, so have your counsel review the script and the list policy before the first campaign runs.
How to launch your first AI outbound program
Once you have picked a call type, most of the build is decisions you make rather than technology you configure. The eight steps below are in the order that usually works, and most of the risk is in the first three.
- Pick one call type using the scorecard above, and write down the single outcome that counts as success.
- Write the opening and the ask yourself. The first thirty seconds of the script have more effect on results than anything else, and you can adjust the rest as you go.
- Decide the handoff rules before you build. Name the situations where the agent stops and transfers the call, such as a request to speak to a person, someone who is upset, or a request for an exception to your policy.
- Clean the list and set the window. Confirm your basis for calling, then set calling days and hours that are narrower than the legal limit. The outbound program spec sheet lists the suppression and attempt rules worth settling at the same time, along with the rules themselves cited clause by clause.
- Connect your system of record. If reschedules cannot be written back to your scheduling system, your team will have to retype them from transcripts.
- Test on your real call types before any live call, whoever builds the agent, and let nothing go live until you have approved it. Several tests from the conversational AI test set for customer service apply to outbound too, especially asking for a person in the first sentence and reading back names and numbers.
- Run a small batch first and listen to the recordings themselves rather than relying on the summaries. The first fifty calls will tell you more about your script than any dashboard.
- Work through the outcomes before you expand. For each call type, track completions per contact, the transfer rate, the opt-out rate and how much of the list ends with a final outcome. The outbound disposition code starter set shows how to map the agent's outcome tags onto the codes your reports already use. Once the tags are reliable and the transfer rate is where you want it, add the next call type.
Each team or department can have its own workspace, with its own agents, numbers and reporting, so one team's results stay separate from another's.
How Telvana runs an outbound program
This is how our platform handles the parts above, as it ships today:
- Each agent places calls from its own phone number. Calls placed through the API go to +1 numbers (the US and Canada), and on a transfer you choose whether your team sees the customer's number or the agent's.
- A call starts from a contact list run as a campaign, or from your own systems through the API, with a signed webhook returning each result. In GoHighLevel, a tag or pipeline stage can trigger the call and the outcome lands back on the contact; HubSpot gets a note with the call summary.
- Campaigns call only inside the days and hours you set, in the campaign's time zone, and can leave out weekends. A campaign calls each contact once unless you turn on "Call multiple times until answered." Then a contact who does not answer, is busy or reaches voicemail is called again, up to five calls in all, one to six hours apart (on some numbers, only voicemail brings a redial). Voicemail is identified from the transcript after the call.
- A GoHighLevel trigger can ask for one redial, placed ahead of the other waiting calls, when the call is not answered, is busy or reaches voicemail while calling hours are still open. A call request through the API gets one attempt (outbound call docs), so for those calls your system decides who is called again.
- In the workspace settings you can turn calls off, set a schedule of pauses in Eastern, Central, Mountain or Pacific time, and pause on US federal holidays. A call that comes up during a pause waits and goes out when the pause ends. While calls are off, new API and GoHighLevel calls are refused, and calls already waiting stay queued.
- Each workspace keeps its own do-not-call list, checked before every outbound call. Campaigns, test calls and list imports leave its numbers out, and API and GoHighLevel calls to them are refused. Turn on "Do-not-call detection" for an agent (it is off by default), and when someone asks not to be called again, the call is tagged Do Not Call and the number goes on the list. You can add numbers by hand, and only an admin can take one off. It is your workspace's own list: Telvana does not check numbers against the National Do Not Call Registry, and a STOP reply to a text does not add the number to it.
- The agent follows the script you approve for each call type, uses the details your system sends with the call, answers from your knowledge base and speaks English or Spanish. Our team builds and tests it on your call types, and nothing goes live until you approve it.
- Transfers are plain transfers to the number you choose, under rules you set, and each one is tagged with why it was handed off.
- The voice agent does not send texts. Texting is a $20 a month add-on per workspace: SMS campaigns to a contact list, plus an SMS agent that replies to people who text your number.
- Every call is recorded, transcribed, summarized and tagged with an outcome such as booked, transferred, voicemail or needs follow-up, and analytics show volume, talk time, pickup and transfer rates by agent and by day.
- Pricing starts at $399 a month based on your call volume, plus a one-time setup fee that covers building, testing and launching the agent (pricing).
Frequently asked questions
Is AI outbound calling legal?
Under the FCC's February 2024 ruling, calls using an AI-generated voice are treated as artificial voice calls under the TCPA. In the United States they generally require the prior express consent of the person called, and written consent for telemarketing, unless an emergency purpose or exemption applies. They also have to identify the business calling, and opt-outs have to be honored within ten business days. State laws add their own requirements, so have your counsel review your script and list policy.
Is an AI outbound call a robocall?
In law, yes. The FCC's 2024 ruling treats an AI-generated voice as an artificial voice under the TCPA, so the call needs consent and has to identify who is calling, and a telemarketing call also has to offer an automated opt-out. On the phone it behaves differently from a recorded message, since the person can talk back and ask for a human.
Can an AI agent cold call a purchased lead list?
Not without consent. A telemarketing call in an artificial voice needs the prior express written consent of the person called, and an AI voice counts as artificial under the FCC's 2024 ruling. Check what consent came with every number on the list, and have your counsel review it before anyone dials.
How is outbound calling with AI different from a predictive dialer?
A dialer places calls and connects the answered ones to a human agent, so you still need an agent for every conversation. An AI outbound agent holds the conversation itself and involves a person only when the call meets one of your handoff rules. You can run both, with the AI taking the repeatable programs. The full comparison, including the agent count a predictive dialer needs per campaign before its pacing forecast is reliable, decides which programs go where.
What happens when nobody answers?
The call ends and is tagged with its outcome in your dashboard. Whether the number is tried again depends on your redial rules. In Telvana, a campaign with "Call multiple times until answered" turned on calls the person again after the gap you set, up to the number of calls you chose, and a GoHighLevel trigger can ask for one redial. Otherwise nothing dials the number again on its own, and your team sees who was not reached and decides whether to call again, switch channels or leave it.
What happens when someone asks the AI agent to stop calling?
That depends on how the platform records the request. In Telvana, an agent with do-not-call detection turned on tags the call Do Not Call and puts the number on your workspace's do-not-call list, which every later campaign and API call checks. Detection is off by default, so turn it on before the first campaign, and add requests that reach you another way, such as by text or email, to the list yourself. Numbers aren't checked against the National Do Not Call Registry, so check telemarketing lists against it before you upload them.
Can the AI transfer a call to my team?
Yes. When the conversation meets a rule you set, the agent transfers the call to a number you choose. It is a plain transfer, so the person who picks up should open the call record for the recording, transcript and summary.
Does it text people after the call?
Ask before you count on it. On some platforms texting is a separate channel with its own agent and campaigns, so a written confirmation after a call is something you set up on purpose rather than something the call does by itself.
What does AI outbound calling cost?
Platforms charge per minute, in minutes bundled into a plan, or under a contract or monthly price sized to your volume, and the per-minute rates on different pricing pages do not cover the same components. How AI voice agent platforms charge turns any quote into a cost per contact. To judge the cost, compare it with the fully loaded hourly cost of the staff who work the same list today, or with an outside provider's quote if you are weighing one: call center outsourcing against AI agents sets out how each is priced and includes a scorecard for deciding per call type.
See it run on your own call list
Bring the outbound list your team never finishes. On a demo we will show you how Telvana would work it, what it would hand back to your team and where it would stop. Book a demo.