Skip to content
AI calling

AI cold calling: what works, what doesn't, and where the legal lines sit

Short, scripted calls with a clear exit work. Pretending to be human, arguing past a no and calling without consent do not. Here is the honest version, compliance included.

Abstract contour lines in deep blue, used as the cover for a post on AI cold calling

What AI cold calling really means on a campaign floor

AI cold calling gets sold as a robot that rings strangers and makes sales. On a US campaign floor it is narrower and more useful than that: a bot that takes the calls your dialer connects, qualifies the person who answers and hands the good ones to a licensed closer. Plenty of people search for cold calling AI hoping for a closer in a box. That is not what works today, and this post explains why.

One point changes the whole conversation, so it comes first. In the US, the word "cold" does a lot of damage. Most calls your floor makes should not be cold in the legal sense at all. They should go to people who gave consent, through a web form, a lead vendor or an existing relationship. A bot calling a truly cold list with an artificial voice is a legal problem before it is a sales problem. More on that below.

What works in AI cold calling

Short, scripted calls with one goal. The calls that work are the ones a good fronter could do half asleep: a disclosure, four to eight questions, a transfer. The bot reads the same opener on call one and call nine hundred, and that is exactly where human floors lose quality late in the shift.

  • An opener that says who is calling and why in the first sentence, not a fake "Hi, how are you today?"
  • One question per turn, so every answer is clean
  • A small set of approved rebuttals for the objections you hear daily: "I'm busy," "How did you get my number?" and "Is this a sales call?"
  • A fast, polite exit for anyone who says no or asks to be removed
  • A warm transfer where the bot introduces the caller to the closer before dropping off

Volume at hours your floor finds hard

US daytime is night in Pakistan and India. Bots hold the same pace through the last hours of the shift, when human transfer rates usually sag. If you have read why transfer rates drop after hour six, this is the fix that does not need a fresh team at 1 a.m.

Consistent wording is the other quiet win. A bot reads the disclosure exactly as approved. That does not make a call compliant by itself, but it removes the most common failure we hear about, which is an agent shortening the wording because they have said it four hundred times.

There is a third, smaller win. Every call is recorded and transcribed, so when a buyer or a carrier disputes a transfer weeks later, you can find the call by number or phrase instead of asking a team lead to remember it. On a floor that sells leads, that proof is worth money on its own.

What doesn't work, whatever the vendor

Some approaches fail on every floor, regardless of whose bot is running. If a vendor's demo leans on any of these, be careful.

Most of these come from the same instinct: treating the bot as a way to squeeze more out of a list. It works better the other way round. Give it a clean, consented list, a short script and a narrow goal, and it will do that job the same way all night. Ask it to be clever and it will be clever in ways you never approved.

  • Pretending to be human. Callers often work it out within a sentence, a caller who feels tricked does not transfer, and in some places it may also break the rules
  • Long, open sales conversations. Qualifying for a transfer is fine. Trying to close a final expense policy over fifteen minutes with a nervous 70-year-old is not where the technology or the licensing rules are
  • Arguing past a no. Two rebuttals is plenty. After that you are producing complaints, not transfers
  • Bad data. AI does not improve a stale or scraped list. It dials it faster
  • Clever openers. Anything that sounds like a trick, such as "this is about your recent inquiry" when there was none, is a complaint waiting to happen

Read this section twice, then hand it to your compliance counsel. I am not a lawyer, the rules differ by state and they change. What follows is the shape of the problem, not legal advice.

The Telephone Consumer Protection Act restricts calls that use an artificial or prerecorded voice, and calls made with certain automated systems, especially to mobile numbers. In 2024 the FCC said that AI-generated voices count as an artificial voice under the TCPA. The practical reading most counsel give is that an AI voice making a marketing call needs the right prior consent, and for telemarketing that usually means prior express written consent. The TCPA glossary entry and our longer guide to TCPA basics for offshore floors cover the terms.

Consent is where offshore floors get hurt. The lead was bought, the vendor said it was consented, and nobody kept the record. If a consumer sues, "the vendor said so" is a weak answer. Keep the consent record for each lead: where and when it was given, the wording the consumer agreed to, and which company it named. Our note on what consent means for a calling floor goes further.

Then come the other layers: the National Do Not Call Registry, your internal DNC list, state calling hours, state telemarketing laws with their own rules, and campaign rules such as Medicare marketing guidance. A bot removes none of these. It can only make the parts of the call it touches consistent.

Should the bot say it is AI?

Several states have passed or proposed rules on disclosing AI in calls, and the federal picture is still moving. The safe default most counsel suggest is to disclose: say early in the call that the person is speaking with an automated or AI assistant, and never let the bot claim to be a named human.

In practice, disclosure costs less than floors fear. A caller who hears "I'm a virtual assistant calling on behalf of..." and stays on is a caller who chose to stay. The ones who hang up straight away were unlikely to survive the transfer anyway. Get the exact wording from your counsel, then put it in the script so it is read on every call.

Keep the disclosure short and plain: the company, the reason for the call, and one sentence saying the caller is talking with an automated assistant who can connect them to a licensed agent. A long legal paragraph at the top of a call loses people faster than the disclosure itself does. If your counsel needs more wording, ask whether all of it has to come in the first sentence.

A pre-launch checklist for AI cold calling

Before a bot dials a single lead, every line below should be a yes. Print it, and have your compliance person sign it rather than your sales manager.

  • Every lead on the list has a consent record you can produce within a day
  • The consent wording covers calls using an artificial or AI voice, as your counsel reads it
  • Numbers are scrubbed against the national registry, relevant state lists and your internal DNC list before the dial
  • Calling windows are enforced by state, in the dialer, not by hand
  • The opener names the company and the purpose, and discloses AI in wording your counsel signed off
  • Removal requests end the call and are marked DNC, with the recording kept
  • Recordings and transcripts are kept for as long as your counsel and your buyer require
  • Someone reviews a sample of calls every day in week one, including the ones that ended badly

Honest limits, and where we fit

AI cold calling will not save a campaign with weak consent or a thin closer queue. It will not close licensed products. What it will do is get the scripted front of the call done the same way every time, through the night, and leave a recording and a transcript of each one.

It is also worth being clear about what a bot will not do for your compliance. It will not check consent, it will not scrub your list and it will not decide which states you may call at what hour. Those stay with your data process, your dialer and your counsel. A vendor who says otherwise is either confused or promising something it cannot back up.

B3 Voice builds fronter and verifier bots for exactly that part. They read your disclosure, mark do-not-call requests on the call and write a disposition for every outcome. Consent and registry scrubbing stay with you and your dialer. If that split matches how you work, the fronter bot page shows the flow end to end.

Share
All posts
Questions

About this topic

It can be, with the right consent and controls, but it is heavily regulated. The FCC treats AI-generated voices as artificial voices under the TCPA, so consent requirements apply, and state laws add their own rules. Have your compliance counsel review your consent language, scripts and lists before you launch.

On short, scripted qualification calls it is more consistent, especially late in a night shift when people tire. On long, emotional or unusual conversations a skilled human still does better. Most floors get the best result by letting bots front and verify while licensed humans do the closing.

Rules vary by state and are changing, so check with your counsel. The safe default is to disclose early in the call and never let the bot claim to be a named person. In practice disclosure rarely hurts transfer quality, because the callers who stay on have chosen to keep talking.

Ours does not. Registry scrubbing and your suppression lists belong in your dialer or data process, before the dial. Our bots handle the removal requests made during the call: they confirm the request, end the call politely and mark the number as do-not-call so it can be suppressed.
WhatsAppCall us7 daysFree trial