Is B2B Outbound Calling Legal? The Rules That Still Apply

TL;DR: B2B outbound calling is legal in the US, and the reason is narrower than most teams think. The FTC’s Telemarketing Sales Rule carries an express exemption for calls between a telemarketer and a business to induce that business to buy, so the whole TSR machine of disclosures, calling-hour limits and registry scrubbing drops away, with two exceptions that stay live: the misrepresentation prohibitions, and calls selling nondurable office or cleaning supplies at retail. The FCC said the same thing about the registry in its 2003 order at 68 FR 44144, that the national do-not-call rules do not prohibit calls to businesses. Then it added the trap in the same paragraph, because it presumes wireless subscribers who register to be residential subscribers, and a business cell phone is a wireless number. The rule that does not care at all whether the line is business or residential is 47 CFR 64.1200, which bars an autodialer or an artificial or prerecorded voice to any number assigned to cellular service without prior express consent, and requires prior express written consent when the call is an advertisement or telemarketing. Your list-based power dialer is almost certainly not an autodialer under that rule, because the regulation defines one by a random or sequential number generator and the Supreme Court read it that way in Facebook v. Duguid on April 1, 2021. A dropped prerecorded voicemail to a mobile number is a different story. So the operator answer is this: call business lines, scrub mobile numbers against the registry and your own suppression list anyway, keep the recorded voice off cell phones without written consent, honor an internal do-not-call request inside ten business days, and check the state layer, which is where the real exposure sits in 2026.

What makes B2B outbound calling legal in the first place

Start with the thing most compliance pages get backwards. There is no federal statute that makes an outbound call to a business lawful. The two federal rules that govern outbound sales calls were written around a residential telephone subscriber, and the question of whether B2B outbound calling is legal is really a question about who answers the phone on the other end. When the called party is a business, most of the rule book stops applying by its own terms. That is an exemption, not a permission slip, and exemptions have edges.

Two rule sets do the work. The FTC enforces the Telemarketing Sales Rule, which is where disclosures, calling hours, abandonment limits and registry scrubbing live. The FCC enforces the Telephone Consumer Protection Act rules in 47 CFR 64.1200, which is where consent, autodialers, prerecorded voices and the do-not-call registry live. They overlap, they are not identical, and the business exemption in one is not the business exemption in the other. Teams get burned when they read a summary of one and assume it covers both.

So the useful frame is not “is outbound calling allowed.” It is “which of these four things is true of the number my rep is about to dial”: is it a business line or a personal line, is it wireline or wireless, is a human dialing it or is a recording going to play, and has anyone at that company already told us to stop. Each one moves the answer. For the consumer-side version of this question, the general rules in our guide to when these calls are illegal still apply in full, because nothing below carves out a consumer.

The Telemarketing Sales Rule exempts B2B calls with two carve-outs

This is the load-bearing fact and it is one sentence in the regulation. The Telemarketing Sales Rule exempts telephone calls between a telemarketer and any business to induce the purchase of goods or services, or a charitable contribution, by that business. Not a judicial gloss, not FTC guidance. The exemption is in the text of the rule itself.

A wide flat slab of frosted translucent glass on a pale violet ground with two wedge-shaped notches cut from its near edge, the two removed glass wedges resting separately below it

Then the same sentence names what survives, and this is the part that gets skipped. The exemption does not reach the rule’s misrepresentation prohibitions. Your rep still cannot misstate the total cost to buy or use what you sell, the quantity, any material restriction or condition on the offer, any material aspect of how the product performs or what it actually does, or any material aspect of your refund, cancellation, exchange or repurchase terms. Claiming an affiliation, endorsement or sponsorship you do not have is in the same list. And the separate prohibition on making a false or misleading statement to induce any person to pay for goods or services applies to any person, which includes a buyer at a company.

Read that as an operating constraint, not a legal footnote. The script is the compliance surface. If a rep says the contract cancels any time and it does not, or quotes a monthly price that excludes a mandatory platform fee, the B2B exemption does nothing for you. That is the one place where a B2B outbound call and a consumer outbound call carry identical exposure.

The second carve-out is narrow and oddly specific. Calls to induce the retail sale of nondurable office or cleaning supplies do not get the exemption. It exists because of a decades-old toner and paper fraud pattern aimed at office managers. If you sell consumable office or cleaning products into businesses by phone, you are inside the full rule, not outside it. Everyone else is outside it.

The national Do Not Call registry and your B2B call list

The registry rule in 47 CFR 64.1200 bars a telephone solicitation to a residential telephone subscriber who has registered the number. The FCC was explicit about the boundary when it built the registry. In the 2003 order implementing the TCPA it wrote that the national do-not-call rules will not prohibit calls to businesses, alongside calls to people with whom the marketer has a personal relationship.

So a clean B2B list of main lines and desk extensions is not a registry problem. Fine. Now ask the question the dashboard cannot answer: how many numbers on that list are actually mobile numbers belonging to a person? Sales data vendors sell direct dials, and a direct dial for a VP of operations is frequently their cell. A twelve-person contracting company is often a sole proprietor’s mobile and nothing else. Nobody labels those rows for you.

That is why the practical standard is wider than the legal one. Scrub the list against the national registry and against your own suppression records before the dial, including the mobile numbers, because the cost of scrubbing a row is nothing and the cost of guessing wrong on a registered personal cell is a per-call claim. If you want the registry rule itself, honored registrations last indefinitely, and the error safe harbor rule in that section requires written procedures, trained personnel, a maintained internal list, and a version of the registry obtained no more than 31 days before the call. Thirty-one days is the operating number. Put the refresh on a calendar, not in someone’s memory.

Kixie’s Compliant Caller supports checks against the National Do Not Call Registry and your internal suppression lists on the dialing path, so the check runs against the list rather than against a rep’s judgment in the moment. Customers remain responsible for their own calling practices and legal review. The point is where the check sits: a suppression rule that lives in a spreadsheet gets skipped on a busy Tuesday, and a suppression rule that lives in the dialer does not.

Business cell phones are where B2B outbound calling gets expensive

Here is the sentence that should change how you build lists. In the same 2003 order, the FCC said that because deciding whether a particular wireless subscriber is a residential subscriber is more fact-intensive than making that call for a wireline number, it will presume wireless subscribers who ask to be put on the national do-not-call list to be residential subscribers. The Commission added that a complaining wireless subscriber may have to provide further proof of that presumption in an enforcement action, but the presumption is the starting point.

A long diagonal file of plain frosted glass cards on a pale violet ground with three magenta tinted cards hidden in the middle of the stack, revealed under a large frosted glass magnifier

Walk the consequence through your queue. Your rep is calling a cell number that the person treats as their work phone. That person registered it years ago on a personal plan. On the registry’s own terms the number presents as residential, and your B2B framing of the account is not visible to anyone reviewing the complaint. You are arguing about the character of the line after the fact instead of having scrubbed it before the dial.

Then there is the rule that skips the residential question entirely, and this is the big one for outbound teams. Nothing in 47 CFR 64.1200 limits the cellular prohibition to residential lines. It bars initiating any telephone call using an automatic telephone dialing system or an artificial or prerecorded voice, without prior express consent, to any number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service, or to any service for which the called party is charged for the call. When the call includes or introduces an advertisement or constitutes telemarketing, the standard rises to prior express written consent. Business cell, personal cell, the rule reads the same.

Does your dialer make a B2B outbound call illegal

No, and the reason is worth knowing precisely, because vendors and compliance consultants both have an incentive to keep it vague.

The FCC rule defines an automatic telephone dialing system as equipment which has the capacity to store or produce telephone numbers to be called using a random or sequential number generator, and to dial such numbers. The Supreme Court read the matching statutory text the same way in Facebook v. Duguid, No. 19-511, decided April 1, 2021: to qualify as an automatic telephone dialing system, a device must have the capacity either to store a telephone number using a random or sequential number generator, or to produce a telephone number using a random or sequential number generator.

A power dialer that advances through a list your team uploaded does not generate numbers randomly or sequentially. It dials records you chose. That is why list-based dialing generally sits outside the autodialer prong, and why “we use a dialer” is not, by itself, a TCPA theory. Two cautions. The autodialer analysis is equipment-specific and is still litigated, so this is the shape of the rule rather than a clearance for any particular configuration. And the autodialer prong is only half the sentence.

The other half is the artificial or prerecorded voice, and it has no generator requirement at all. Drop a recorded message on a business mobile number without prior express written consent and the dialer question never comes up, because the recording triggered the prohibition on its own. Teams that have internalized “our dialer is compliant” walk straight into this with a voicemail campaign. The rules that attach to a recording are the subject of our breakdown of whether Voicemail Drop is legal, and they are the ones to read before any automated voicemail touches a cell number.

Calling hours and do not call requests on B2B calls

The federal 8 a.m. to 9 p.m. window, measured in local time at the called party’s location, is written for telephone solicitations to residential telephone subscribers. On its face it does not reach a call to a business line. Neither does the federal internal do-not-call list requirement, which is also framed around a residential telephone subscriber.

Now be honest about what that buys you. Almost nothing operationally. You are still dialing mobile numbers you cannot classify with certainty, state law frequently sets its own hours, and calling a prospect’s cell at 7 a.m. because the federal window technically does not apply is a strategy for getting hung up on. Run the standard window. It costs you nothing in connect rate, since the buyer is not at their desk at 7 a.m. anyway, and it removes an argument you do not want to have.

Internal do-not-call requests deserve a harder rule than the law requires. Where the federal standard applies, the request has to be recorded at the time it is made and honored within a reasonable time not exceeding ten business days, and the entry stays on the list for five years. Build to that standard across the whole list, business lines included. The reason is not legal, it is operational: a company that told your team to stop calling and gets dialed again next quarter by a new rep working a refreshed list is a complaint, a burned account, and a support ticket. Record the request against the account, not against the single phone number the rep happened to be dialing.

Worth tracking separately, the FCC finished a rulemaking on how consent revocation works that takes effect on November 25, 2026, published at 91 FR 67214. It lets callers treat a revocation as applying to the specific category of informational robocalls it was directed to, lets a caller designate an exclusive means to revoke consent, and amends the fraud-alert exemption for financial institutions. A companion proposal published the same day is taking comment on shortening the window a caller has to honor a revocation. None of it changes the B2B exemption, and all of it changes how you should be logging opt-outs.

State rules that still reach B2B outbound calls

Federal law is the floor, and in 2026 it is not where the risk concentrates. States have passed their own telemarketing statutes, several with private rights of action, their own calling-hour windows, their own consent language and their own registration and bonding requirements for sellers who call into the state. Those statutes do not all borrow the federal business exemption, and some define a covered call by the location of the called party rather than by whether that party is a business.

Three practical consequences. Your calling-hour policy should follow the strictest window among the states you dial into, which is what the state-by-state calling hours breakdown is for. Your registration obligations are a function of where you call, not where you are headquartered. And a state registry is not the federal registry, so check the state do-not-call lists separately rather than assuming the national scrub covered them.

Recording is its own state layer and it catches B2B teams constantly, because call recording consent rules turn on the parties to the conversation, not on whether the account is a business. A recorded sales call with a buyer in an all-party consent state needs that buyer’s agreement regardless of how commercial the conversation is.

Outbound calling to businesses outside the US

The rules follow the called party, not your office. A US team dialing into Canada, the UK or the EU is inside those regimes, and they are built on a different premise. Several treat a named individual at a company as personal data, which means a business card does not function as consent the way US B2B practice assumes. Canada runs its own national do-not-call list with its own exemption structure. The UK runs a corporate preference service that businesses can register on, which has no US analogue at all.

The operating rule is simple even when the law is not. Segment the list by country before the first dial, not after the first complaint, and treat each country as a separate compliance question with separate suppression data. A single global list with one scrubbing step is the failure mode.

A B2B outbound calling compliance checklist

  • Classify every number before it enters a dialing list. Business line or personal line, wireline or wireless, and which state. The rows you cannot classify get treated as the stricter case.
  • Scrub against the national registry and your own suppression records anyway. The business exemption does not require it. The mobile numbers in your list do.
  • Refresh the registry version on a schedule inside 31 days. The error safe harbor rule in the FCC rules is written around that number, together with written procedures, trained personnel and a maintained internal list.
  • Keep the recorded voice off cell numbers without prior express written consent. This is the single most common way a B2B team creates federal exposure.
  • Audit the script against the misrepresentation prohibitions. Total cost, material conditions, what the product actually does, refund and cancellation terms, and any claimed affiliation or endorsement. Those survive the exemption.
  • Log every stop request against the account inside ten business days and keep it five years. Account level, not phone-number level.
  • Set calling hours to the strictest state window you dial into and let the system enforce it rather than the rep.
  • Segment non-US numbers out of the main list and handle each country separately.
  • Record the evidence. Consent source and date, scrub date and registry version, suppression entries, and call outcomes. If a complaint lands six months from now, the only thing that helps is the record you kept at dial time.

Most of that list is a data problem rather than a legal one. Kixie is a sales engagement platform for business calling and texting, and the part of this it addresses is placement: suppression checks and call logging sit on the dialing path, and call, text and outcome records land in the CRM automatically, which is where a compliance record has to live to be worth anything later. The legal judgment stays with your counsel.

B2B outbound calling FAQ

Is it legal to make an outbound call to another business?

Yes, in the US. The Telemarketing Sales Rule expressly exempts calls between a telemarketer and a business made to induce that business to purchase goods or services, and the FCC has stated that the national do-not-call rules do not prohibit calls to businesses. The exemption does not cover misrepresentations in the pitch, and it does not cover calls selling nondurable office or cleaning supplies at retail.

Can sales teams call business cell phones?

Yes, if a rep dials the number by hand and no recording plays. The FCC rules bar calls to numbers assigned to cellular service using an autodialer or an artificial or prerecorded voice without prior express consent, with prior express written consent required when the call is an advertisement or telemarketing, and that prohibition does not carve out business users. The FCC also presumes wireless subscribers who register on the national list to be residential subscribers, so scrub mobile numbers.

Does the National Do Not Call Registry apply to B2B calls?

Not to business lines. The registry rule is written around residential telephone subscribers, and the FCC said in its 2003 implementing order that the rules do not prohibit calls to businesses. The exposure is in misclassified rows, mainly personal mobile numbers used for work, which is why scrubbing the whole list is the cheaper posture.

Does using a sales dialer make B2B outbound calling illegal?

Not on its own. The FCC rules define an automatic telephone dialing system by the capacity to store or produce numbers using a random or sequential number generator and to dial them, and the Supreme Court read the statute the same way in 2021. A dialer that works through a list your team uploaded is not generating numbers. The analysis is equipment-specific, and the separate prohibition on artificial or prerecorded voices applies no matter how the number was dialed.

Do B2B outbound calls have to follow the 8 a.m. to 9 p.m. rule?

The federal window applies to telephone solicitations to residential telephone subscribers, so it does not reach a call to a business line by its terms. State telemarketing statutes often set their own hours and do not always copy the federal business exemption, so run the strictest window among the states you dial into.

How is this different from outbound calling to consumers?

Almost everything is different except the misrepresentation rules and the cellular prohibition. A consumer call sits inside the full Telemarketing Sales Rule and the full registry regime. Industry-specific consumer calling, such as outbound calling in real estate, carries additional constraints that a B2B list does not.

This article is general information about US telemarketing rules and is not legal advice. Rules change and state requirements vary, so confirm your own calling program with counsel.

Sources

Sources verified by the Kixie Research Team on November 18, 2026.

Prior Express Written Consent Is Still Your DNC Exemption

TL;DR: Prior express written consent is defined at 47 CFR 64.1200(f)(9) as an agreement in writing, bearing the signature of the person called, that clearly authorizes a named seller to deliver advertisements or telemarketing messages by automatic telephone dialing system or artificial or prerecorded voice, and that includes the telephone number the signer authorizes. The written agreement has to carry a clear and conspicuous disclosure saying two things: that signing authorizes those calls, and that the person is not required to sign as a condition of buying anything. A signature can be electronic where federal law or state contract law treats it as valid. Two things changed recently and they pull in opposite directions. The Eleventh Circuit vacated the FCC’s one-to-one consent rule, mandate issued April 30, 2025, and the FCC conformed its rules on August 29, 2025 at 90 FR 42137, so the single-seller and logically-and-topically-associated language is gone from the definition. Then on February 25, 2026 the Fifth Circuit decided Bradford v. Sovereign Pest Control of TX, No. 24-20379, holding that the statute at 47 USC 227(b)(1)(A)(iii) requires only prior express consent, oral or written, and that nothing in it supports the FCC’s written-only rule for telemarketing. That decision binds Louisiana, Mississippi and Texas under 28 USC 41. It did not erase the regulation, it did not touch the FTC, and the FTC is the part that matters most to an outbound team, because the Telemarketing Sales Rule at 16 CFR Part 310 still says the only consent route onto a do-not-call registry number is the express agreement, in writing, carrying the number and the signature. Drop the signed record and you do not gain a dialing lane. You lose your registry exemption.

A rep asks whether the list is cleared to dial. Somebody says yes, the leads came from a form. That is where most consent problems start, because the form is not the record and the answer is not a yes until somebody can produce what the person actually saw and actually signed.

The question got harder in the last eighteen months, not easier. One court vacated part of the FCC’s consent definition. Another court said the writing requirement was never in the statute at all. Both of those are real, both are narrow, and neither one is permission to stop collecting a signed record. Here is what the rule says, what the two decisions did, and what has to be in the CRM before a list is actually cleared.

What Prior Express Written Consent Actually Requires

Start with the regulation, because this is a defined term and the definition is short. 47 CFR 64.1200(f)(9) says prior express written consent means an agreement, in writing, bearing the signature of the person called, that clearly authorizes the seller to deliver or cause to be delivered advertisements or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice, and the telephone number to which the signatory authorizes those messages to be delivered.

Four things have to be present. A writing. A signature. A clear authorization naming the seller and the message type. The specific phone number.

Then the rule adds a disclosure requirement on top. Paragraph (i) says the written agreement has to include a clear and conspicuous disclosure telling the person signing that executing the agreement authorizes the seller to deliver telemarketing calls using an automatic telephone dialing system or an artificial or prerecorded voice, and that the person is not required to sign, directly or indirectly, or to agree to the agreement as a condition of purchasing any property, goods, or services.

That second disclosure is the one teams forget. It is not a nice-to-have sentence. It is written into the definition, which means a consent form that gates a download or a quote behind the checkbox is arguing with the rule it is trying to satisfy.

Paragraph (ii) handles signatures. The term includes an electronic or digital form of signature, to the extent that form is recognized as a valid signature under applicable federal law or state contract law. So a checkbox and a submit can work. The word doing the work there is recognized. The question is never whether the click happened. The question is whether you can show which person clicked, on which number, under which disclosure text, at which moment.

Where does the requirement attach? 47 CFR 64.1200(a)(2) is the operative prohibition for mobile numbers. It bars initiating a call that includes or introduces an advertisement or constitutes telemarketing, using an automatic telephone dialing system or an artificial or prerecorded voice, to a wireless number, other than a call made with prior express written consent. Tax-exempt nonprofit calls need only prior express consent, and a health care message from a covered entity or its business associate under the HIPAA Privacy Rule is carved out separately. Paragraph (a)(3) runs the parallel rule for residential lines.

Read it closely and the structure is clear. The statute sets a consent floor. The FCC raised that floor for one category of call. That gap is exactly what the Fifth Circuit went after.

What the Fifth Circuit Changed About Written Consent

On February 25, 2026 the Fifth Circuit decided Bradford v. Sovereign Pest Control of TX, No. 24-20379. Chief Judge Elrod wrote it, joined by Judges Clement and Haynes. The court affirmed summary judgment for the caller.

The facts are ordinary, which is the point. On the record described in the court’s opinion, Bradford signed a service-plan agreement with a pest-control company and wrote his cell number on it. He later said he gave the number in case the company needed to get in contact with him. The company sent prerecorded calls about renewal inspections. He scheduled the inspections. He renewed the plan four times. Then he sued, arguing the renewal calls were telemarketing and that the company never got his prior express written consent.

The court did not resolve whether the calls were telemarketing. It did not need to. It held that the statute requires only prior express consent for any auto-dialed or prerecorded call, whether the call is telemarketing or informational.

The reasoning runs through the text. 47 USC 227(b)(1)(A)(iii) bars a call to a wireless number using an automatic telephone dialing system or an artificial or prerecorded voice unless the call is for emergency purposes or made with the prior express consent of the called party. The court read express consent the way the phrase was understood when Congress passed the TCPA in 1991, citing the sixth edition of Black’s Law Dictionary: consent directly given, either viva voce or in writing, positive, direct and unequivocal. Viva voce means by word of mouth. So Congress permitted oral or written consent, and in the court’s words, the statute provides no basis for concluding that telemarketing calls require prior express written consent but not oral consent.

The court reached the question without deferring to the agency, citing McLaughlin Chiropractic Associates v. McKesson Corp., 606 U.S. 146 (2025), and Loper Bright Enterprises v. Raimondo, 603 U.S. 369 (2024). In an enforcement proceeding, courts read the enacted text with ordinary tools of construction. That is the mechanism that made this decision possible, and it is the part worth tracking, because it applies to every FCC interpretation a defendant wants to test, not just this one.

Now the boundaries, and they matter more than the headline.

The court did not vacate 47 CFR 64.1200(a)(2). The regulation is still printed in the Code of Federal Regulations. What happened is narrower: in a private suit, one circuit declined to apply the agency’s added requirement because the statute does not contain it. Under 28 USC 41 the Fifth Circuit covers Louisiana, Mississippi and Texas. A list is not filtered by circuit. A rep in Dallas dials a number that rings in Atlanta, and the case law that governs that call is not chosen by where the rep sits.

The other limit is scope. The holding is about the consent standard in 47 USC 227(b). It says nothing about the do-not-call rules, nothing about internal suppression lists, nothing about calling hours, and nothing about state law. A sales leader who reads this decision as a green light to stop collecting signatures has read one paragraph of a seven-page opinion and skipped the rest of the regulatory stack.

Why the FTC Rule Keeps Written Consent in Place

Here is the part the litigation coverage mostly skips, and it is the part that should decide what you build.

The FCC is not the only agency with a written-consent requirement. The FTC’s Telemarketing Sales Rule has its own, in a different title of the CFR, enforced by a different agency, and the Fifth Circuit decision does not touch it.

The abusive practices section of that Rule, in 16 CFR Part 310, makes it an abusive practice to call a number on the national do-not-call registry unless the seller or telemarketer can demonstrate one of two things. The first is that the seller has obtained the express agreement, in writing, of that person to place calls to that person. The rule then spells out what that writing has to do: it shall clearly evidence the person’s authorization that calls made by or on behalf of a specific party may be placed to that person, and shall include the telephone number to which the calls may be placed and the signature of that person. A footnote to the part defines signature to include an electronic or digital form, to the extent it is recognized as valid under applicable federal law or state contract law. The second route is an established business relationship.

So what is that provision actually doing? It is not a consent rule for prerecorded calls. It is the exemption that lets a live human being dial a registry-listed number at all. No ATDS required, no prerecorded voice required, no telemarketing-versus-informational argument to have.

So the two requirements sit in different places and do different work. The FCC definition governs the technology you dial with. The FTC provision governs whether you may call that number in the first place. A team that drops the signed record because one circuit narrowed the first one has quietly given up the second one, which was never in dispute and which applies in all fifty states.

That is why the operating answer does not change. Keep collecting the writing. It costs one form field and it covers both rules.

Where Prior Express Written Consent Does Not Reach

Consent is not one switch. It is scoped, and most of the real failures are scope failures rather than missing records. Scoped to what? To a seller, a number, and a message type, and a record can satisfy one of those and fail the other two.

The regulation ties the authorization to a specific seller and a specific number. A consent captured by an affiliate for a different brand does not travel to you because the two companies share an owner. A consent captured on a landline the prospect gave you in 2023 does not cover the mobile number they typed into a different form last month.

It is also scoped by message type. The definition authorizes advertisements or telemarketing messages. A record built for one channel is a weak basis for another, and if the disclosure the person read described calls, a texting campaign is leaning on language that never mentioned texts.

The one-to-one question is a live example of why versioning matters. The FCC adopted a revised definition in 2023 that required consent to name a single seller and that the resulting call be logically and topically associated with the interaction that produced the consent. The Eleventh Circuit vacated that paragraph, the mandate issued April 30, 2025, and the FCC conformed its rules on August 29, 2025 at 90 FR 42137, which removed the vacated language. So a disclosure written to satisfy one-to-one in late 2024 is now stricter than the rule requires, and a disclosure written before 2023 is back in force. Neither is a problem. Not knowing which version a given lead signed is the problem.

State law is the other edge, and it moves independently of both federal rules. Several states run their own telemarketing statutes with their own consent and registration requirements, which is covered in mini TCPA laws by state, and several run their own do-not-call registries that a national scrub never sees, covered in state do not call lists. A federal-only consent posture is incomplete by construction.

Purchased leads deserve their own paragraph. When a lead vendor says the record carries consent, the question is what the vendor can produce: the disclosure text, the timestamp, the number, the parties named. A contractual warranty is not a consent record. The transfer question is worked through in TCPA rules for insurance agents and purchased leads.

What a Written Consent Record Has to Hold

Storage is not the goal. Reconstruction is. If a complaint arrives eleven months from now, somebody has to rebuild the moment of consent from fields, not from memory.

A translucent violet glass bar threaded through three open glass rings of different sizes on a pale violet background, binding them into one piece.

Work backward from the rule text and the fields fall out.

  • The phone number, in full. Both rules name the number explicitly. A consent record that points at a contact instead of a number does not match either provision.
  • The exact disclosure text as displayed. Not a link to the current form. The rendered language that was on screen when the person acted.
  • A version identifier for that text. This is the field most teams skip and the one that makes the timestamp useful. Legal changes the wording, the identifier changes, and every record stays interpretable.
  • The seller named in the disclosure. The entity, not the campaign nickname.
  • The affirmative action and its timestamp. What was clicked or submitted, and when, with the time zone recorded rather than inferred.
  • The source. Page URL, form, campaign, and the vendor if the lead was purchased, plus the vendor’s own evidence for that lead.
  • The message types authorized. Calls, prerecorded calls, texts, separately, matching the disclosure rather than the campaign plan.
  • Revocation state and its own timestamp. Consent is a current state, not a historical event.

One practical test tells you whether this is real. Pick a lead at random, open the record, and try to answer those eight questions without asking anyone. If you need to email marketing operations to find out which form version was live in March, the record is a storage artifact, not evidence.

How Consent Records Break in the CRM

The CRM says the lead is consented. Fine. Consented to what, on which number, under which disclosure text? The record is usually sound on the day it is created. It breaks later, inside normal operations, and the breakage is boring.

Three translucent violet glass chain links on a pale violet background, with the middle link split open and its two broken ends pulled apart so the outer links no longer hold together.

A lead comes in with consent on one number. The rep calls, learns the prospect has a better mobile, and updates the phone field. The consent flag did not move, because it was never tied to the number. Now the record says consented and the number on it was never authorized.

A list gets imported. The import maps a column called opt-in to the consent flag, and every row arrives marked consented with no disclosure, no version, no timestamp. Nothing in the system distinguishes those rows from the ones that came through a real form.

A prospect tells a rep on a call to stop calling. The rep notes it in the call summary and moves on. The suppression list never hears about it, and the number is back in a cadence the following week because the note is prose and the queue reads fields.

A duplicate merges. Two records, one consented and one not, and the merge rule keeps the most recent value on every field. The merge just manufactured consent.

Those four are all the same failure. The consent state lives in a flag, and the flag is not bound to the number, the disclosure, or the revocation. Bind it to the number, carry the disclosure version, and make every write path that touches a phone field either preserve the binding or drop the consent. Dropping it is the safe default for the consent record and costs one re-consent email.

The dialing side needs its own check, and it is independent of the CRM flag. The national registry and your internal suppression list are a separate gate that runs regardless of what the consent field says. Kixie’s National DNC compliance supports checks against the National Do Not Call Registry and against internal suppression lists, and customers remain responsible for their calling practices and legal review. The written agreement under the FTC rule is what lets a registry-listed number through that gate, which is the whole reason the signed record keeps earning its place.

Revocation is the last piece, and it has its own deadlines and its own mechanics under the FCC rules. Those are worked through in when to text prospects instead of calling.

What to inspect this week. Pull a hundred records marked consented, in a dialer or a power dialer list that is about to run, and check three fields on each: the authorized number matches the number on the record, a disclosure version is present, and the revocation field is empty. The percentage that fails is your real consent coverage. Everything above is how to raise it.

Prior Express Written Consent FAQ

Does the Fifth Circuit decision mean written consent is no longer required?

No. Bradford holds that 47 USC 227(b) requires only prior express consent, oral or written, and that one circuit will not apply the FCC’s written-only rule for telemarketing calls in a private suit. 47 CFR 64.1200(a)(2) and the definition at (f)(9) are still in the Code of Federal Regulations, the decision binds only Louisiana, Mississippi and Texas, and the FTC’s separate written-agreement requirement in the Telemarketing Sales Rule is untouched nationwide.

Does a checkbox on a web form count as a signature?

It can. 47 CFR 64.1200(f)(9)(ii) says signature includes an electronic or digital form, to the extent it is recognized as a valid signature under applicable federal law or state contract law, and the FTC rule uses the same formulation. The evidentiary burden is the real work: tie the action to the person, the specific number, and the exact disclosure shown at that moment.

Is consent still required to name one seller at a time?

Not under the current federal definition. The FCC’s 2023 revision added a single-seller requirement and a logically-and-topically-associated requirement, the Eleventh Circuit vacated that paragraph with its mandate on April 30, 2025, and the FCC removed the language at 90 FR 42137 effective August 29, 2025. Naming one seller is still the cleaner record to defend, it is just no longer the rule.

Does a prospect giving a rep their cell number create consent?

It can create prior express consent in some circumstances, which is what the court found on the facts in Bradford, where the number was written on a signed service agreement and the person said he provided it so the company could contact him. It is not the same as prior express written consent under the regulation, and it is not a basis for calling a registry-listed number under the FTC rule.

What is the single operational takeaway?

Bind consent to the phone number rather than to the contact, store the disclosure version alongside the timestamp, and keep collecting the signature. Two federal agencies, two rules, one form field.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 19, 2026.

Time Zone by Area Code Is a Guess, Not a Clock

TL;DR: A time zone by area code lookup resolves cleanly for most of the country and fails quietly for the rest, and the rest is the part that puts a calling program outside the law. The NANPA numbering file dated November 19, 2026 lists 378 US geographic area codes in service. 356 of them carry exactly one time zone. The mainland split runs 168 Eastern, 110 Central, 52 Pacific, 18 Mountain and 3 Atlantic, with five more codes covering Alaska, Hawaii, Guam, the Northern Mariana Islands and American Samoa. 21 carry two. Twelve of those straddle Eastern and Central, six straddle Central and Mountain, three straddle Mountain and Pacific, and they sit in twelve states, with Indiana, Kentucky and Tennessee holding three each. Nevada’s 775 is the 22nd case and the strangest one. The numbering file flags it for a single city, because the federal regulation that draws the mountain and Pacific line routes that line around the city limits of West Wendover. This is not trivia. The federal calling hours rules attach to the clock at the called party’s location, not to yours and not to the area code. The FCC rule bars a telephone solicitation to a residential subscriber before 8 a.m. or after 9 p.m. local time at the called party’s location, and the FTC telemarketing rule sets the same window for calls to a person’s residence. Daylight saving is the second trap. Federal law runs it from 2 a.m. on the second Sunday in March to 2 a.m. on the first Sunday in November, Arizona rejected it by statute, and Arizona’s five area codes carry the same Mountain letter all year while the offset they actually match moves twice. So store the inferred zone in its own field with its source and the date it was last checked, never let it overwrite an address-derived or contact-stated zone, mark the 21 split codes and every nongeographic number ambiguous instead of picking a side, and dial those records inside the window that is legal in every zone they could be in.

A rep opens a list of 400 numbers at 7:15 in the morning and starts dialing. Nothing on the screen says what time it is at the other end. The area code is the only location signal most lists carry, so that is what the rep uses, usually without thinking about it.

Most of the time that works. So what happens on the calls where it does not? The rule that governs when you are allowed to call is written against the buyer’s clock, not against the three digits in front of their number. A time zone by area code lookup is a starting estimate. Treated as an answer, it is how a careful calling program ends up dialing at 7:15 local.

Here is what the numbering data actually supports, where it breaks, and what to store in the CRM so the break does not reach the dialer.

What a Time Zone by Area Code Lookup Can and Cannot Tell You

Start with the source. The North American Numbering Plan Administrator publishes a machine-readable report of every area code, and each row carries a time zone field. That field is the honest version of what an area code knows about the clock.

As of the November 19, 2026 file there are 378 US geographic area codes in service. 356 of them carry exactly one time zone. The mainland split runs 168 Eastern, 110 Central, 52 Pacific, 18 Mountain and 3 Atlantic, with five more codes covering Alaska, Hawaii, Guam, the Northern Mariana Islands and American Samoa.

In that same file, 21 codes carry two time zones. One more, Nevada’s 775, carries a note instead of a zone, because a single city inside it sits on the other side of a federal boundary line.

So the lookup answers the question for roughly nineteen out of twenty codes. That is a good tool. It is not a clock. And the gap is not spread evenly. It concentrates in a dozen states, where the same reps work the same territory every day.

Two more things the area code does not know. A number keeps its area code when the person moves, so a 212 number can sit in Denver for years. And a nongeographic number, including a toll free number, is not attached to a local calling area at all. There is no zone to read off it.

The 21 Area Codes That Cross a Time Zone Line

Numbering boundaries and time zone boundaries were drawn by different agencies for different reasons, and nobody reconciled them. Where they disagree, one area code serves communities on both sides of a clock change. These are the 21 codes the numbering file flags with two zones.

Pale violet illustration of a long frosted glass trough divided into two compartments by a thin glass wall, with one small glass sphere resting in each compartment.
ZonesStateArea codes
Eastern and CentralFlorida448, 850
Eastern and CentralIndiana219, 574, 812
Eastern and CentralKentucky270, 364, 606
Eastern and CentralMichigan906
Eastern and CentralTennessee423, 729, 931
Central and MountainKansas620, 785
Central and MountainNebraska308
Central and MountainNorth Dakota701
Central and MountainSouth Dakota605
Central and MountainTexas915
Mountain and PacificIdaho208
Mountain and PacificOregon458, 541

Twelve states, 21 codes. Indiana, Kentucky and Tennessee carry three apiece. Work a territory in any of them and a real share of your list has no single correct answer.

Run the arithmetic on one of them. A 606 number is somewhere in Kentucky, which means the contact is on Eastern or Central time. Dial it at 8:15 Eastern and you are either fifteen minutes inside the legal window or forty-five minutes outside it. The number alone will not tell you which. The rep did nothing wrong. The data did.

Overlays are a separate issue, and worth separating. An overlay puts more than one area code over the same region, so two neighbors on the same block can carry different codes and the same clock. Of the 21 split codes, eight are overlays and thirteen are not. Overlays and zone splits are two different problems that happen to land on the same list.

One Nevada City Sits Outside Its Own Area Code Time Zone

Nevada is Pacific. Nevada’s 775 covers nearly the whole state, and the numbering file does not give it a zone letter at all. It gives it a note naming one city.

The reason is in the federal regulation that defines the line between the mountain and Pacific zones. That rule walks the boundary down the Utah and Nevada border, and when it reaches West Wendover it turns, runs along the northern, western and southern city limits, and returns to the state line before continuing south. The city is deliberately carved out into Mountain time.

Two different federal publications, a numbering report and a boundary regulation, independently flag the same town. That is the resolution limit of this whole exercise. The lookup resolves to three digits. The law resolves to a city boundary. No area code table will ever close that gap. Which is why the output of a lookup belongs in a field marked as an estimate, not in the field your dialer reads.

Calling Hours Run on the Buyer Local Clock

Why does a twenty-one-code edge case deserve this much attention? Because this is where a data question becomes a compliance question.

The FCC rule implementing the Telephone Consumer Protection Act bars any telephone solicitation to a residential telephone subscriber before the hour of 8 a.m. or after 9 p.m., and the rule says in parentheses whose clock counts: local time at the called party’s location. The FTC’s Telemarketing Sales Rule says the same thing in its own words, making it an abusive practice to place an outbound call to a person’s residence at any time other than between 8:00 a.m. and 9:00 p.m. local time at the called person’s location.

Read that twice. Not your local time. Not the area code’s nominal zone. The location of the person answering.

Both rules are written for residential calls, and a list of mobile numbers rarely tells you which of those is a residence. That ambiguity is not a loophole to lean on. It is a second reason the conservative window is the cheap answer: when you cannot prove the zone and you cannot prove the line type, the overlap of the possible windows costs you forty-five minutes of dialing and removes the question.

State rules can be stricter than the federal floor, and several are. If you are building calling windows for a national list, read the state telemarketing laws alongside the federal hours and take whichever is tighter. The same logic applies to your do-not-call process: the screening and the hours are separate checks and a list can pass one and fail the other.

Daylight Saving Moves the Offset and the Area Code Never Moves

Suppose you resolved the zone correctly. You are still not done. The zone is a label, and the label does not carry the offset.

Pale violet illustration of two flat concentric frosted glass rings, each carrying a small raised marker block on its rim, with the outer marker rotated a short arc away from the inner one.

Federal law advances the clock one hour from 2 a.m. on the second Sunday of March to 2 a.m. on the first Sunday of November, and it lets a state that lies entirely within one time zone exempt itself. Arizona took that option. Its statute says the state elects to reject daylight saving time and to stay on standard mountain time, and it adds that a future legislature can change its mind.

Now look at what the numbering file says about Arizona. All five of its area codes, 480, 520, 602, 623 and 928, carry the same Mountain letter, every month of the year. The letter is correct and the letter is useless on its own. For roughly eight months a 602 number keeps the same clock as Los Angeles, and for the other four it keeps the same clock as Denver, and nothing about the number changes on either date.

So the rule for any system that stores this is short. Store the geographic zone, not a fixed offset and not a three-letter abbreviation, then compute the offset for the date of the call. A call booked in October for a date in November is a call booked across a transition. Teams that store an offset instead of a zone find this out when the meeting fires an hour early.

One more wrinkle worth knowing before you build a converter. Countries change clocks on different dates, so the usual difference between two cities is wrong for a couple of weeks a year in both directions. Anything scheduling international local presence outreach has to convert on the call date rather than on today.

How to Find a Time Zone by Area Code Without Guessing

The mechanics are simple. The discipline is in what you do with an ambiguous result.

  1. Normalize the number first. Strip the punctuation, identify the country code, and only then read the next three digits as an area code. A bare three-digit sequence is not automatically a North American code.
  2. Check the code against a current numbering source. New codes go into service every year, and a stale table returns a clean-looking answer for a code it has never heard of.
  3. Keep every zone the source returns. If the code is one of the 21, the correct output is two zones, not the more common one.
  4. Apply the call date, not today. Resolve the offset for the date the call or meeting actually happens.
  5. Cross-check against something that knows the location. A billing address, an office location on the account, a stated city, or the territory the deal is assigned to all beat an area code, and any of them should win when they disagree with it.
  6. When it stays ambiguous, take the intersection. For an Eastern and Central code, the window that is legal in both is 9 a.m. to 9 p.m. Eastern. Dial it there and the zone stops mattering.

That last step is the whole method compressed. You are not trying to find the buyer’s clock. You are trying to find a time that holds up no matter which clock they are on.

What to Store in the CRM and What the Area Code Must Not Overwrite

Most of the damage here is done by an enrichment job, not by a rep. A field gets populated from the phone number. It overwrites something better. Six months later nobody remembers which records are inferred and which were real.

Give the Inferred Zone Its Own Field

Three fields, not one: the zone, where it came from, and the date it was last checked. Source values that carry their own confidence are the point here, something like contact-stated, address-derived and area-code-derived. A rep looking at the record can then tell the difference between a zone the buyer told you and a zone a script guessed, which is the only thing that lets them decide whether to trust the number in front of them.

Never Overwrite a Better Signal With a Worse One

If the account already carries a verified office address or a zone the contact supplied, an area-code-derived value does not replace it. Write to the inferred field, leave the better field alone, and let the display logic pick the best available source. An enrichment run that fills blanks is useful. An enrichment run that overwrites is a data loss event you will not notice for a quarter.

Let Ambiguous Mean Ambiguous

For the 21 split codes, for nongeographic numbers, and for any record where the signals conflict, write multi-zone or unknown. Do not resolve it to the more populous half of the state because the field requires a value. A record marked ambiguous routes into the conservative window automatically. A record silently resolved to the wrong half routes into a violation.

Sort the Call Block by Likely Local Time

Once the field is honest, it earns its keep. Group the day so the earliest legal zone goes first and the list moves west as the morning does, push the ambiguous records into the overlap window, and stop sorting the queue by lead score alone in a national territory. Kixie’s scheduled auto-calls take the target’s time zone when the call is set up, so the field you store is the field that decides when the call fires. That is the handoff that matters: the inference stops being a note a rep reads and becomes the input that controls the dial.

Then track one number. Count the calls your dialer places in the first and last hour of each contact’s local day. If that count is not near zero on the ambiguous records, the window is not being applied and the field is decoration.

Time Zone by Area Code FAQs

Can an area code tell me what time it is for my prospect?

It gives you a likely zone, not a clock. 356 of the 378 US geographic area codes resolve to one zone, so the estimate is usually right, but the contact may have kept the number after moving, may be traveling, or may be in one of the 21 codes that covers two zones. Confirm against an address or an account location before you treat it as settled.

Which area codes cross two time zones?

Twenty-one of them, in twelve states. Eastern and Central: 448 and 850 in Florida, 219, 574 and 812 in Indiana, 270, 364 and 606 in Kentucky, 906 in Michigan, and 423, 729 and 931 in Tennessee. Central and Mountain: 620 and 785 in Kansas, 308 in Nebraska, 701 in North Dakota, 605 in South Dakota, and 915 in Texas. Mountain and Pacific: 208 in Idaho, and 458 and 541 in Oregon. Nevada’s 775 is a separate case, flagged for the city of West Wendover.

Does an overlay area code change the time zone?

No. An overlay puts a second code over the same geographic region, so two neighbors can carry different area codes and the same clock. Check the current mapping for each code anyway, because a new overlay will not appear in a table that has not been refreshed.

Can a toll free number give me a time zone?

No. A toll free or other nongeographic number is not tied to a local calling area, so there is nothing to derive. Use a business address, a stated location, or another location-bearing record instead.

Is Arizona on Mountain time or Pacific time?

Arizona’s area codes are Mountain in the numbering data year round, and Arizona rejects daylight saving time by statute. The practical effect is that for most of the year an Arizona number matches the Pacific clock rather than the Denver clock, which is why you resolve the offset for the call date instead of reading the zone label.

What time zone field should a CRM store?

Store a geographic zone identifier, the source it came from, and the date it was last checked. A fixed UTC offset or a three-letter abbreviation looks tidier and breaks twice a year, because the offset changes on dates the zone label does not.

Use the Area Code as a Signal and Dial Against the Window

The useful version of this is short. Resolve the code against current numbering data, keep both answers when there are two, compute the offset for the call date, let anything that knows the real location outrank the area code, and dial the ambiguous records inside the window that is legal in every zone they could be in.

Then go check the one thing that proves it worked. Pull the timestamps of your outbound calls against each contact’s resolved zone and look at the edges of the day. The records sitting at 7:40 local are the ones your area code lookup got wrong, and they were findable before the call, not after.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 19, 2026.

Florida Telemarketing Laws That Survive Every Exemption

TL;DR: Florida telemarketing laws live in two different statutes, and most teams read only one of them. The Florida Telephone Solicitation Act sits in Part I of chapter 501 and governs prior express written consent, the state do-not-call list, the internal opt-out list, the caller ID transmission rule and what the rep has to say on contact. The Florida Telemarketing Act sits in Part IV and governs licensing, which the state regulator priced as of November 18, 2026 at $1,500 a year for the business, $50 a year for each salesperson, and a minimum $50,000 security posted as a surety bond, a certificate of deposit or a letter of credit. Part IV carries what the regulator counts as 28 paragraphs of exemptions, and the exemption provision opens by naming three things that survive every one of them: the duty to file and display a license or an affidavit of exemption, the 8 a.m. to 8 p.m. window in the called person’s time zone, the cap of three calls to the same person in 24 hours on the same subject, and the caller ID rules. Those exemptions disclaim only their own part, so none of them touch the consent, do-not-call or identification duties in Part I. Two more operating facts decide how a dialer gets configured. A call to any Florida area code carries a rebuttable presumption that it reached a Florida resident, so the state’s rules attach to the number you dialed rather than the address on the record. And the per-violation civil penalty is a Class IV penalty, which the penalty statute defines as $10,000 or more, with a Class III administrative fine of up to $10,000 as the alternative, plus a private action for actual damages or $500 per violation, trebled at the court’s discretion for a willful or knowing violation. Texts get one procedural gate before any of that: the called party must first reply STOP, and the solicitor then has 15 days to stop sending.

A rep loads a Florida list on Tuesday afternoon and starts dialing. Nothing on that screen says which of the two Florida statutes applies, whether the company filed an affidavit of exemption, or whether 6:40 p.m. Pacific is already past the cutoff in Tampa. That is the whole compliance problem in one screen. Florida telemarketing laws are not one rule you either clear or fail. They are two statutes with different scopes, different regulators’ hooks, and an exemption list that is far narrower than the word exemption suggests.

This is general business information, not legal advice. Have counsel review your program against the current statutes before you call or text Florida numbers.

Florida splits its telemarketing rules across two statutes

Chapter 501 of the Florida Statutes splits the work. Part I, the general provisions, holds the Florida Telephone Solicitation Act. It is the one that defines a telephonic sales call, requires prior express written consent for automated and recorded sales calls, builds the state do-not-call list, forces caller ID transmission, and gives the called party a private action. Part IV, the Florida Telemarketing Act, is a licensing regime. It decides who has to register with the Department of Agriculture and Consumer Services, post security and license every salesperson.

That split matters because the two parts use different words for the same people. Part I regulates a telephone solicitor. Part IV regulates a commercial telephone seller and a salesperson. A company can be outside the Part IV definition entirely and still be squarely inside Part I. Teams get this backwards constantly. They confirm with a bond broker that no license is required, file the paperwork, and treat the question as closed. It is not closed. Nothing in the licensing analysis says anything about consent, list scrubbing or what the rep says when the buyer picks up.

Both parts reach out-of-state callers. The regulator’s own guidance answers the question directly: a team that solicits no one in Florida but calls from a Florida desk is still covered, and a team with no Florida presence that calls a purchaser in Florida is covered too. Doing business in the state means a call from Florida or a call to a purchaser in Florida. Pick either end of the call and the statute attaches.

Florida telemarketing laws that survive every exemption

Here is the part that gets misread. The exemption provision in the Telemarketing Act does not begin by listing who is exempt. It begins by naming what stays. The provisions of that part do not apply to the listed categories except the license and affidavit section and two subsections of the unlawful-acts section. Read the carve-out before you read the list.

Thick translucent glass ring tilted in perspective on a pale violet ground, holding three glass spheres inside its opening while small glass fragments drift away to the right.

Those surviving duties are not trivia. They are the three that a dialer actually has to enforce:

  • Filing and display. A seller claiming one of the common exemptions has to file a notarized affidavit of exemption with the department and display the receipt at the place of business. The department can request scripts and contracts to verify the exemption before it accepts the filing. Failure to display a license or an exemption receipt is grounds for an immediate cease and desist order, and the statute says the department may order the business to cease operations and shall order the phones shut off.
  • Hours and frequency. No commercial telephone solicitation call before 8 a.m. or after 8 p.m. local time in the called person’s time zone, including calls placed through automated dialing or recorded messages. No more than three such calls to a person over a 24-hour period on the same subject matter, regardless of the phone number used to place them.
  • Caller identification. No intentional blocking of the solicitor’s name or number when the equipment can transmit it, and no technology that deliberately displays a different number to conceal the caller’s identity. The statute makes that second one a second-degree misdemeanor.

So an exemption is a licensing exemption. It is not a calling exemption. A seller operating under a filed affidavit still answers for the window, the frequency cap and the caller ID rules, and still has to produce the filing on request.

Then there is the larger asymmetry. Every exemption in that list disclaims this part, meaning Part IV only. The Telephone Solicitation Act is in Part I. A business-to-business seller that qualifies under the Part IV exemption for firms operating three years under the same name with at least half their dollar volume in repeat sales to existing businesses has done nothing at all to its Part I obligations. The consent rule still applies. The do-not-call screen still applies. The identification rule still applies.

The practical test is short. Ask which part your analysis covered. If the answer is a license, an affidavit or a bond, the analysis covered Part IV, and the rules that govern how your reps dial are still unexamined.

What counts as consent under Florida telemarketing laws

Florida requires prior express written consent before anyone places an unsolicited telephonic sales call using an automated system for the selection and dialing of telephone numbers, or playing a recorded message once the call connects. A telephonic sales call in Florida is defined to include a text message and a voicemail transmission, not just a live voice call. That definition is doing most of the work people miss.

The statute spells out what the written agreement has to contain, and the list is checkable against a form:

  • The signature of the called party.
  • Clear authorization for the sender to place a call, text or voicemail using an automated dialing system, a recorded message or a prerecorded voicemail.
  • The telephone number the called party authorizes.
  • A clear and conspicuous disclosure of what the person is authorizing, and a statement that signing is not required as a condition of purchasing anything.

Signature is defined generously, which cuts both ways. It covers an electronic or digital signature valid under federal or state contract law, and it also covers an act demonstrating express consent, including checking a box or replying affirmatively to receiving text messages. That means a well-built web form clears the bar. It also means your form is now the evidence record, so store what the form said, when it said it, which version rendered, the number submitted and the affirmative action taken. A phone number with no disclosure attached to it is not consent.

Revocation has its own rule, and it is broader than the do-not-call list. The statute bars an outbound call, text or voicemail to a consumer, business, or donor who has previously communicated that they do not want one, whether that message went to the seller or to someone soliciting on the seller’s behalf. Note the word business. The state do-not-call list is residential, mobile and paging; the internal suppression duty is not limited that way. If a B2B prospect tells one rep to stop, that record has to go quiet across every campaign and every vendor, not just that rep’s queue.

Two do-not-call lists Florida expects you to screen

The department maintains the state list, and the operating detail that matters is its refresh cadence. The statute bars an unsolicited telephonic sales call to a number appearing in the then-current quarterly listing published by the department. Quarterly, not daily. A quarterly file means your suppression table has a known staleness window, and the campaign that launches the week a new file drops is the one that inherits the risk. Build the refresh into the calendar rather than treating the download as a one-time setup task.

Two overlapping translucent glass panels of different sizes lying on a pale violet ground, a cluster of glass beads caught where they overlap and three beads loose outside both panels.

Consumers get on that list for free and stay on it indefinitely, which the department states plainly. There is no expiry to plan around and no renewal cycle that quietly releases numbers back to you.

The federal registry is a separate obligation with its own access rules, and the two lists do not substitute for each other. If you are only screening against the National Do Not Call Registry, you are missing the state file. If you are only screening the state file, you are missing everything outside Florida. A do-not-call process has to run both, plus the internal list, plus client-specific suppression when you call on another company’s behalf.

One more trigger decides whether any of this attaches at all. The statute creates a rebuttable presumption that a telephonic sales call placed to any area code in Florida reached a Florida resident, or someone physically in the state when the call connected. That presumption runs on the number dialed. A record whose billing address says Ohio and whose mobile number carries a Florida area code is presumptively a Florida call, and the burden to show otherwise is yours. Route on the area code, not on the address field.

Florida calling hours and the three-call cap

Florida closes at 8 p.m. rather than the 9 p.m. federal cutoff, measured in the called person’s time zone. That one hour is where West Coast teams get caught: a 5:15 p.m. Pacific block is 8:15 p.m. in Miami, and the dialer does not know that unless someone told it to care. Enforce the window on the recipient’s location, which for Florida means the area code presumption above, and not on the rep’s clock.

The frequency cap is the second control and it is harder to implement than it reads. Three calls to a person in 24 hours on the same subject matter, counted across every number you place them from. That is a per-person counter, not a per-campaign or per-caller-ID counter, so a multi-line dialer rotating caller IDs and two sequences touching the same record can breach it without any single system showing a problem. Count attempts centrally, across reps, queues, numbers and vendors.

Florida is not alone on either rule, and the thresholds differ enough that a national list needs a per-state table rather than one global setting. The comparison for calling hours in every other state is a separate piece.

What Florida requires the rep to say on contact

The identification duty is specific and it is immediate. On an unsolicited telephonic sales call to a residential, mobile or paging number, the solicitor identifies himself or herself by true first and last name, plus the business on whose behalf the call is placed, immediately upon making contact. Not after the hook. Not once the prospect sounds interested. Immediately. A script that opens with a question and gets to the company name in the third exchange does not meet that standard.

On the display side, the originating number has to be transmitted, along with the solicitor’s name where the carrier makes it available. There is one permitted substitution, and it is narrow: the name of the seller on whose behalf the call is placed, and that seller’s customer service number. The statute then adds a condition most summaries drop. The substituted number has to be capable of receiving calls, and when the recipient calls it back, it has to connect them to the solicitor or the seller. A substituted number that rings to a dead queue fails the rule even though the display looked correct.

Two more prohibitions sit alongside it. Deliberately displaying a different number to conceal the caller’s identity is a second-degree misdemeanor. Intentionally altering the caller’s voice to disguise identity, in order to defraud, confuse or injure the recipient or to extract personal information, is barred outright. None of that is in tension with rotating local numbers you actually own and answer, which is a caller ID reputation question rather than a concealment question, but the line is drawn at whether the displayed number resolves back to you.

What a Florida violation costs

The numbers are worth writing down, because they change how a program gets resourced rather than just how it gets described.

  • Civil penalty, per violation. The Telephone Solicitation Act puts it in the Class IV category, and the penalty statute defines Class IV as a fine of $10,000 or more. There is no stated ceiling in that category.
  • Administrative fine, as the alternative. The department may instead impose a Class III fine for each act or omission, which the penalty statute caps at $10,000.
  • Private action. A called party aggrieved by a violation may sue to enjoin it and recover actual damages or $500, whichever is greater. If the court finds the violation willful or knowing, it may increase the award up to three times that amount.
  • Fees. In civil litigation arising from a transaction involving a violation, the prevailing party recovers reasonable attorney fees and costs from the losing party, after judgment and after appeals.

Per violation is the operative phrase on all four. A list-level error does not produce one claim. It produces one claim per call, and a bad consent record replicated across a 40,000-record campaign is an arithmetic problem rather than a legal one. The department may waive a civil penalty where the person has already made full restitution to the injured consumers, which is one more reason complaint handling belongs in the operating process rather than in the legal file.

Florida text claims run through a 15-day gate

The private action for text message solicitations runs through a required notice step, added when the statute was amended in 2023. Before commencing an action for damages over texts, the called party has to tell the solicitor to stop by replying STOP to the number the texts came from. The solicitor then has 15 days to cease, and may send exactly one more message to confirm receipt of the notice. The action lies only if the person did not consent and the texts continue after that 15-day window.

Read as an operating rule rather than a litigation rule, that is a 15-day repair clock with a hard dependency on one thing: whether an inbound STOP on any of your numbers reaches your suppression table automatically. If a STOP lands in a shared inbox and waits for someone to read it on Monday, you have already spent most of the window. Wire the keyword to the suppression list, confirm once, and stop. The confirmation message is permitted; a second marketing message is not.

A Florida telemarketing laws checklist for the dialer

Most of this is configuration, not policy. Each item below is something a manager can open and inspect today.

  1. Decide the part, then the rule. Record whether the company is licensed under the Telemarketing Act, operating under a filed affidavit of exemption, or outside that part entirely. Then separately record the Part I analysis, because the first answer does not produce the second.
  2. Confirm the filing exists. If you are relying on an exemption that requires an affidavit, confirm it is on file and the receipt is displayed. An exemption believed in good faith and never filed reads the same to an inspector as no exemption.
  3. Set the window on recipient time zone. Block Florida attempts before 8 a.m. and after 8 p.m. local to the called party, and derive the zone from the number rather than the address field.
  4. Build the 24-hour counter centrally. Count attempts per person per subject across reps, queues, caller IDs, sequences and outsourced teams. Three is the cap, and a per-campaign counter will not see the breach.
  5. Schedule the quarterly scrub. Put the state list refresh on the calendar, run it against every active campaign, and log the file date you screened against.
  6. Honor revocation across the whole book. One STOP, one verbal request, one email request suppresses the record everywhere, including for business contacts, and including on lists you call on a client’s behalf.
  7. Audit the opening line. True first and last name plus the business, immediately on contact. Pull five recordings this week and check the first ten seconds.
  8. Call back your own displayed number. Dial each caller ID you present and confirm it rings somewhere a human or a queue answers during business hours.
  9. Store the consent artifact, not the checkbox result. Disclosure text, form version, timestamp, source URL, submitted number and the affirmative action taken.
  10. Re-read the statutes on a schedule. This framework was amended in 2021 and again in 2023, and the private-action mechanics changed both times.

Software implements those rules; it does not decide them. A sales engagement platform can enforce a time window, hold a suppression table, count attempts per record and keep the disposition history that proves what happened. Kixie runs those checks on the dialing path on the outbound path, which is the enforcement layer. The legal analysis above it stays a human job.

Florida telemarketing laws FAQ

Do Florida telemarketing laws apply to text messages?

Yes. The Telephone Solicitation Act defines a telephonic sales call to include a text message and a voicemail transmission, so the consent, revocation and identification provisions reach texts. The text-specific difference is procedural: a private damages action over texts requires the recipient to reply STOP first and give the sender 15 days to cease.

Does an existing customer relationship exempt the call?

Not on its own. A call to someone with a prior or existing business relationship is outside the statutory definition of an unsolicited telephonic sales call, which is what the do-not-call screen and the identification duty attach to. The Telemarketing Act has a separate exemption for soliciting prior purchasers, and it requires that the solicitor operate under the same exact business name. Neither one waives the internal suppression duty or the consent rule for automated and recorded calls.

Are business-to-business calls exempt in Florida?

Only from the licensing part, and only on specific facts. The Telemarketing Act exempts a business-to-business sale where the seller has operated at least three years under the same name with at least half its dollar volume in repeat sales to existing businesses, or where the buyer intends to resell the goods or use them in a manufacturing or recycling process. That exemption does not reach Part I, and the internal do-not-call duty expressly covers a business that has asked you to stop.

What hours can you call in Florida?

Between 8 a.m. and 8 p.m. local time in the called person’s time zone, which is an hour tighter than the federal 9 p.m. cutoff. That limit sits in the Telemarketing Act’s unlawful-acts section and survives every exemption in that part.

Do Florida telemarketing laws apply if my company is not in Florida?

Yes, if you are calling into the state. The statute defines doing business in Florida as placing calls from a Florida location or from anywhere else to purchasers located in Florida, and the regulator states the same in its own guidance. A call to a Florida area code also carries a rebuttable presumption that the person reached was in the state.

How much does a Florida telemarketing license cost?

The department lists $1,500 annually for the business application and $50 annually for each salesperson, plus a minimum $50,000 security posted as a surety bond, a certificate of deposit or a letter of credit. Those figures are the licensing side only and say nothing about the calling rules.

Sources

Sources verified by the Kixie Research Team on November 18, 2026.

Area Codes by State, Checked Against NANPA Records

TL;DR: The table below lists area codes by state for all 50 states and Washington, DC, rebuilt line by line from the North American Numbering Plan Administrator NPA report dated November 18, 2026. That file carries 372 in-service geographic area codes across the 50 states and DC, and 262 of them are overlays, meaning the old one code one region model is now the exception rather than the rule. California holds 41 codes, Texas 29, New York 23, Florida 23 and Illinois 17, while 11 states still run on a single code: Alaska, Delaware, Hawaii, Maine, Montana, North Dakota, New Hampshire, Rhode Island, South Dakota, Vermont and Wyoming. Nine codes entered service between March 2024 and June 2026 and are missing from most lists still in circulation: 235 in Missouri, 924 in Minnesota, 357 in California, 748 in Colorado, 729 in Tennessee, 457 in Louisiana, 471 in Mississippi, 483 in Alabama and 465 in New York. Three more are already scheduled: 565 in Georgia on December 6, 2027, 451 in North Carolina on September 21, 2028, and 761 in Kentucky, currently in trigger status. For a rep working a list, the operating takeaway is narrower than the table suggests. An area code tells you which numbering plan area a number was issued in. It does not tell you where the person is sitting today, what time it is there, or whether you are allowed to call.

Most lists of area codes by state are copies of copies. Somebody scraped a table a few years back, somebody else reformatted it, and the version your rep is looking at has not been checked against the numbering authority since. That is how you end up with a prospect in a brand new overlay whose number your routing rules treat as invalid, or a territory map that silently misses a code serving half a metro.

So this one is rebuilt from the source. Every code in the table came out of the NPA report published by the North American Numbering Plan Administrator, the body that actually assigns these codes, in the file dated November 18, 2026. Nothing was carried over from an older list.

Area Codes by State Reference Table

Codes shown are geographic area codes in service in each state as of the November 18, 2026 file. Toll free codes (800, 833, 844, 855, 866, 877, 888) are not tied to a state and are left out, as are codes serving US territories rather than states.

StateAbbrArea codes in serviceCount
AlabamaAL205, 251, 256, 334, 483, 659, 9387
AlaskaAK9071
ArizonaAZ480, 520, 602, 623, 9285
ArkansasAR327, 479, 501, 8704
CaliforniaCA209, 213, 279, 310, 323, 341, 350, 357, 369, 408, 415, 424, 442, 510, 530, 559, 562, 619, 626, 628, 650, 657, 661, 669, 707, 714, 738, 747, 760, 805, 818, 820, 831, 837, 840, 858, 909, 916, 925, 949, 95141
ColoradoCO303, 719, 720, 748, 970, 9836
ConnecticutCT203, 475, 860, 9594
DelawareDE3021
FloridaFL239, 305, 321, 324, 352, 386, 407, 448, 561, 645, 656, 689, 727, 728, 754, 772, 786, 813, 850, 863, 904, 941, 95423
GeorgiaGA229, 404, 470, 478, 678, 706, 762, 770, 912, 94310
HawaiiHI8081
IdahoID208, 9862
IllinoisIL217, 224, 309, 312, 331, 447, 464, 618, 630, 708, 730, 773, 779, 815, 847, 861, 87217
IndianaIN219, 260, 317, 463, 574, 765, 812, 9308
IowaIA319, 515, 563, 641, 7125
KansasKS316, 620, 785, 9134
KentuckyKY270, 364, 502, 606, 8595
LouisianaLA225, 318, 337, 457, 504, 9856
MaineME2071
MarylandMD227, 240, 301, 410, 443, 6676
MassachusettsMA339, 351, 413, 508, 617, 774, 781, 857, 9789
MichiganMI231, 248, 269, 313, 517, 586, 616, 679, 734, 810, 906, 947, 98913
MinnesotaMN218, 320, 507, 612, 651, 763, 924, 9528
MississippiMS228, 471, 601, 662, 7695
MissouriMO235, 314, 417, 557, 573, 636, 660, 816, 9759
MontanaMT4061
NebraskaNE308, 402, 5313
NevadaNV702, 725, 7753
New HampshireNH6031
New JerseyNJ201, 551, 609, 640, 732, 848, 856, 862, 908, 97310
New MexicoNM505, 5752
New YorkNY212, 315, 329, 332, 347, 363, 465, 516, 518, 585, 607, 624, 631, 646, 680, 716, 718, 838, 845, 914, 917, 929, 93423
North CarolinaNC252, 336, 472, 704, 743, 828, 910, 919, 980, 98410
North DakotaND7011
OhioOH216, 220, 234, 283, 326, 330, 380, 419, 436, 440, 513, 567, 614, 740, 93715
OklahomaOK405, 539, 572, 580, 9185
OregonOR458, 503, 541, 9714
PennsylvaniaPA215, 223, 267, 272, 412, 445, 484, 570, 582, 610, 717, 724, 814, 835, 87815
Rhode IslandRI4011
South CarolinaSC803, 821, 839, 843, 854, 8646
South DakotaSD6051
TennesseeTN423, 615, 629, 729, 731, 865, 901, 9318
TexasTX210, 214, 254, 281, 325, 346, 361, 409, 430, 432, 469, 512, 621, 682, 713, 726, 737, 806, 817, 830, 832, 903, 915, 936, 940, 945, 956, 972, 97929
UtahUT385, 435, 8013
VermontVT8021
VirginiaVA276, 434, 540, 571, 686, 703, 757, 804, 826, 94810
WashingtonWA206, 253, 360, 425, 509, 5646
Washington, DCDC202, 7712
West VirginiaWV304, 6812
WisconsinWI262, 274, 353, 414, 534, 608, 715, 9208
WyomingWY3071

That is 372 codes across the 50 states and DC. Four states carry more codes than the entire bottom half of the list combined.

Why One Code No Longer Means One Place

Here is the part that breaks older mental models. Of the 372 codes in the table, 262 are overlays. An overlay is a new code laid on top of a region that already has one, covering the same territory rather than splitting it. Existing customers keep their numbers. New numbers get the new code. Two neighbors on the same street can have different area codes, and two contacts with different codes can be in the same building.

Four overlapping frosted glass rings sharing one bright central region on a pale violet ground

New York City is the clearest example in the file. The 212, 332, 646 and 917 codes form one overlay complex, and 347, 465, 718, 917 and 929 form another. The 917 code belongs to both. So a 917 number means New York City and nothing more precise than that, and no amount of territory logic will squeeze a borough out of it.

Overlays also changed how people dial. The numbering file flags 263 of those 372 codes as requiring all ten digits for a local call inside the same area code. The seven-digit habit only survives in 51 of them. If your team still trains reps to drop the area code on in-state numbers, that training is wrong in roughly seven cases out of ten.

Where new area codes come from

Codes do not appear at random. The numbering administrator collects utilization and forecast data from carriers, projects when each area code will run out of central office codes, and publishes a semi-annual exhaust analysis every April and October. When a code is heading for exhaust, the industry convenes, agrees on a relief plan, sends it to the state regulator for approval, and publishes a planning letter with the implementation schedule. If demand outruns the plan, the administrator can declare jeopardy and ration codes until relief lands.

Ten area codes are in relief planning as of the November 18, 2026 file: 502 in Kentucky, 509 in Washington, 580 in Oklahoma, 626, 657, 714 and 949 in California, 828 in North Carolina, 912 in Georgia and 956 in Texas. Each of those is a candidate to gain an overlay partner, which means any list you build today has a known expiration date in those regions.

The Nine Area Codes Older Lists Miss

Nine geographic codes entered service between March 2024 and June 2026. All nine are overlays, which means they sit inside regions your list already covers, so the gap is easy to miss until a number fails a validation rule.

CodeStateOverlay complexIn service
235Missouri235/573March 24, 2024
924Minnesota507/924August 30, 2024
357California357/559March 26, 2025
748Colorado748/970July 7, 2025
729Tennessee423/729September 5, 2025
457Louisiana318/457September 25, 2025
471Mississippi471/662January 30, 2026
483Alabama334/483February 23, 2026
465New York347/465/718/917/929June 18, 2026

Three more are already approved and dated. Georgia gets 565 on December 6, 2027, joining the 912 complex. North Carolina gets 451 on September 21, 2028, joining 828. Kentucky has 761 assigned against 502 and sitting in trigger status. Put those three on the calendar now rather than finding them when a rep cannot dial one.

What an Area Code Does Not Tell You

This is where a reference table starts doing damage if you ask too much of it. The table answers one question: which numbering plan area issued this number. Teams routinely ask it three more questions it cannot answer.

It does not tell you where the person is

People keep mobile numbers when they move. A rep in Denver can carry a 617 number for a decade. Businesses buy numbers in markets they want to sell into. So the area code records where a number was issued, not where the human answering it lives or works today. Treat it as a weak signal that loses to a verified address record every single time, and keep the inferred field separate from the confirmed one in your CRM so nobody downstream mistakes one for the other.

It does not tell you the local time

The numbering file carries a time zone field, and it disagrees with itself inside 11 states. Florida, Idaho, Indiana, Kansas, Kentucky, Michigan, Nebraska, Nevada, Oregon, Tennessee and Texas all have in-service codes carrying more than one zone value. Tennessee alone carries three. So a rep who derives a calling window from the first three digits will dial somebody an hour earlier than intended often enough to matter, and calling windows are exactly the thing you do not want to get wrong.

It does not tell you whether you may call

Permission is a record, not a prefix. Whether a number can be dialed depends on consent, suppression lists, the National Do Not Call registry and internal do-not-call status, plus whatever the applicable state rules require. None of that is encoded in an area code. A local-looking number is not a legal basis for anything.

Using Area Codes by State in Outbound Calling

There is one place where this table earns its keep operationally, and it is not the contact record. It is the number you dial from.

An arc of seven frosted glass pebbles with the glowing larger one at the apex above a wide flat glass lens on a pale violet ground

Local presence dialing matches the caller ID a prospect sees to the area code attached to the number being called. Kixie runs this through a pool of real phone numbers covering area codes across the US, and rotates through several of them so one number is not burned by repeated attempts to the same prospect. The mechanism depends entirely on the mapping in the table above being current. Feed it a stale list and a brand new overlay gets dialed from an out-of-market number, which is the exact thing the feature exists to avoid.

Two caveats worth saying plainly, because this tactic gets oversold. First, a matching area code is not a magic answer rate. Kixie has published its own comparison of local, toll free and out-of-state numbers and what actually gets answered, and the honest version is that number reputation and call volume per number matter alongside the match. If the number you rotate to is already flagged, a perfect area code match will not save the call. That is a caller ID reputation problem, not a numbering problem.

Second, the practice has rules. Displaying a number you control and can be reached at is different from displaying a misleading one, and the boundary matters. Kixie covers it in more depth in how local presence dialing works, and the mechanics live on the local presence feature page.

What to inspect this week

Pull your number list and diff it against the table above. Four things to check, in order:

  • Do the nine codes added since March 2024 exist in your validation rules, or do numbers carrying them get rejected or misrouted?
  • Does your dialing-from pool cover the overlay partners in the states you actually sell into, or only the older code in each pair?
  • Are the inferred location and confirmed location stored in separate CRM fields, and does your calling-window logic read the confirmed one?
  • Are the ten area codes in relief planning on a review date, so a new overlay does not surprise you?

Those four take an afternoon. The alternative is finding the gap one failed dial at a time.

Area Codes by State Questions

How many area codes does each state have?

It ranges from one to 41. California has the most at 41 in-service geographic codes, then Texas at 29, New York and Florida at 23 each, and Illinois at 17. At the other end, 11 states run the whole state on a single code.

Which states still have only one area code?

Alaska (907), Delaware (302), Hawaii (808), Maine (207), Montana (406), North Dakota (701), New Hampshire (603), Rhode Island (401), South Dakota (605), Vermont (802) and Wyoming (307). That is 11 states as of the November 18, 2026 numbering file.

Can one area code cover more than one state?

In the current US numbering file each geographic code is listed against a single state or jurisdiction. The practical complication is the reverse case: a single state can hold dozens of codes, and overlay complexes mean several codes share the same ground.

Why did my area code start requiring ten digits?

An overlay was added to the region. Once two codes serve the same territory, seven digits no longer identify a unique number, so local calls move to ten digits. This applies to 263 of the 372 codes in the table.

How often does this list change?

Several times a year. Nine codes entered service in the roughly two and a half years before this file date, three more are scheduled through 2028, and ten existing codes are in active relief planning. A yearly re-check is the minimum; quarterly is better if local presence dialing is part of your motion.

Where should I verify an area code?

Go to the numbering administrator itself. The NPA report linked in the Sources section below is the underlying data file, refreshed continuously, and it carries the in-service date, overlay complex, time zone and dialing plan for every code.

Sources

Sources verified by the Kixie Research Team on November 18, 2026.

Telemarketing Rules Canada Enforces on Outbound Calls

TL;DR: The telemarketing rules Canada enforces are three rule sets, not one list, and the National Do Not Call List is only the part everyone remembers. Every organization on whose behalf telemarketing happens has to register with the National DNCL Operator even when its calls are exempt, and only non-exempt callers also buy a subscription, which, on the fees published as of November 18, 2026, runs $62,166 a year for every Canadian area code or $3,218 a year for a single one, with a query option at 50 cents per number in sessions of up to 100. Numbers registered on the list are off limits after 31 days. The existing business relationship window is 18 months after a purchase, lease, rental or written contract and 6 months after an inquiry, and it dies the moment that person asks you to stop calling. The internal do not call list is the obligation with no exemption at all: anyone who asks has to be on it within 14 days and stays for 3 years, and if you dial for a client you have to get them onto the client’s list inside the same 14 days. Business numbers are outside the DNCL rules and are not supposed to be registered on it, but they are still inside the Telemarketing Rules and the automated dialing rules. Calls placed from outside Canada are covered too. Penalties run up to $1,500 for an individual and $15,000 for a corporation per violation, each continued day counts as a separate violation, and the regulator may publish your name and the amount. Email and texts fall under CASL instead, where contact details have to stay good for 60 days, unsubscribes have to take effect within 10 business days, and the ceiling is $1,000,000 for an individual and $10,000,000 for anyone else. Build the suppression path into the dialer and the CRM before the first Canadian call, because the part that bites is never the national list, it is the stop-calling request a rep took on Tuesday that never reached the client’s system.

Most teams open a Canadian calling motion the same way. Somebody buys a list, somebody asks whether there is a do not call list in Canada, somebody says yes and subscribes to it, and the campaign goes live. That is one requirement out of three, and it is not the one that generates complaints.

Here is the shape of the thing. The Canadian Radio-television and Telecommunications Commission runs a set called the Unsolicited Telecommunications Rules. Inside it there are the Telemarketing Rules, the automatic dialing-announcing device rules, and the National DNCL Rules. The first two apply to your calls whether or not the National DNCL Rules do. So an exemption from the national list is not an exemption from the framework, and a team that treats it as one has mapped roughly a third of its obligations.

This is general information for planning a campaign, not legal advice. Fees, exemptions and enforcement practice change, so confirm the current text and get qualified compliance review before you dial.

What the telemarketing rules Canada enforces actually cover

Start with the definition, because it is wider than most reps assume. The National DNCL describes solicitation as selling or promoting a product or service, or asking for money or money’s worth, directly or indirectly, for yourself or for somebody else. Read that twice. Indirectly is doing a lot of work there. A call that never names a price but exists to move someone toward a purchase is still solicitation.

Some calls are not telemarketing at all. The National DNCL names product recall calls, appointment reminders, payment and bill collection calls, public service announcements, and calls made solely for market research, surveys or public opinion polls. Those sit outside the National DNCL Rules. They can still fall under the automated dialing rules, which is the trap: a team concludes the call is not telemarketing, then drops a prerecorded message on it and lands back inside a rule set it stopped reading.

So the first question on every campaign is not which list do we scrub. It is what is this call, and what is it for. Classify the channel and the purpose before anybody uploads a file.

Register your organization first, subscribe to the National DNCL second

This is the distinction that catches people, and it is worth being precise about because the two words get used interchangeably on sales floors.

Registration is mandatory for every organization on whose behalf telemarketing calls are made, whether you dial yourself or hire somebody. The National DNCL is explicit that you must still register even if the calls made by you or for you are exempt. Subscription is the paid access to the actual numbers, and that is required only when the calls are not exempt.

Now the vendor side. If you are an agency dialing purely on behalf of clients, you generally do not need your own registration or subscription, because you work off the client’s. But you do carry a records obligation: a telemarketer calling for clients has to make sure each client is registered, make sure each client is subscribed when the calls are not exempt, and keep records of those client registrations and subscriptions for three years.

Registering is not instant either. New registrants go through an identity validation step run with Dun and Bradstreet, matching your business legal name, parent company name, operating name and address against their database. No match means you go get a D-U-N-S number first and start the registration over. Build that into the launch timeline instead of running into it the week you wanted to dial.

What a National DNCL subscription costs

Published fees, and they are not small. These are the rates published as of November 18, 2026, and they get revised, so price the campaign against the current schedule rather than this paragraph. For a download subscription covering every Canadian area code, the total payable is $62,166 for a year, $34,011 for six months, $17,835 for three months, or $6,112 for one month. Each of those splits into a National DNCL Operator fee and a CRTC unsolicited telecommunications fee; on the annual all-area-code option that is $40,460 plus $21,706.

By individual area code, on the same schedule, it drops hard: $3,218 a year, $1,656 for six months, $854 for three months, or $290 for one month. There is also a query option at 50 cents per telephone number, capped at 100 numbers per query session, in any combination of area codes.

Those numbers should change how you build the territory. A team calling three area codes and a team calling all of Canada are not making the same decision, and buying national coverage for a list that lives in two provinces is a line item nobody will defend later. Download files come as CSV or XML, for one, three, six or twelve months. Size the subscription to the list you actually have.

One more rule that surprises groups and franchises: you cannot sell, rent, lease, publish or otherwise hand the list to anyone outside your organization, affiliates included. Association members are usually separate legal entities, so each one registers and buys its own. A third party can scrub for you, and that is allowed, but they register in their own name and access your subscription using your Registration Access Number, Subscription Access Number and Download Key. When you part ways, regenerate the Download Key. That kills the old key and cuts their access without anyone needing to be polite about it.

The 31 day DNCL clock and what scrubbing really means

A consumer registers a number. You have 31 days. After that, the National DNCL Rules prohibit calling it. Canadians can register home, mobile, fax and VoIP numbers, and registration is free, so there is no cost barrier keeping the list small.

A large frosted glass disc with a wedge segment cut out of it, beside a receding row of small glass cards that fade as they approach a narrow upright glass gate, on a pale violet ground.

The operational failure here is almost never the subscription. It is the gap between the download and the dial. A list scrubbed on the first of the month and still dialing on the twenty-eighth has four weeks of new registrations sitting in it, and the 31 day window does not care that your file is old. If you run US campaigns too, this is the same discipline that makes DNC scrubbing run on more than one clock, just with a Canadian interval attached.

Pick a re-scrub cadence, write it down, and make the dialer refuse a list older than that cadence. If the enforcement lives in a rep’s memory, it is not enforcement.

Telemarketing exemptions that do less than reps think

The exemptions from the National DNCL Rules cover calls made by or for Canadian registered charities, political parties and riding associations and candidates, people collecting information for a survey, and newspapers of general circulation soliciting subscriptions. There is also the existing business relationship, and express consent.

The existing business relationship has hard edges. You can call someone who purchased, leased or rented a product or service from you in the last 18 months, who has a written contract with you still in effect or expired within the last 18 months, or who made an inquiry or submitted an application about a product or service within the last 6 months. Eighteen months and six months. Those are different windows for different events, and a CRM that stores one timestamp called last_touch cannot tell you which one applies.

Express consent means a written, electronic or online form, or an audio recording of the person’s verbal permission, or a record of that permission confirmed by an independent third party. A checkbox nobody can produce later is not an exemption. It is a story about an exemption.

Now the part worth memorizing. In the Telecommunications Act, the existing business relationship exemption is written to apply to a person who has not made a do not call request to the organization the call is for. The exemption is conditional on the absence of that request. So the moment a customer says stop calling me, the relationship stops being a permission slip. Reps who have been taught that a current customer is always callable have the rule exactly backwards at the one moment it matters.

And labels do not settle anything. Calling a campaign a survey does not make it one if its purpose is promotional. The question is always what the call is for, not what the project is named in your sheet.

The internal do not call list has no exemption

Every telemarketer and every client of a telemarketer in Canada has to keep an internal do not call list. Including the ones making exempt calls. That is the obligation that survives every carve-out on the page above, and it is the one most teams run worst.

Two frosted glass trays set apart at different heights on a pale violet ground, joined by a single arcing translucent tube with one small glass token travelling inside it.

The mechanics are specific. When someone asks not to be called, their name and number go on your internal list within 14 days. If you are dialing on behalf of another organization, you have to make sure that name and number reach that organization’s own list within the same 14 days. And it stays there for 3 years.

Walk that through a real floor. A rep takes the request at 2:40 on a Tuesday. Does it get captured as a call disposition, or typed into a note field nobody queries? Does it leave the dialer and reach the CRM? If an agency took the call, does it reach the client’s system, and who confirms that it did? Fourteen days is generous until you realize nothing in the chain is automatic, and then it is a deadline running against a manual handoff.

One more boundary worth knowing: firms calling solely for market research, surveys or public opinion polls are not required to keep internal do not call lists for those calls. If your organization does both research and selling, do not let one team’s rule travel to the other team’s campaign.

Exempt calls still have to say who is calling

At the start of an exempt telemarketing call, the caller still has to identify the person or organization the call is being made for. Exempt from the list is not exempt from introducing yourself.

The Telemarketing Rules also set requirements for caller identification, disclosures and the hours during which calls may be placed, and those run against the recipient’s local time, not yours. Confirm the current permitted hours and the exact disclosure language against the CRTC’s published Unsolicited Telecommunications Rules before launch rather than against a blog post, including this one. What does travel safely as advice is the operating pattern: configure the dialing windows centrally, derive them from the recipient’s time zone, and do not ask a rep to work out whether it is too late in Newfoundland. US teams already run this problem across telemarketing calling hours that differ by state, and Canada adds six time zones to the same arithmetic.

Account for mobile numbers that moved, customers who relocated, daylight saving shifts and records with no location at all. Where the time zone is unknown, use the conservative window. A missing field should fail closed.

Automated and prerecorded calls run on their own rulebook

Automatic dialing-announcing device rules are a separate component of the Unsolicited Telecommunications Rules, and the National DNCL is explicit that they apply regardless of whether a call is exempt from the National DNCL Rules. They also reach calls that are not telemarketing at all.

Practical translation: consent that supports a live conversation does not automatically support dropping a recorded message at the same number. Before you turn on anything that plays audio without a person on the line, check the current consent standard, the identification requirements and the recordkeeping obligations for that specific call type. Then test the whole path, because the rules follow the experience and not the intent. What happens when a human answers. What happens on voicemail. What happens when someone asks for an agent, or asks not to be called again, and whether that request lands anywhere.

Business numbers sit outside the DNCL, not outside the telemarketing rules

The National DNCL Rules do not apply to telemarketing calls made to a business. Canada is clearer about this than most jurisdictions: business numbers are not supposed to be registered on the National DNCL at all, including a personal line that is also used for business.

Useful. Not a blanket. The Telemarketing Rules and the automated dialing rules still apply to those calls, and the internal do not call list still applies, so a business contact who asks to be removed gets the same 14 day and 3 year treatment as anyone else. The classification also has to be real. A job title in a data file, a company domain on an email address, or a vendor’s assurance that a list is business-to-business is not evidence about how a particular phone number is used. Mixed-use mobiles are where this gets decided, and the burden of showing why a number was treated as a business number sits with you.

If you work both sides of the border, note how differently this lands. The US National Do Not Call Registry comes with its own treatment of business and wireless numbers, and American teams also carry state do not call lists a national scrub will not catch. Do not port a Canadian assumption into a US campaign or the reverse.

Where CASL takes over from the telemarketing rules

The channel decides the rulebook. Canada’s Anti-Spam Legislation governs commercial electronic messages sent to an electronic address, and the Act defines that address as an email account, an instant messaging account, a telephone account or anything similar. Texts are in scope. Voice calls sit under the telemarketing side.

Under CASL you need consent, express or implied, and the message itself has to identify who sent it and who it was sent for, give the recipient a way to contact one of them, and carry an unsubscribe mechanism. Two timing rules are easy to miss and easy to fail. The contact information in the message has to stay good for at least 60 days after it goes out, which means a rotating alias or a mailbox that dies with a campaign is a problem. And an unsubscribe has to take effect without delay and no later than 10 business days, with no further action required from the person who asked.

So map sequences channel by channel before they run. Permission to call is not permission to email. A valid basis for an email is not a basis for a call. A mixed-channel cadence into Canada is being judged under two frameworks at once, and the suppression lists behind them are not the same list.

Telemarketing rules Canada applies no matter where you dial from

The telemarketing rules Canada enforces apply regardless of where the call originates. A team dialing Canadian consumers from Manila, Denver or anywhere else is inside the National DNCL Rules. Offshoring the dialing does not offshore the obligation.

Outsourcing does not move it either. Put the allocation in the contract: who holds National DNCL access, who scrubs and how often, who keeps consent evidence, whose script is approved, who retains call records, and how a complaint gets escalated and to whom. Before launch, confirm the vendor is running the campaign list you approved and the script you approved. During the campaign, audit a sample of records and calls where it is lawful and appropriate to do so. After any suppression request, verify the update reached both the vendor’s systems and your own, because a one-way sync is the most common way a 14 day obligation quietly fails.

And watch your own people. List exports, a side dialer somebody expensed, a spreadsheet a rep keeps because it is faster. Every one of those is a path around suppression. One authoritative suppression process is easier to audit than six informal ones, and it is the only version you can describe honestly to a regulator.

Put call suppression in the dialing path, not in a spreadsheet

Everything above fails or holds in the same place: the gap between a person saying stop and a system refusing to dial. That gap is a tooling question, not a policy question, and policy documents are where teams go to avoid answering it.

Kixie is a sales engagement platform for business calling and texting, and its Compliant Caller capability supports checks against the National Do Not Call Registry and against your internal suppression lists on the dialing path. The registry side of that is the US list. The internal suppression side is the piece that carries straight into a Canadian campaign, because the internal do not call list is the one Canadian obligation with no exemption attached to it. Kixie states plainly on that page that customers remain responsible for their own calling practices and legal review, which is the right way to read any vendor control: it enforces what you configure, it does not decide what the law requires of you.

What that changes operationally is the handoff. A stop-calling request captured as a call outcome in the dialer, written to the CRM automatically, is a record with a timestamp you can produce 3 years later. The same request written in a notes field is not. PowerDialer sessions advance through a list rather than waiting for a rep to click, which is exactly why the list has to be clean before it loads, and ConnectionBoost handles local presence and outbound number reputation, which is a separate problem from consent and should not be confused with one. A caller ID that connects more often does nothing about whether you were permitted to dial.

Evaluate any tool on this chain and not on its category label. What does the rep no longer do by hand. Where does the suppression request get written. What stops a list that has not been re-scrubbed from loading. Who can pull the evidence when a complaint arrives, and how long does it take them.

What a telemarketing violation costs in Canada

Under the Telecommunications Act, contravening a CRTC requirement made under its unsolicited telecommunications power carries an administrative monetary penalty of up to $1,500 for an individual and up to $15,000 for a corporation.

Read the next two provisions before you decide that is cheap. A violation continued on more than one day is a separate violation for each day it continues. And the Commission may make public the nature of the violation, the name of whoever committed it, and the penalty amount. So the exposure is a daily multiplier plus your name in a published decision, which for most companies is the more expensive half.

On the electronic side the ceilings are an order of magnitude up: CASL’s maximum penalty for a violation is $1,000,000 for an individual and $10,000,000 for anyone else. That asymmetry should influence which channel you launch first into Canada and how much evidence you keep behind it.

Checklist before a Canadian campaign goes live

  • Classify every channel and purpose in the campaign, call by call, before any list is uploaded.
  • Register the organization with the National DNCL Operator, exempt or not, and leave time for the Dun and Bradstreet identity match.
  • Buy a subscription sized to your actual area codes if the calls are not exempt, and compare the per-area-code and query options against national coverage.
  • Set a re-scrub interval against the 31 day window and make the dialer reject lists older than it.
  • Document every exemption you rely on, including which 18 month or 6 month event supports an existing business relationship.
  • Store consent in a producible form: the form itself, or the recording, or the third party record.
  • Stand up one internal do not call list, with a 14 day path from the rep to every client system and 3 year retention.
  • Configure calling windows centrally from the recipient’s time zone, and fail closed when the time zone is unknown.
  • Treat prerecorded and automated calls as a separate approval with their own consent standard.
  • Map email and text sequences under CASL separately, with contact details good for 60 days and unsubscribes honoured within 10 business days.
  • Put National DNCL access, scrubbing, suppression sync, scripts, records and complaint escalation into the vendor contract, then audit against it.
  • Close the side doors: no list exports, no shadow dialers, no rep-maintained suppression spreadsheets.
  • Keep the records a complaint needs: list source, scrub result, consent evidence, script version, call timestamps, vendor instructions, system logs.

When a telemarketing complaint arrives

Consumers file complaints through the National DNCL and the CRTC. Your job on the receiving end is boring and procedural, which is the point.

Preserve the records. Do not edit or delete anything after a complaint lands, because an altered log is a worse problem than the call ever was. Route the inquiry to whoever owns legal and compliance rather than letting a sales manager answer a regulator. Then reconstruct the call: where the number came from, when it was last scrubbed, what exemption or consent was relied on, what the rep said, what was recorded afterward. If you cannot assemble that in an afternoon, the gap you just found is the thing to fix, complaint or no complaint.

Frequently asked questions

Does a US company calling into Canada have to follow these rules?

Yes. The National DNCL states the rules apply regardless of where the call originates, and telemarketers calling Canadian consumers from outside Canada must comply with the National DNCL Rules.

How long before a newly registered number is off limits?

31 days from the date the consumer registers. After that the National DNCL Rules prohibit calling it, which is why a stale scrub is the usual cause of a complaint rather than a missing subscription.

Do we still register if all our calls are exempt?

Yes. Registration is required for organizations on whose behalf telemarketing is conducted even when the calls are exempt. The paid subscription is what you skip, not the registration.

How long does an internal do not call request last?

3 years. The name and number must be added within 14 days of the request, and if you are calling for a client, added to that client’s own list within the same 14 days.

Can we call an existing customer who asked us to stop?

No. The Telecommunications Act writes the existing business relationship exemption to cover a person who has not made a do not call request to the organization the call is for, so the request ends the exemption.

Are business-to-business calls into Canada exempt?

They are exempt from the National DNCL Rules, and business numbers are not to be registered on the list. The Telemarketing Rules, the automated dialing rules and the internal do not call list obligation still apply.

Does CASL cover our outbound calls?

Not your voice calls. CASL governs commercial electronic messages sent to an electronic address, which the Act defines to include email, instant messaging and telephone accounts, so your texts and emails are in scope while the calls themselves run under the telemarketing side.

Sources

Sources verified by the Kixie Research Team on November 18, 2026.

Reassigned Numbers Database Checks and the TCPA Safe Harbor

TL;DR: The Reassigned Numbers Database answers one narrow question, and most outbound teams ask it wrong. You submit a phone number plus the date you obtained consent, and the FCC database run by SomosGov returns yes, no, or no data. Only a response of no can support the TCPA safe harbor rule in 47 CFR 64.1200(m), and even then it covers you only when the database itself returned that no in error, with the caller carrying the burden of proof and persuasion. A no data response carries no protection at all when the consent date falls before January 27, 2021, because the database holds nothing earlier. Two more limits decide how you build the workflow. Carriers report permanent disconnects once a month, on the 15th, so every answer is a monthly snapshot rather than a live line check, and a number ported to another provider is not permanently disconnected at all, so a port never surfaces as a yes. The 2019 FCC order that created the database also set a 45 day minimum aging period before a disconnected number can be reassigned to someone new. Query access is a paid subscription with tiers, prorated upgrades, rollover of unused queries, and a top off that buys ten percent more queries for ten percent of the subscription price. Push the output into the suppression list your team already runs, log the number, the date submitted, the response, and the action taken, and treat the result as one input to a contact decision rather than permission to dial.

A phone number is not a person. It is a lease. A consumer cancels service, switches carriers, lets an account lapse, and the carrier eventually hands that number to somebody else. Your CRM does not notice. The record still says the contact agreed to hear from you in 2022, so the dialer keeps calling, and one day a stranger picks up who never agreed to anything.

That is the exposure the Reassigned Numbers Database exists to reduce. It is not a permission slip and it is not a line check. It is a dated lookup against carrier disconnect reports, and it only helps teams that understand exactly how narrow the answer is.

What the Reassigned Numbers Database Actually Tells You

The Reassigned Numbers Database, usually shortened to RND, came out of the Federal Communications Commission’s Second Report and Order, released December 13, 2018, and published as a final rule at 84 FR 11226 effective March 26, 2019. The FCC selected SomosGov, Inc. through a competitive procurement to run it.

Here is the mechanic that matters. Under the delivery restrictions in 47 CFR 64.1200, reporting carriers keep the most recent date each North American Numbering Plan number they hold was permanently disconnected, and they report those dates to the administrator on the 15th of each month. The database is that pile of carrier reports. When you query it, you are not asking whether a number is live, who owns it, or whether you may call. You are asking one question: has this number been permanently disconnected since the date I am giving you?

The rule also defines permanently disconnected tightly. A number counts when the subscriber has permanently relinquished it or the provider has permanently reversed its assignment so the number is disassociated from that subscriber. Everything else is out of scope.

How a Database Query Works Step by Step

Two values go in. The phone number, and a date.

The date is where teams get sloppy. It is supposed to be the date you obtained consent, or the last date you can defend that the intended person was still reachable at that number. It is not the lead creation date, not the import date, and not whatever timestamp was easiest to pull from the CRM. Submit the wrong date and the query still returns a clean answer, just to a question you did not mean to ask.

  1. Pull the number and the consent date from the system of record, not from a spreadsheet copy.
  2. Normalize the number so it matches the accepted query format.
  3. Submit the lookup through your registered access path or a registered agent.
  4. Write the response back to the record along with the query timestamp and the exact date you submitted.
  5. Apply a documented decision rule before the record reaches a dialer or a messaging queue.

Access is not free and it is not open. Callers register, then buy a subscription. The administrator publishes tiered subscription terms with volume discounts, and three documented ways to handle running out mid term: buy a new subscription once you have used at least 75% of your queries, which rolls the remainder forward; upgrade to a higher tier on a prorated basis; or top off by paying ten percent of the subscription price for ten percent more queries. Subscription pricing last changed effective April 28, 2025, so confirm current tiers with the administrator before you budget a program around a number somebody quoted you last year.

Reassigned Numbers Database Responses and the Safe Harbor Rule

Three responses come back: yes, no, or no data. The administrator maps each one to the safe harbor rule directly, and the mapping is less generous than most teams assume.

Pale violet diagram of one frosted glass channel splitting into three paths that end in a closed cap, a bright open ring, and a frayed open mouth.
  • Yes. The number was permanently disconnected on or after your consent date. The safe harbor rule does not apply. Suppress the record and re-verify through another channel.
  • No. The number has not been permanently disconnected since consent was provided. This is the only response where the safe harbor rule can apply.
  • No data. The safe harbor rule does not apply, because the number was not permanently disconnected and the consent date predates January 27, 2021. The database simply has nothing to say about that period.

That January 27, 2021 floor is the single most expensive detail in this topic. If you are working an aged list, a reactivation campaign, or a book of dormant accounts, a large share of your consent dates sit before that line, and every one of those queries comes back no data. You paid for the query. You got no protection from the rule.

Now read the safe harbor rule itself. Under 47 CFR 64.1200(m), a caller avoids liability for a call to a reassigned number only by demonstrating two things: that they queried the database against the most recent reported numbering information and received a response of no, and that the call happened because the database erroneously returned that no. The rule puts the burden of proof and persuasion on the caller. The Federal Register summary of the 2019 order says the same thing in plainer words, describing the rule as a limited safe harbor for a caller that relies upon inaccurate information provided by the database.

So the protection is for database error. It is not for diligence. Querying every number and getting honest answers earns you nothing under this rule if the answer was right and you called anyway. That is a narrower bargain than the marketing around compliance tooling usually suggests, and it should change how you write your decision rules. This is general information about a federal rule, not legal advice; your counsel owns the call on what any of it means for your program.

What the Database Will Never Catch

Three blind spots, all of them structural, none of them fixable by querying more often.

Ports are invisible. The rule says it outright: a number ported to another provider is not permanently disconnected. Your contact can move from one carrier to another and keep the number, and nothing about that transaction enters the database. Good, because the person is the same. Worth knowing, because a quiet number is not evidence of anything.

The data is a monthly snapshot. Carriers report on the 15th of each month. A number disconnected on the 16th will not appear in the database for roughly four weeks. The 2019 order set a 45 day minimum aging period before a permanently disconnected number may be reassigned to a new subscriber, which buys some margin, but the gap is real and your recheck cadence has to account for it.

Smaller carriers came in later. The rule gave reporting carriers serving 100,000 or fewer domestic retail subscriber lines, counted across affiliates on their most recent Form 477, an extra six months to start keeping records and filing reports. Coverage is broad, but it is not and never was instant and universal.

None of that makes the database useless. It makes it one dated signal among several, which is the only way it was ever designed to be used.

Who Should Run Reassigned Numbers Checks

The honest filter is list age, not department. If every number you dial was collected this week from an inbound form, the database has little to tell you. The further your consent dates sit from today, the more the lookup is worth.

  • Sales teams reactivating dormant opportunities or working a purchased or inherited list.
  • Customer success and service teams contacting accounts after long inactivity.
  • Messaging programs built on numbers collected through forms, events, or registration.
  • Collections and recovery operations working historical records by definition.
  • Contact centers merging data from several systems, where consent dates arrive inconsistent.

Eligibility, registration, credentials, and usage terms are set by the administrator and the FCC, not by your vendor. Check them before you assume your team or your agent can query at all.

Where Database Results Belong in the Dialing Workflow

A lookup that lands in a report nobody reads has changed nothing. The result has to reach the thing that decides whether the call goes out.

Pale violet diagram of four frosted glass streams feeding one wide filter bar, with a single narrow channel continuing to three stacked tiles and two stopped fragments beside it.

For most teams that is the suppression list, because that is already the mechanism standing between a record and a dialer. The same list carrying your opt outs, your internal do not call entries, and your National Do Not Call Registry checks is the natural home for a yes response. Kixie’s National DNC integration helps teams check calling lists against the registry and apply suppression workflows, and the same workflow is where an RND result belongs; customers remain responsible for their own calling practices and legal review. The point is that one list governs the PowerDialer, not four systems applying four different rules.

Keep the controls distinct in your head even when they share a list. Reassignment screening asks whether the number changed hands. Consent records document who agreed, to what, how, and when. Suppression entries record a decision not to contact. Number validation checks format and numbering plan validity. A number can pass all four and still be wrong to call, and it can fail one while the other three look fine. Neither state telemarketing laws nor state do not call lists stop applying because a federal database said no.

A Reassigned Numbers Database Checklist for Contact Operations

Pick the consent date field and write it down

Name the exact CRM field you will submit and why it is defensible. Then stop anyone from quietly substituting a different one when that field is null.

Clean the numbers before you pay for queries

Normalize formats, strip duplicates, flag records with missing or conflicting consent dates. A query against a bad record returns a confident answer to the wrong question, and you paid for it.

Set the trigger, not a vague cadence

Decide the event that fires a check. Before a dormant list goes live. Before a reactivation campaign. After a defined period of inactivity. The monthly reporting cycle and the 45 day aging period are the facts your recheck interval has to respect.

Map every response to one action

Yes, no, no data, and technical failure each need a defined outcome. Write down what suppresses, what proceeds, what routes to review. If a response has no mapped action, someone will improvise at the worst moment.

Log enough to prove what you did

The number submitted, the date submitted, the response, the query timestamp, the system that ran it, and the action taken. The rule puts the burden of proof on the caller, so an unlogged query is an argument you cannot make later.

Decide what happens when the lookup fails

Service outages, malformed records, duplicate submissions, delayed responses. Automation should fall into a review path, never default to dialing.

Put one person on the rules

Database specifications, subscription terms, carrier practices, and regulations all change. Assign an owner to read the administrator’s notifications and to test that routing and suppression still behave the way the documentation says.

Database Mistakes That Cost Teams the Safe Harbor Rule

  • Reading a no as permission. It is a statement about disconnection records, nothing more. Consent, revocation, registry status, and campaign purpose all still govern the call.
  • Submitting a convenient date. The response only means something in relation to the date you sent. The wrong field produces a technically correct, operationally worthless answer.
  • Treating no data as a soft no. For any consent date before January 27, 2021, the rule gives you nothing. Treating it as reassurance is the most common way teams pay for queries and keep the full exposure.
  • Checking once and trusting it forever. Carriers report monthly. A clean record from four months ago is four reporting cycles stale.
  • Querying without logging. The caller carries the burden of proof and persuasion, so an undocumented query is not evidence of anything.
  • Letting systems disagree. When the CRM, the dialer, the messaging platform, and the suppression list each apply their own rules, the loosest one decides who gets called.

Reassigned Numbers Database FAQs

Does the database tell you who owns the number now

No. It does not identify any current subscriber. It returns a dated answer about reported permanent disconnection, and that is the whole scope.

Can a query confirm a number is active

No. It is not a line check and carries no real time signal about whether a number rings, is in service, or still belongs to the person you meant to reach.

Does a no response establish consent

No. Consent is a separate record with its own source, scope, timestamp, and revocation history. The two controls answer different questions and neither substitutes for the other.

How often should a team run checks

There is no universal cadence in the rule. Set one against your own list age, campaign design, and risk posture, bounded by the fact that carriers report monthly on the 15th.

Can lookups be automated

Yes, inside the access and query methods the administrator defines, and registered callers may also use a registered agent. Confirm current eligibility, fees, and usage terms with the administrator, and build automation that preserves every response and handles errors without defaulting to contact.

Is querying the database enough for TCPA compliance

No. The safe harbor rule in 47 CFR 64.1200(m) is narrow, covering only a call that followed a no response the database returned in error. It sits inside a larger program covering consent, revocation, registry requirements, identification rules, suppression, and recordkeeping, and it does not replace any of them.

A stored phone number is not a permanent identity, and the Reassigned Numbers Database is the dated, monthly, federally defined way to test that assumption on one specific axis. Pull your list, look at how many consent dates sit before January 27, 2021, and you will know within an hour whether this is a workflow worth building or a line item worth skipping.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 18, 2026.

Home Improvement Call Center Script Starts With Who Dialed

TL;DR: A home improvement call center script is two different legal animals depending on who placed the call, and most template libraries never mention it. The federal telemarketing rule exempts calls where the sale is not completed and no payment is taken until after a face to face presentation, which is exactly the appointment setting model, but four requirements survive that exemption: no threats or intimidation, caller ID transmission to the homeowner, the do not call provisions, and outbound calls to a residence only between 8 a.m. and 9 p.m. local time at the called person’s location. Inbound calls a homeowner places after seeing your ad are exempt too, right up until the agent upsells, and the exemption stops covering that upsell. Separately, the telephone rules require a written do not call policy available on demand, trained agents, every do not call request recorded at the moment it is made and honored within no more than ten business days, and the individual caller’s name plus a reachable number that is not a 900 number. Then the appointment pays off in the living room, and a contract signed there for $25 or more carries a right to cancel until midnight of the third business day, where business days exclude Sunday and federal holidays, the buyer has to be told orally, and the paper cannot be sold to a finance company before midnight of the fifth business day. So the script’s job is to book a qualified visit, not to pre close one. Kixie’s PowerDialer auto dials up to 4 numbers in parallel and its automated lead caller prompts an agent to call a new lead as soon as a web form comes in.

Most home improvement call centers write the script backwards. Somebody drafts a warm opener, bolts on five qualification questions, adds a rebuttal for every objection the floor hears, and ships it. Then the appointment rate looks fine and the cancellation rate quietly eats it. Reps book visits that never happen, estimators drive forty minutes to a homeowner who thought they were getting a phone quote, and signed contracts come apart three days later.

The script is not the problem. A home improvement call center script that nobody mapped to the actual transaction is describing something it does not understand.

What a Home Improvement Call Center Script Has to Do Before It Sells

Start with the actual job. A home improvement call center does not close anything on the phone. It qualifies a property, confirms the work is in scope, and books a human being to stand in somebody’s kitchen. That is the whole product of the phone call.

That matters because the federal rules are built around exactly that split. The telemarketing rule exempts telephone calls in which the sale is not completed, and payment or authorization of payment is not required, until after a face to face sales presentation by the seller. Read that again with your own process in mind. If your agent books an estimate and nobody takes a card number on the phone, most of the rule does not reach the call.

Most. Not all. The exemption carves out four things that still apply, and those four are the spine of any script you write.

So the agent is not selling. The agent is qualifying a visit and setting an expectation the estimator can meet. Every line in a home improvement call center script either moves toward that or gets cut.

Who Dialed Decides Which Rules the Script Follows

Here is the distinction that should sit at the top of your agent training, and almost never does.

Your call center dialed the homeowner. That is an outbound telemarketing call. The face to face exemption applies if the sale closes in the home, but four requirements survive it. No threats, intimidation, or profane language. The telephone number, and the telemarketer’s name where the carrier makes it available, has to reach the homeowner’s caller identification service, with a permitted substitution of the seller’s name and a customer service number answered during regular business hours. The do not call provisions apply in full. And outbound calls to a person’s residence are an abusive practice outside 8 a.m. to 9 p.m. local time at the called person’s location, without that person’s prior consent.

That last one is a dispatch rule, not a script rule. Local time at the called person’s location. A center in Phoenix working an Eastern list is done dialing at 6 p.m. its own clock, and no opener fixes that.

The homeowner called you after seeing an ad. Calls a customer initiates in response to an advertisement through any medium other than direct mail are exempt as well, with named exceptions for investment, debt relief, technical support and certain business opportunity offers that have nothing to do with gutters. One carve out does apply to you: the exemption does not cover any instances of upselling included in the call.

Think about what upselling means on a real inbound call. A homeowner calls about a leaking water heater. The agent handles it, then offers to have the estimator price the furnace while he is there. That second offer is an upsell inside an inbound call, and it falls outside the exemption even though the first half of the conversation did not.

The homeowner called you with no prompting at all. Calls a customer initiates that are not the result of any solicitation are exempt, with the same upselling carve out attached.

Three doors into the same phone room, three different sets of obligations, one home improvement call center script. That is why a script written as pure copy fails. The script has to branch on how the call started, which means your agents need to know, and which means the record has to say.

The Do Not Call Work Happens Before the Script Opens

The telephone rules set a floor your script sits on top of. Any entity making telemarketing calls to a residential subscriber needs procedures for maintaining a list of people who ask not to be called, and those procedures carry four minimum standards.

A written policy for maintaining a do not call list, available on demand. Personnel engaged in any aspect of telemarketing informed and trained in the existence and use of that list. Every do not call request recorded and placed on the list at the time the request is made, honored within a reasonable time that may not exceed ten business days. And identification on the call: the name of the individual caller, the name of the entity on whose behalf the call is made, and a telephone number or address where that entity can be reached, which may not be a 900 number.

The separate telemarketing rule adds the national registry. Calling a number on the Commission’s do not call registry is an abusive practice unless the seller can demonstrate an express written agreement from that person naming the party and the number, or an established business relationship with a person who has not since asked to stop.

None of that is script copy. All of it decides whether the script ever gets read out loud. Kixie’s compliance workflows support checks against the National Do Not Call Registry and internal suppression lists, and the calling practices and legal review stay with the company doing the dialing.

The Inbound Script for a Homeowner Who Called You

Open, find out what broke, confirm you can fix it, book the visit. Four moves.

Agent: “Thanks for calling [Company], this is [Agent]. What’s going on at the house?”

Agent: “Got it. How long has it been doing that?”

Agent: “What’s the address, so I can check that we cover it?”

Agent: “And the best number to reach you at if we get disconnected?”

Agent: “Here’s how it works. [Role] comes out, looks at it, and gives you a written price before anything gets scheduled. I have [Option A] or [Option B]. Which one is easier?”

Notice what is missing. No price. No range. No “typically our customers see.” The agent on the phone has not seen the house, and a number said out loud becomes the number the homeowner remembers when the estimator says something different.

If the project is out of scope or out of the service area, say so in the first ninety seconds. “That’s outside what we do, and I don’t want to send somebody out just to tell you that.” A booked appointment you cannot serve costs an estimator half a day and a review.

And if the conversation turns into an upsell, remember the exemption stops there. Treat that part of the call the way you would treat an outbound one.

The Outbound Script for a Lead Who Asked for a Quote

Outbound to a form fill is still outbound. The agent identifies, states the reason accurately, and checks whether now works.

Agent: “Hi, is this [Name]? This is [Agent] with [Company]. You filled out a form about [project type] on [date]. Is now a bad time?”

Agent: “Takes two minutes. What are you trying to fix or change?”

Agent: “Where’s the property?”

Agent: “Any timeline you’re working against? Permit, closing, insurance, anything like that?”

Agent: “Next step is [approved next step], no charge, no obligation. I’ve got [Option A] or [Option B].”

When the homeowner does not remember filling anything out, do not argue the point. Read back the source and the date if the record has them, offer to take the number off the list, and log the outcome. An agent who wins that argument has just created a do not call request that somebody has to record anyway.

Pace matters more than wording on this call. A power dialer that auto dials up to 4 numbers in parallel changes what an agent does between conversations, which is where most of a shift actually goes. Fewer gaps means less call hesitancy, and call hesitancy is what quietly eats an afternoon.

Qualification Questions That Earn the Appointment

Ask what changes the routing. Nothing else.

Translucent white glass channel branching into five paths on a pale pink ground, four tapering to blunt stubs and one thicker branch continuing to a small rounded pad
  • What are you looking to repair or replace?
  • When did it start?
  • What is the property address?
  • Do you own the home?
  • Is anything actively leaking, sparking, or unsafe right now?
  • When would you want the work done?
  • Who else looks at the quote before a decision gets made?
  • What times are usually open for you?

Eight questions. Every one of them routes the lead, sizes the job, or sets the appointment. Drop any question your dispatch board does not actually use, because every extra one buys you a shorter call and a colder homeowner.

The decision maker question earns its place for a specific reason, and it is not a closing trick. If the person signing is not home when the estimator arrives, the visit produces a second visit. Ask it on the phone or pay for it in windshield time.

The In Home Close Comes With a Cancellation Window

This is the part the script library never covers, and it is the part that decides whether a booked job stays booked.

Translucent white glass slab on a pale pink ground with a rectangular window cut through it, a small glass wedge lifted out above the opening and three shrinking glass beads trailing away

A sale, lease, or rental of consumer goods or services where the seller personally solicits the sale, including sales that follow an invitation by the buyer, and the agreement to purchase is made somewhere other than the seller’s place of business, is a door to door sale once the purchase price hits $25 or more at the buyer’s residence. Your phone booked kitchen table signature is squarely inside that definition. The invitation came from the homeowner and it does not matter.

What follows from that is concrete:

  • The buyer gets a completed receipt or copy of the contract at the time it is signed, in the same language used in the oral sales presentation, showing the date and the seller’s name and address.
  • Right next to the signature line, in bold face type of at least 10 points, a statement that the buyer may cancel the transaction at any time prior to midnight of the third business day after the date of the transaction.
  • Two copies of a completed cancellation notice captioned either “NOTICE OF RIGHT TO CANCEL” or “NOTICE OF CANCELLATION,” in ten point bold face, with the seller’s name and business address and the date by which notice may be given already filled in.
  • The buyer has to be told orally about the right to cancel at the time of signing. Misrepresenting that right in any manner is itself a violation.
  • Business day means any calendar day except Sunday or a federal holiday. Sign on a Friday before a Monday holiday and the clock runs into Thursday.
  • The seller cannot negotiate, transfer, sell, or assign the note or other evidence of indebtedness to a finance company or third party before midnight of the fifth business day after signing.
  • A valid cancellation gets all payments refunded, trade ins returned, and any negotiable instrument cancelled within 10 business days.

There is an exclusion worth knowing, and a trap inside it. A transaction is outside the rule when the buyer initiated the contact and specifically asked the seller to come out to repair or perform maintenance on personal property. But if the seller then sells additional goods or services beyond the replacement parts needed for that repair, those additional goods or services are not covered by the exclusion. The service call stays outside. The replacement system sold during the service call does not.

Now read your phone script again. Every line that creates urgency to sign today is working against a rule that gives the homeowner three business days anyway. “This price is only good while the estimator is standing there” does not shorten the cancellation window. It just gives a hesitant buyer a reason to use it.

The script that holds up says the opposite. The visit is free, the price is written down, and the homeowner has time to think about it. Teams that say that on the phone send estimators into warmer houses.

Voicemail and Text Templates for the Calls Nobody Answers

Most dials do not connect, and the message is where the next conversation starts.

Voicemail, outbound to a lead: “Hi [Name], it’s [Agent] at [Company], calling about the [project type] request on [date]. You can reach me at [number] between [hours]. Again, [Agent] at [number].”

Name, company, reason, number, number again. Nothing else. An agent who improvises a voicemail on every no answer is writing a new one forty times a shift, which is time that could have gone into the next dial. Recording the message once and letting the system drop it is what Voicemail Drop does, and the agent moves to the next call while it plays.

Missed inbound callback: “Hi, this is [Agent] at [Company] returning a call from this number. What’s going on at the house?”

Text after a booked appointment: “[Name], [Role] from [Company] is set for [date] at [time] at [address]. Reply C to confirm or R to reschedule. Reply STOP to opt out.”

Keep the appointment text to confirmation and logistics. A text that starts selling turns a service message into a marketing one, and the consent you have for one is not automatically the consent you have for the other.

Objections Your Agents Will Hear on Every Shift

Clarify, ask one question, offer a proportionate next step. Do not argue a homeowner out of a reasonable position.

“I’m just getting prices.” “That’s fine, that’s what the visit is for. Do you want the written number so you have something to compare, or are you not ready for anybody to come out yet?”

“I need to talk to my wife.” “Makes sense. When is a time you’re both around? That way nobody has to repeat it.”

“How much is this going to run?” “I’d be guessing, and a guess over the phone helps nobody. [Role] measures it and writes the price down while he’s there, and there’s no charge for that.”

“I’m getting three bids.” “Good, you should. What’s going to decide it for you, price or timeline?”

“Just send me something in email.” “I can do that. The email won’t have a price in it though, because nobody’s seen the house. Do you want the email, or do you want the number?”

Every one of those grants the premise first. The homeowner comparing bids is behaving sensibly, and a rebuttal that treats that as an obstacle reads as pressure. Pressure on the phone becomes a cancellation on day two.

What the Agent Logs When the Call Ends

A script with no disposition behind it is a script you cannot coach.

At minimum, every call should leave the direction of the call, how the lead arrived, the outcome, the next step with an owner and a date, and any do not call request with the timestamp it was made. That last one is not optional housekeeping. The rule says the request gets recorded at the time it is made.

Call disposition logging is what turns that from a note somebody meant to write into a field a manager can filter on. Calls, texts, outcomes and recordings logging into the CRM automatically is the difference between a floor you can inspect and a floor you can only guess at.

Then inspect the right number. Not dials. Not even appointments booked. Look at appointments that held, and at the gap between booked and held by agent. One agent booking 14 a week with 4 holding is not outperforming the agent booking 9 with 8 holding. He is generating windshield time.

If you record calls, know which rule you are under. Federal law makes it lawful for a person who is a party to the communication, or who has the prior consent of one party, to intercept it, unless the interception is for a criminal or tortious purpose. Several states require every party to agree, so the recording notice belongs in the opener and not in a policy document nobody reads.

Home Improvement Call Center Script Mistakes That Cost Appointments

Five patterns show up in nearly every home improvement call center script that gets audited on the floor.

Quoting a price to get off the phone. The agent gives a range, the estimator gives a number, and the homeowner hears a bait and switch that was really just a guess.

One script for inbound and outbound. They are different legal animals and different conversations. The homeowner who called you has a problem right now. The homeowner you called is doing something else.

Treating the appointment as the finish line. Booked is not held, and held is not sold. Measure through.

Burying the cancellation right. It is required, it is going to be disclosed, and the homeowner is going to find out anyway. Scripts that treat it as an awkward disclosure teach agents to rush past it, which is exactly the behavior the rule calls out.

No branch for the homeowner who should not be sold. Out of area, renter without authority, project your crews do not do. Give the agent clean language to end it, and give them credit for ending it fast.

Home Improvement Call Center Script Questions Teams Ask

Does the telemarketing rule apply if we only book estimates?

Partly. The exemption covers calls where the sale is not completed and no payment is taken until after a face to face presentation, which fits the estimate model. But the conduct provisions, the caller identification requirement, the do not call provisions, and the 8 a.m. to 9 p.m. residential calling window all still apply to outbound calls.

Do inbound calls from our ads have the same rules?

Calls a customer initiates in response to an advertisement are exempt from the telemarketing rule, with named exceptions and one that will reach you: the exemption does not cover upselling that happens during the call.

How long does a homeowner have to cancel a contract signed at home?

Until midnight of the third business day after the date of the transaction, for a door to door sale of $25 or more at the residence. Business day excludes Sunday and federal holidays, so a Friday signature before a Monday holiday runs the window into Thursday.

Can agents give a price range over the phone?

They can, and most teams regret it. The phone price becomes the anchor, the written price becomes the disappointment, and the cancellation window is already open.

What does the agent have to say about who is calling?

The name of the individual caller, the name of the company on whose behalf the call is made, and a telephone number or address where the company can be reached, and that number cannot be a 900 number.

How many questions should a qualification script have?

As many as your dispatch board actually consumes. Eight is a workable ceiling for home improvement teams booking in home estimates, and anything past that is usually somebody’s old spreadsheet.

Run the Script Against One Week of Recordings

Writing the home improvement call center script is the easy half. Pull twenty recordings from last week, five per agent, and mark four things on each one: whether the agent identified the company and themselves in the first fifteen seconds, whether a price was quoted, whether the next step had a named owner and a date, and whether any do not call request got logged while the caller was still on the line.

That is a one hour exercise and it will tell you more than another rewrite. Fix the first broken behavior you can see on tape. Then check whether appointments held moved, because that is the only number in this whole process that pays anybody.

Sources

Sources verified by the Kixie Research Team on November 16, 2026.

How to Make Outbound Calls as a Financial Advisor

TL;DR: Learning how to make outbound calls as a financial advisor is mostly a question of which rulebook your script lands in, and the trigger is different in each one. FINRA Rule 2210(f)(1) treats an unscripted live call as a public appearance, while 2210(f)(4) makes any script used in connection with that appearance a communication in its own right, categorized by audience, content and use. From there the line is a headcount: Rule 2210(a)(2) calls a written communication reaching 25 or fewer retail investors in any 30 calendar-day period correspondence, supervised under Rule 3110(b), and 2210(a)(5) calls anything reaching more than 25 a retail communication, which needs a registered principal’s approval before the earlier of its use or its filing under 2210(b)(1)(A), plus retention under SEA Rule 17a-4(b) with a copy, the dates of first and last use, and the approving principal’s name. One rep’s call block clears 25 in a day, so the script is a retail communication from the first week. Regulation Best Interest uses a different trigger entirely: Regulation Best Interest attaches the moment the call carries a recommendation to a retail customer, and it demands the disclosure of capacity, material fees and costs, and type and scope of services in writing, prior to or at the time of the recommendation, which a phone call cannot deliver. That single word is the reason the first call is a fit check rather than a pitch. Registered investment advisers hit the same hinge from the other side: the Advisers Act marketing rule excludes extemporaneous, live, oral communications from the advertisement definition, and the SEC’s adopting release states that extemporaneous communications do not include prepared remarks or speeches, such as those delivered from scripts, with the record kept under the advisers books and records rule at 204-2(a)(11)(i)(A) as the script, the preparatory materials, or a recording of the call. Projections are the live edge: the SEC approved SR-FINRA-2026-004 on October 15, 2026, adding Rule 2210(d)(1)(F)(iv), which permits a projected performance or targeted return only with written policies and procedures on audience relevance and disclosure of the criteria, assumptions, risks and limitations.

Most advice about advisor prospecting stops at tonality. It tells you to sound natural, open with a question, and avoid pitching too early. Fine. None of that answers the question a compliance officer will ask on Monday, which is what the script is, who approved it, and where the copy lives.

So start there. The words you say on a first call are not governed by one rule. They are governed by whichever rulebook your firm registered under, and each one uses a different trigger to decide when the call stops being a conversation and starts being a regulated communication. Get the trigger right and the script writes itself around it.

This article explains general sales process and the published rules behind it. It is not legal or compliance advice. Your firm’s compliance team approves your lists, scripts, disclosures, recording practices, calling hours and retention.

Why a Financial Advisor Outbound Call Script Changes the Rules

FINRA Rule 2210(f)(1) describes a public appearance as a seminar, forum, radio or television interview, or other speaking activity that is unscripted and does not amount to a retail communication, institutional communication or correspondence. Speaking off the cuff is held to the content standards in 2210(d)(1) and supervised under written procedures. That is the lighter path.

Then comes 2210(f)(4). Any scripts, slides, handouts or other written materials used in connection with a public appearance are themselves communications, and the firm has to comply with every applicable part of the rule based on that communication’s audience, content and use. Read those two paragraphs together and the hinge is obvious. The moment you write the call down, you have created a second thing to govern.

That matters because a script is not optional on a calling floor. Reps need one. Managers need one to coach against. New hires need one on day three. So the practical question is not whether to have a script. It is what the script becomes once it exists.

Whatever it becomes, the content standards in 2210(d)(1) still apply. Communications must be based on principles of fair dealing and good faith, must be fair and balanced, and must give a sound basis for evaluating the facts. No false, exaggerated, unwarranted, promissory or misleading statement or claim. Paragraph (d)(1)(D) adds balanced treatment of risks and potential benefits, consistent with fluctuating prices and the uncertainty of dividends, rates of return and yield. Paragraph (d)(1)(E) tells you to consider the nature of the audience and pitch the explanation to it.

Paragraph (d)(1)(F) is the one that kills most opening lines. Communications may not predict or project performance, imply that past performance will recur, or make any exaggerated or unwarranted claim, opinion or forecast. An opener built on a number the prospect could hit is a forecast. Cut it.

There is a live exception worth tracking. On October 15, 2026 the SEC approved SR-FINRA-2026-004 (Release No. 34-106675), which amends Rule 2210 to let a member project performance or provide a targeted return for a security, a securities portfolio, or an asset allocation or other investment strategy, subject to conditions. The conditions are in 2210(d)(1)(F)(iv): the member adopts and implements written policies and procedures reasonably designed to make sure the communication is relevant to the likely financial situation and investment objectives of the intended audience, and the member supplies enough information for that audience to understand the criteria and assumptions used and the risks and limitations of relying on the figure. FINRA’s rulebook entry lists the amendment without an effective date, so the operative date arrives with FINRA’s implementation notice. Until then, treat projections in a calling script as off limits.

The 25 Retail Investor Line Every Outbound Call Script Crosses

Here is the part that surprises people. The category your script falls into is decided by a headcount, not by content.

Shallow frosted glass tray split by an upright glass divider, a few loose glass discs on the near side and a dense crowd of violet and pink glass discs on the far side, one disc lifted above the divider, on a pale violet ground.

Rule 2210(a)(2) defines correspondence as any written (including electronic) communication distributed or made available to 25 or fewer retail investors within any 30 calendar-day period. Rule 2210(a)(5) defines a retail communication as the same thing distributed or made available to more than 25 retail investors in that window. And 2210(a)(6) defines a retail investor as any person other than an institutional investor, regardless of whether that person has an account with the firm. Prospects count.

Now do the arithmetic on a normal week. A rep running a list through a dialer reaches more than 25 prospects in a single block. The script is a retail communication by Tuesday.

The two categories carry different obligations, and the gap between them is wide:

  • Correspondence is subject to the supervision and review requirements of Rule 3110(b) and its supplementary material on correspondence review, and is retained under that supplementary material and Rule 4511.
  • Retail communications require an appropriately qualified registered principal to approve each one before the earlier of its use or its filing with FINRA’s Advertising Regulation Department, under 2210(b)(1)(A).
  • Retention for retail communications runs under SEA Rule 17a-4(b), and 2210(b)(4)(A) spells out what the record has to contain: a copy of the communication, the dates of first and last use, the name of the registered principal who approved it and the date of approval, and the source of any statistic, chart or projection used in it.

Read that last bullet again. Dates of first and last use. That is a version-control requirement sitting inside a communications rule, and it means an edit to the opener is not a small thing. The old version has a last-use date. The new version needs its own approval.

Newer firms carry one more step. Rule 2210(c)(1)(A) requires a member, for one year from the date its FINRA membership became effective in the CRD system, to file with the Advertising Regulation Department at least 10 business days before first use any retail communication published or used in electronic or other public media. The rule’s own list of media includes telephone and audio recording. A first-year firm’s calling script is squarely in scope, and 2210(c)(5) requires each filing to carry the actual or anticipated date of first use plus the name, title and CRD number of the approving principal.

So the sequence is approval first, then dialing. Not the other way around. A floor that writes a new opener on Wednesday and runs it Wednesday afternoon has skipped a step that leaves a trail in the call logs.

What Regulation Best Interest Does to a Financial Advisor Outbound Call

Regulation Best Interest ignores headcount. Its trigger is a recommendation.

Under Regulation Best Interest, a broker, dealer or associated person making a recommendation of any securities transaction or investment strategy involving securities, including account recommendations, to a retail customer has to act in that customer’s best interest at the time the recommendation is made. The rule defines a retail customer in (b)(1) as a natural person, or their legal representative, who receives such a recommendation and uses it primarily for personal, family or household purposes. Nothing in that definition requires an existing account. A prospect on a first call qualifies.

Then look at how the Disclosure Obligation is worded in (a)(2)(i). Prior to or at the time of the recommendation, the firm or the associated person provides the retail customer, in writing, full and fair disclosure of the capacity in which they are acting, the material fees and costs that apply to the customer’s transactions, holdings and accounts, and the type and scope of services provided, including any material limitations on what may be recommended. Plus all material facts about conflicts of interest tied to the recommendation.

A phone call delivers no writing. That is the whole mechanism. If the rep recommends on the first call, the written disclosure arrives after the recommendation, which is backwards against a rule that says prior to or at the time of it.

The Care Obligation closes the other door. Under (a)(2)(ii)(B), the rep needs a reasonable basis to believe the recommendation is in the best interest of that particular retail customer based on that customer’s investment profile. The rule tells you what the profile includes in (b)(2): age, other investments, financial situation and needs, tax status, investment objectives, investment experience, time horizon, liquidity needs, risk tolerance and anything else the customer discloses. You do not have any of that ninety seconds into a first call.

So the first call is a fit check. Not because it is polite, and not because somebody’s blog said to build rapport. Because the disclosure cannot arrive in time and the profile does not exist yet.

One more provision speaks directly to how a calling floor gets run. The Conflict of Interest Obligation at (a)(2)(iii)(D) requires written policies and procedures reasonably designed to identify and eliminate any sales contests, sales quotas, bonuses and non-cash compensation based on the sales of specific securities or specific types of securities within a limited period of time. A spiff on one product for one week is the pattern that paragraph names. Pipeline targets and activity goals are a different animal; a product-specific push on a deadline is not.

Outbound Call Rules That Apply to Registered Investment Advisers

Advisers do not answer to FINRA Rule 2210. They answer to the Advisers Act marketing rule, and it arrives at the same hinge from the opposite direction.

The first prong of the advertisement definition in (e)(1)(i) covers any direct or indirect communication an adviser makes to more than one person, or to one or more persons if the communication includes hypothetical performance, that offers advisory services with regard to securities. Then it carves out three things, and the first is the interesting one: extemporaneous, live, oral communications.

The SEC explained the carve-out when it adopted the rule. A phone call or live video communication between an adviser and an investor could qualify for the exclusion. In the same discussion the Commission drew the boundary in one sentence: extemporaneous communications do not include prepared remarks or speeches, such as those delivered from scripts.

Same hinge as FINRA. Different rulebook, different words, identical pivot point.

The adopting release also says what happens next. A live oral communication that is not extemporaneous, but otherwise meets the advertisement definition, is an advertisement, and a record of it has to be kept under the advisers books and records rule at 204-2(a)(11)(i)(A). The Commission listed what that record can be: a copy of the prepared remarks, other written preparatory materials, or a recording of the oral communication.

Which means the script and the call recording are not two separate compliance chores. Either one can be the record.

Once a script makes the call an advertisement, the marketing rule’s seven general prohibitions govern what it may say. No untrue statement of material fact and no omission that makes a statement misleading. No material statement of fact the adviser lacks a reasonable basis for believing it can substantiate on demand by the Commission. Nothing that would likely cause an untrue or misleading implication. No discussion of potential benefits without fair and balanced treatment of the material risks and material limitations. No reference to specific investment advice unless it is presented fair and balanced. No performance results included, excluded or time-framed in a way that is not fair and balanced. And nothing otherwise materially misleading.

That second prohibition is the one to design around. Substantiate upon demand is an evidence standard, not a tone standard. If a line in the opener states a fact, somebody has to be able to produce the basis for it.

What to Check Before an Outbound Call as a Financial Advisor

Everything above decides what you may say. A separate set of rules decides whether you may dial at all, and it does not care that you are registered.

Long frosted glass tube with a rippled glass filter disc seated in a collar two thirds along, a line of small violet glass spheres passing through toward the right while one sphere is diverted out a side opening and rests apart, on a pale violet ground.

FINRA Rule 3230 is the telemarketing rule for member firms. It governs calling hours and the firm-specific do-not-call list, and the published analysis of how it interacts with federal telemarketing rules is worked through in detail in the financial advisor voicemail script breakdown, so this article will not repeat it. Federal telemarketing rules layer the national registry and the calling window on top; the TCPA rules for outbound calling cover that ground.

The operational failure is almost never the rule. It is the timing of the check.

A list scrubbed on Monday is stale by Thursday. A prospect who asked a rep to stop on Tuesday is still sitting in the Wednesday call queue if the request was logged in a note instead of a suppression field. That is not a legal subtlety. That is a workflow with the check in the wrong place, and the way to find it is to walk the path from list upload to dial and ask where the suppression lookup actually happens. Walking lists through a scrub before upload is covered in the guide to scrubbing calling lists.

Kixie puts that lookup in the dialing path rather than in a spreadsheet. National DNC compliance screens numbers against do-not-call data as part of Kixie’s business calling and texting, and PowerDialer advances the approved list so the rep is not choosing the next number by hand. The point is not that the feature exists. The point is where the decision sits: if the suppression check lives inside the dialing step, a rep cannot route around it by working from a personal export, and the manager can prove which list version a given call came from.

Run the pre-call list in this order and most of the trouble disappears:

  • Confirm the script version the rep is working from, and that a principal approved that version.
  • Confirm the suppression check runs at dial time, not at list-build time.
  • Confirm the local time at the called party’s number, not the rep’s.
  • Confirm whether the call will be recorded and whether the consent rule in the called party’s state has been satisfied.
  • Confirm the rep can state where the contact data came from, from the record rather than from memory.

How to Open an Outbound Call as a Financial Advisor

Knowing how to make outbound calls as a financial advisor without rewriting the opener every quarter means building the opener out of things that do not need approval again when the market moves. Identity does not change. A question does not change. A forecast changes constantly, which is exactly why it keeps failing review.

A workable shape:

  1. Identify. Your name, your firm, and the fact that this is a sales call. Say it in the first breath.
  2. Give the reason. One sentence on why this person and not a random number. Tie it to something you can point at in the record.
  3. Ask permission. A real question with a real no available.
  4. Ask one or two discovery questions. Open, factual, nothing that assumes you already know their situation.
  5. Propose one next step. An introductory meeting. Not a product.
  6. Document it. Outcome, what was asked, what was promised, and any contact restriction.

Written out, it sounds like this:

“Hi, this is [name] with [firm]. This is a sales call, and I will keep it to about a minute. We work with [specific group] in [area] on [the planning question you actually handle]. I do not know whether that is relevant to you, which is why I am calling. Do you have a minute for two questions, or should I try another time?”

Read that against the rules. It states capacity. It makes no recommendation, so Regulation Best Interest has nothing to attach to. It projects nothing, so 2210(d)(1)(F) is satisfied without an exception. It asserts no fact that needs substantiating on demand. And it gives the prospect a clean exit, which is the line most openers cut because it lowers the connect-to-conversation rate on paper.

It also has a version number, because every word of it is a script and the script is the artifact under review.

Outbound Call Objections a Financial Advisor Should Not Argue

Objection handling on an advisor call has a hazard that other industries do not share. Some of what sounds like an objection is a regulated event, and treating it as a sales problem converts a lost call into a rule problem.

“I already have an advisor.” Not an objection. A fact about their situation. Ask one question about what they are working on, accept the answer, and move. Arguing that their current advisor is doing it wrong is specific investment advice delivered with no profile behind it.

“I’m not interested.” Clarify once, gently, and listen to the shape of the answer. If what comes back is a request not to be called again, the conversation is over and the only remaining task is logging it in the suppression field. Do not run a rebuttal track against a do-not-call request. That is the single most expensive mistake on this list.

“Send me information.” Fine, but understand what you just agreed to. Whatever you send is its own communication and gets categorized the same way the script did, by audience, content and use. A one-off email to one prospect and a template mailed to two hundred are not the same object under Rule 2210.

“This isn’t a good time.” Ask for a specific time and honor the calling window at their location, not yours. Then actually call then. A missed callback is the cheapest trust you will ever throw away.

“How did you get my number?” Answer from the record. If the rep cannot say where the number came from, the problem is upstream in list governance, and the honest answer is to say you will check and to flag the record before anyone calls it again. Never improvise a source.

Financial Advisor Outbound Call Follow Up and Recordkeeping

Follow-up on an advisor desk is where the recordkeeping rules stop being abstract.

For member firms, 2210(b)(4)(A) wants a copy of the communication, the dates of first and last use, the approving principal’s name and approval date, and the source of any statistic or projection in it, retained per SEA Rule 17a-4(b). For advisers, the advisers books and records rule at 204-2(a)(11)(i)(A) wants a copy of each advertisement, and the Commission said that record can be the prepared remarks, the written preparatory materials, or a recording of the call.

That last option changes how to think about call recording. On most sales teams recording is coaching material. On an advisor desk it can double as the record of the communication itself. Check the consent rule in the called party’s state before you switch it on, because the states split on whether one party or all parties have to agree.

Voicemail follows the same logic. A voicemail left on a prospect’s phone is a communication, and a dropped voicemail is the same communication every time, which is an advantage: one message, one approval, one version. Voicemail Drop makes that consistency the default instead of hoping each rep repeats the approved wording. Text follow-up has its own retention rules, worked through in the financial advisor texting compliance breakdown.

The manager’s version of all this is four questions. Which script version ran on this call? Who approved it and when? Where is the copy? And if the prospect asked us to stop, which field holds that, and does the dialer read it?

Financial Advisor Outbound Call Metrics Worth Tracking

Dial count tells you the floor was busy. It does not tell you what to coach.

Break the result into the states a call actually passes through, and the coaching target appears on its own:

  • Attempts, live connections, and the gap between them by time of day.
  • Calls where the rep got permission to continue, as a share of live connections.
  • Qualified conversations, meaning a stated planning question the rep could name afterwards.
  • Introductory meetings scheduled, and separately, meetings actually held.
  • Outcome by list source and by approved script version.
  • Opt-outs and do-not-call requests, counted and routed to a suppression field.
  • Wrong numbers and data-quality failures, because those are a list problem wearing a rep problem’s clothes.

Script version is the one nobody tracks and the one the rules already make you keep. Put it on the dashboard next to connect rate and you can answer a question most desks cannot: did the new opener actually change anything, or did the list change underneath it?

Skip universal dial targets borrowed from another industry. Advisor list sizes, call windows and documentation load do not match a transactional sales floor, and a number that fits one does not fit the other.

Financial Advisor Outbound Call FAQs

Can a financial advisor make outbound calls to prospects?

Calling is a permitted prospecting channel for registered firms, subject to telemarketing rules on hours and do-not-call lists, your firm’s own procedures, and the communications rules covering whatever you say. The question is never whether calling is allowed. It is whether this number, at this hour, with this script, is allowed.

Does an outbound call script need principal approval?

Under FINRA Rule 2210(b)(1)(A), a retail communication needs an appropriately qualified registered principal’s approval before the earlier of its use or its filing with the Advertising Regulation Department. A script reaching more than 25 retail investors in a 30 calendar-day period is a retail communication under 2210(a)(5), which covers any script in regular use on a calling desk.

Does Regulation Best Interest apply to an outbound call?

It applies when the call carries a recommendation of a securities transaction or investment strategy to a retail customer, as Regulation Best Interest defines that term. A first call that asks questions and proposes a meeting carries no recommendation. The moment the rep suggests a specific product, account type or strategy, the Disclosure and Care Obligations attach, including the requirement that the disclosure be in writing prior to or at the time of the recommendation.

Are registered investment advisers covered by the same outbound call rules?

No. Advisers fall under the Advisers Act marketing rule, which excludes extemporaneous, live, oral communications from the advertisement definition. The SEC’s adopting release states that extemporaneous communications do not include prepared remarks or speeches, such as those delivered from scripts, so a scripted call that otherwise meets the definition is an advertisement and the firm keeps a record of it under the advisers books and records rule at 204-2(a)(11)(i)(A).

How long do you keep a financial advisor outbound call script?

Member firms retain retail and institutional communications for the period required by SEA Rule 17a-4(b), in a format and media that comply with that rule, and the record has to include the copy plus the dates of first and last use and the approving principal’s name and date, per FINRA Rule 2210(b)(4)(A). Correspondence is retained under the Rule 3110 supplementary material on correspondence retention and under Rule 4511.

Start with the script, not the tonality. Decide which rulebook it lands in, get the version approved before anyone dials it, put the suppression check inside the dialing step, and keep the copy where a reviewer can find it. Then go run the call block.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 14, 2026.

Can ChatGPT Agent Make Phone Calls? Not By Itself

TL;DR: Can ChatGPT agent make phone calls? No. ChatGPT agent has no phone line of its own, and nothing in the shipped product gives it one. OpenAI describes an agent as a model, plus tools, plus guardrails and human oversight, and a telephone is simply not one of the tools in that box. ChatGPT Voice is a microphone-and-speaker conversation inside the desktop app. On OpenAI’s always-on dot agent you can press a phone button to call it, while calls the agent starts on its own are still documented as planned for after launch. The thing that actually dials is GPT-Live over a SIP trunk you bring. You buy the number, you supply the provider endpoint, the digest username and password, and the caller number, then you POST to /v1/live/sessions with the destination written in full international format. OpenAI does not sell you a carrier. Ringing caps at three minutes, a connected call caps at two hours, and neither limit is configurable in the request. A 200 response means the session started, not that anybody answered. Then the law shows up. 47 CFR 64.1200(a)(1) bars initiating a call with an artificial or prerecorded voice to a cellular number absent an emergency purpose or the prior express consent of the called party, telemarketing needs prior express written consent under (a)(2), and the FCC has already determined that voice cloning and similar technologies qualify as an artificial voice. Inbound answering sits outside that prohibition, which is the single biggest planning lever in this article. Kixie has no native ChatGPT integration, so teams wire the two together with webhooks, the developer API, Zapier, Make or n8n. That split is the honest architecture: the agent decides, a rep talks.

So you asked ChatGPT agent to call a prospect and nothing happened. That is the expected result. The agent is not broken, you did not miss a toggle, and there is no permission buried in settings that turns this on.

Here is the short version. Can ChatGPT agent make phone calls? Not on its own. It has no number, no carrier, and no audio path to the telephone network, so the request fails at the first hop rather than somewhere clever. Every demo you have seen where an AI dialed a real phone had a telephony provider underneath it, and somebody was paying that provider by the minute.

Why does that matter beyond pedantry? Because it decides what you can build, what it costs to run, who is liable when a call goes wrong, and whether the thing is legal before you place the first dial.

Why ChatGPT agent cannot make phone calls by itself

Start with the definition OpenAI uses, because it explains the gap better than any feature list.

A frosted glass tray on a pale violet ground with four moulded recesses, three holding a glass lens disc, a cube and a standing ring, and the fourth recess left empty.

An agent is an AI system that can work through a task on your behalf, and OpenAI says agents bring together three elements: a model to interpret the task and plan next steps, tools to gather information or take action, and guardrails and human oversight to set boundaries. The model is excellent. The guardrails are real. The question is the middle element.

What tools does it actually have? Browsing, files, connected apps, code. Not a dial tone.

That is the entire answer, and everything below is consequence. An agent can only act through the tools it was given, so asking it to place a call is like asking it to print a document on a printer that was never connected. The intent is fine. The capability does not exist.

ChatGPT Voice is where most of the confusion starts. Why? Because it genuinely sounds like a phone call. It runs in the ChatGPT desktop app, it is powered by GPT-Live, and it lets you talk through ideas and coordinate tasks in Chat, Work, and Codex. You allow microphone access, you pick a voice, you talk. It supports natural turn-taking, so you can interrupt mid-response and steer the task without typing.

That is a conversation with your computer, which is useful on its own terms and completely unrelated to telephony, because nothing in it touches a phone network and the person you actually wanted to reach is not on the other end.

OpenAI’s dot agent gets closer to the thing people imagine, and the gap there is even more instructive. You can create, message, or call your dot in the ChatGPT mobile app, desktop app, or a desktop browser. To call it, you open its conversation and select the phone button. You talk through a request, clarify a decision, or ask for a progress update, and you can keep typing while you talk.

Read the direction carefully, because the entire question turns on it. You are calling it.

The documentation is explicit about the other direction: calls initiated by your dot are planned for after launch. That is OpenAI describing its own most autonomous consumer product, and outbound calling sits on the roadmap rather than in the build. Ending a call ends the voice conversation, though work you already assigned keeps running in the background.

So when a rep asks whether the agent can call a lead back while they finish lunch, the answer is no. Not yet, and not without a completely different stack underneath it.

The phone call is placed by a carrier you bring

Now the part that does work, because there is a real path from an OpenAI model to a ringing phone. So what is OpenAI actually selling you here? The model and the session, and nothing else. It is an API path rather than a chat path, and the difference in effort between those two is the whole story.

Two frosted glass platforms of different shapes on a pale violet ground joined by a single curved glass tube with four small spheres travelling inside it.

GPT-Live connects incoming and outgoing phone calls through a SIP trunk. Your provider exchanges call audio with OpenAI, while your backend handles session configuration, call controls, and business logic. SIP signaling uses TLS and GPT-Live requires SRTP for the call audio.

The load-bearing word in that paragraph is your. OpenAI does not hand you a phone number.

To place an outbound call you use a SIP trunking provider, such as Twilio, and you purchase a number from that provider first. Then you supply the trunk configuration on every single request: a provider endpoint that must use sips: for TLS signaling, digest authentication carrying your SIP username and password, a caller number and a destination number, both written in full international format with the country code. SIP URI destinations are not supported, so a clever routing shortcut is off the table. Your provider also has to support TLS signaling and SDES-SRTP media, and you enable SRTP in their settings before the first call goes out.

Then you send a POST to /v1/live/sessions with your session configuration and a transport type of sip.

What did you just agree to own? Count the list. A carrier contract. A number you pay for monthly. Credentials that have to stay under server-side control, which is exactly why the documentation tells you to keep your OpenAI API key and SIP credentials on your server rather than anywhere near a client. A backend that stays awake and listening. None of that is a prompt, and none of it is something a sales manager can configure on a Friday afternoon.

One detail catches experienced teams out. Outbound SIP calling is available through the Live API, not the Realtime API call-creation endpoint, so if you built against the older surface the method you are reaching for is not the one that dials.

What about calls coming the other way? Inbound runs as the mirror image, and it is meaningfully simpler. You point your provider’s SIP trunk at your project URI, OpenAI fires a live.transport.incoming webhook when a call arrives, and your backend decides whether to accept or reject it. The documentation also tells you to treat the SIP headers as untrusted caller metadata rather than authorization, which is sound practice in any inbound system and considerably more urgent when a language model is about to act on whatever it was told.

The call limits OpenAI bakes into every phone session

This is where a convincing demo and a production deployment separate, and the published numbers are specific enough to plan against.

Ringing is limited to three minutes. A connected call is limited to two hours. Neither limit is configurable in the creation request.

Is three minutes enough? For a single dial, easily. As a retry strategy it is useless, so your queue logic has to live in your code rather than in the session. Two hours is far longer than any qualification call will ever run. Design against both anyway, because a session nobody closed is still a session somebody pays for.

The response behavior is the part that burns people. When you create the session you get a 200 back once it initializes, and the documentation is blunt about what that does not mean: the call has not been answered. The response carries no SDP and no trunk credentials.

So what actually tells you a human picked up? Three events do, and you have to be listening for them. transport.ringing means the provider reports ringing or early media. transport.answered means the call was answered and media is established. transport.failed means setup failed after initialization, and you inspect the error code and message to find out why.

You read those over a sideband WebSocket that you attach to the session after creating it. Attach immediately. The sideband replays only the preceding three seconds of events before it starts streaming new ones, so a late attachment quietly misses earlier call progress and you end up debugging a call you have no record of starting.

So what should you actually trust? Not the status code. That is the full operational shape, and it is worth saying in one line. A dial attempt is not a result, a 200 is not a connection, and the only proof a conversation happened is an event you were already listening for.

Anyone selling you an agent that “just calls people” has skipped every requirement above and handed you the bill for them later.

What the law counts as an AI phone call

Suppose you build the whole thing and it works. Now ask the question that stops most of these projects before launch.

47 CFR 64.1200(a)(1) says no person or entity may initiate any telephone call using an automatic telephone dialing system or an artificial or prerecorded voice to the lines it lists, other than a call made for emergency purposes or made with the prior express consent of the called party. One of those lines, at (a)(1)(iii), is any telephone number assigned to a cellular telephone service, a paging service, a specialized mobile radio service, or any service for which the called party is charged for the call.

Does that reach your list? Almost certainly. It covers most of the numbers sitting in your CRM right now.

The bar rises when you are selling something. Under (a)(2), a call that includes or introduces an advertisement or constitutes telemarketing, placed with an artificial or prerecorded voice to those same lines, requires the prior express written consent of the called party rather than ordinary consent.

Can you argue your way around it? The obvious dodge is to claim a synthesized conversational voice is not an “artificial” one in the statutory sense. That argument is already closed. In its 2024 rulemaking on AI and robocalls, the FCC noted that the TCPA expressly covers artificial or prerecorded voice, and that the Commission has already determined that voice cloning and similar technologies qualify under that statutory phrase.

There is one asymmetry here that is worth designing your entire roadmap around. The same FCC document states that the TCPA’s prohibition on using an artificial or prerecorded voice message extends only to outbound calls that are made or initiated by the caller, and that the requirements do not extend to technologies used to answer inbound calls.

Read that twice. It is the most useful sentence in this article.

Why does the direction matter so much? Because an AI voice answering your main line is a fundamentally different legal object from the same voice dialing out of it. Same model, same vendor, same code, opposite exposure. So if you want AI voice in production this quarter and you would rather not stand up a written-consent program first, the inbound side is where the room is, and that is a planning decision rather than a technical one.

The Commission has also proposed requiring callers who use AI-generated voice to disclose at the beginning of each call that the call uses the technology. Proposed is doing real work in that sentence, so treat it as a direction of travel rather than a rule you can cite today, and have counsel review anything you intend to dial.

Where an agent belongs in a sales call workflow

Strip the hype out and a clean division of labor appears, which is usually what happens once you know exactly what a tool can and cannot reach.

So where does the agent actually earn money? Not on the call. It is genuinely good at the work around it. It reads the account, assembles context, drafts the opener, pulls the last three touches, and writes the follow-up while the rep is still saying goodbye. It never gets tired at dial ninety and it never skips the notes because the next call is already ringing.

It is bad at the call itself. Not technically bad, though latency and interruption handling are real problems. Bad commercially.

Why? Because a prospect who changes tone at minute two needs somebody who can hear it and throw the plan away, and that is the precise moment a scripted system keeps going. Sticking to the script after the buyer has moved is a named failure mode in human reps too. It is simply guaranteed in a system that has no other option.

The practitioner read on tooling is old and still correct. A tool earns its place when it changes what the rep no longer does by hand, when the outcome lands in the system of record automatically, and when a manager can inspect what happened afterward. An agent that drafts follow-up and logs context clears all three of those. An agent that holds the conversation clears none of them and adds a compliance surface you now own.

So model it as a queue rather than a replacement. The lead arrives, the agent enriches and prioritizes it, a rep dials, the outcome is logged against the record, and the agent handles the admin on the back end so the rep is already on the next call. Dead time disappears. Judgment stays with a person.

Here is the diagnostic question to put to any AI calling pitch, and it works on vendors and internal builds alike. When the buyer says something the script did not anticipate, what happens in the next four seconds? If the answer is a warm transfer to a human, you have bought a routing layer with extra steps and a monthly carrier bill. If the answer is that the agent keeps talking, you have bought a liability with a pleasant voice.

Connecting ChatGPT to Kixie calls without a native integration

Worth stating plainly, because it sets expectations correctly and saves a procurement conversation: Kixie does not have a native ChatGPT integration. Teams connect the two with custom builds on the Kixie API and webhooks, or through Zapier, Make or n8n.

That is not a gap to apologize for. It is exactly the architecture the previous section argued for.

Which direction does the data move? Both, and each direction does different work. Kixie webhooks post completed calls, outcomes, recordings, and texts to your automation layer, which is where a ChatGPT workflow picks them up, so the model reasons over what actually happened on the line instead of what a rep remembered to type an hour later. Going the other way, an event in that workflow can trigger a Kixie call or text through the same automation layer rather than a native endpoint, because the Kixie developer API has no direct auto-call endpoint and those recipes are brokered through Zapier. New records can also be pushed into a PowerList or Cadence so reps can start dialing them immediately.

Notice who dials in that sentence. Reps do.

The developer API and webhooks are included on all plans, which matters because this pattern depends on them rather than on a premium tier. Start Call, Answered Call, End Call, Disposition, and Call Outcome are the events your automation listens to, and they are enough to drive a full post-call workflow. Keep the API key server-side, the same discipline OpenAI asks for with SIP credentials.

On the dialing side, the Multi-Line PowerDialer addresses the volume problem that made people want an AI caller in the first place, while keeping a human voice on every connection. Conversation Intelligence then gives the model something real to summarize. One caution that is easy to get backwards: Voicemail Drop messages are recorded by a rep, and a synthetic voice does not belong in that slot.

If you want the broader version of this question beyond the agent product specifically, we covered whether ChatGPT can make phone calls and why your carrier still does the dialing.

What to check before you let an agent make phone calls

Run this list before anyone writes code. It is short on purpose, and most projects die on the first item.

First, name the carrier. If nobody on the project can say which provider holds the trunk and who pays that invoice every month, there is no calling system yet, there is a diagram.

Second, write down the one task. What single job is this for? Appointment confirmation, a reminder, a callback collection, an inbound routing decision. One of them. Open-ended selling is not a first deployment and probably is not a second one.

Third, settle the direction before anything else gets built, because inbound answering and outbound dialing carry genuinely different obligations under 64.1200. Pick one, get it reviewed, then build.

Fourth, decide what the agent is allowed to read. How much of the CRM does this job actually need? A model with your entire CRM in scope will eventually say something from it out loud to the wrong person.

Fifth, define the stop condition. Which sentence from the buyer ends the automation and hands the call to a person, and how many seconds does that handoff take?

Sixth, test the ugly cases rather than the demo path. Voicemail, dead silence, an interruption at four seconds, a disconnect mid-sentence, a wrong number, an accent the model handles poorly, and a connected system that times out while the buyer waits.

Seventh, check what gets logged. Where does the outcome land? If the call does not land in your system of record with an outcome attached, your manager cannot coach it and your compliance team cannot evidence it, which means it may as well not have happened.

Who owns the result when it goes wrong? You do. One more thing sits underneath all seven. OpenAI’s own guidance says an agent does not share a colleague’s responsibility for the outcome, and that you remain responsible for deciding whether the work is ready to use. On a phone call, that decision gets made in real time by whoever is on the line.

Track the carrier, the task, the direction, the data scope, the stop condition, and the log. Now there is something to review.

ChatGPT agent phone call FAQs

Can ChatGPT agent make phone calls to a real phone number?

Not by itself. The consumer product has no telephony tool at all. Placing a real call requires GPT-Live connected to a SIP trunk from a provider you contract with separately, plus a backend that creates the session and monitors it.

Is ChatGPT Voice the same as a phone call?

No. ChatGPT Voice runs in the ChatGPT desktop app through your microphone and speakers, and it never touches the telephone network. It is a conversation with the model, not with your prospect.

Can an AI agent receive phone calls instead?

Yes, and this is the easier side in every sense. You route your provider’s SIP trunk to your OpenAI project, your backend accepts the incoming call webhook, and the model handles the conversation. The FCC has stated the artificial-voice prohibition does not extend to technologies used to answer inbound calls, which is a large part of why inbound deployments move faster.

What does it actually cost to let an agent call prospects?

It costs more than the model, and the forgotten line items are the expensive ones. You pay for the API, the SIP provider, the phone numbers, and the engineering time to build and monitor the backend that holds it together. Budget the carrier relationship as a permanent line item rather than a one-time setup cost.

Do I need consent before an AI voice calls a cell phone?

Under 64.1200(a)(1), an artificial or prerecorded voice call to a cellular number needs the prior express consent of the called party absent an emergency purpose, and under (a)(2) telemarketing with that voice needs prior express written consent. The FCC has determined that voice cloning and similar technologies fall under the statutory phrase. Get legal review before you dial.

Should sales teams let an agent run calls alone?

No, not for selling. Use the agent for research, prioritization, drafting, and after-call admin, and keep a rep on the conversation itself. The moment a buyer goes off-script is the moment the deal is won or lost, and that moment needs a person.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 15, 2026.