A TCPA-compliant script builds the required disclosures into the words agents actually say. It identifies the caller and the company within the first few seconds, states that the purpose of the call is to sell, uses fixed wording to capture consent, and gives agents an exact path to stop the call when someone asks not to be contacted again.
In This Article
What follows is the compliance layer of a script, in the order an operations lead meets it when auditing a live campaign.
Script review also sits inside our TCPA compliance consulting engagements, alongside campaign audits, DNC scrubbing setup, consent documentation and agent training.
What makes a telemarketing script TCPA-compliant?
A script is compliant when the required disclosures are written into the words agents say, early enough in the call to count as prompt, and when the opt-out path leaves agents nothing to improvise.
The script is the only part of a live conversation you control in advance. Who answers, how they react and where the conversation turns are improvised. The opening, the consent wording and the opt-out path are not. That is where the exposure sits.
Compliance failures are rarely decisions. They are drift: an opener shortened for pace, a rebuttal someone added because it worked, an opt-out line an agent improvised once and kept. The script is where drift becomes visible, and the cheapest place to correct it. It is also the first artifact a regulator or a plaintiff’s lawyer asks to see, alongside the recordings that show whether anyone followed it.
Two rulebooks apply at once, written by two agencies. The FCC’s rules implementing the TCPA sit at 47 CFR 64.1200 and govern consent, do-not-call handling and calling hours. The FTC’s Telemarketing Sales Rule sits at 16 CFR Part 310 and governs what must be disclosed on a sales call and what an agent may not do when someone objects. A script can satisfy one and breach the other. That is why a script reviewed once still fails an audit.
Not every outbound call is a telephone solicitation
Check which rules the campaign is under before auditing any wording. The FCC defines a telephone solicitation as a call encouraging the purchase, rental or investment in property, goods or services.
A call that does none of those is not a solicitation, which changes how the national do-not-call registry rules apply. That split runs straight through a book of campaigns.
Appointment setting, lead generation and lead qualification calls are selling, even when the ask is only a meeting. The full disclosure set applies. Market research and customer insight surveys do not encourage a purchase, so they carry a lighter set of obligations, right up to the point a survey steers toward an offer: at that point it is a sales call with a survey on the front. Outsourced programs running several of these at once document the distinction per campaign, not per client.
What has to be said in the first fifteen seconds of an outbound call?
Four things on a sales call, and three of them every time: who the seller is, that the purpose of the call is to sell, and what is being sold.
The fourth applies only to prize promotions. The Telemarketing Sales Rule requires all of them truthfully, promptly, and in a clear and conspicuous manner.
The FCC adds a requirement the TSR does not. Under its identification rule at 64.1200(d)(4), a telemarketing call must give the called party the name of the individual caller, the name of the entity on whose behalf the call is made, and a telephone number or address for that entity. Scripts written from the TSR alone miss the agent’s own name. It is a one-word fix that goes unmade because nobody reads both rulebooks side by side.
Neither rule defines promptly in seconds. The working standard is before the pitch starts. A sales team writes the opener differently: a warm greeting, a rapport question, a short qualifying question, and the disclosure landing forty seconds in, after the prospect has already been asked to engage. Read aloud, it sounds natural. On a QA scorecard it is a gap.
Fix it structurally, not with training. Score the first fifteen seconds as its own QA item, make the disclosure a required field that cannot be marked complete by inference, and route any edit to the opening back through script approval rather than treating it as a wording tweak a team lead can make.
Teams without an approval loop build one first. That is the script review workstream, and it sits alongside campaign audits, consent documentation, DNC scrubbing, call recording compliance and agent training.
What the opening carries | FTC Telemarketing Sales Rule 16 CFR 310.4(d) | FCC TCPA rules 47 CFR 64.1200(d)(4) |
|---|---|---|
Identity of the seller | Required | Required, as the entity on whose behalf the call is made |
Name of the individual caller | Not required | Required |
That the purpose is to sell | Required | Not required by this rule |
Nature of the goods or services | Required | Not required by this rule |
A contact number or address | Not required | Required |
Prize promotion disclosure | Required where a prize promotion is offered | Not required by this rule |
Timing standard | Promptly, clearly and conspicuously | The rule sets no timing |
How should a script capture consent, and what wording holds up?
For most outbound campaigns the script captures no consent at all. Prior express written consent is collected before the call, in a signed written agreement, and the script relies on it.
Confusing the two is a recurring structural error in script review: wording that reads as though the agent is obtaining consent on the call when the legal basis is a form somebody signed six months earlier.
The FCC’s definition is specific. The written agreement carries a signature, clear authorisation for the seller to deliver telemarketing calls using an automatic telephone dialing system or an artificial or prerecorded voice, the telephone number being authorised, and a clear and conspicuous disclosure that signing is not a condition of buying anything. If your consent records lack any of those, no script wording rescues them.
State this one plainly, because published guidance still gets it wrong: the FCC’s one-to-one consent rule never took effect. The Eleventh Circuit vacated it in January 2025, holding the Commission had exceeded its statutory authority, and the FCC deleted the vacated language and reinstated the previous standard in August 2025. Scripts and consent forms rewritten in anticipation of it revert. Guidance published in 2026 describing one-to-one consent as arriving describes a rule that does not exist.
A script does capture consent in one narrower case: a verbal opt-in taken on the call for text follow-up. That is the one place word-for-word delivery matters, because the wording is the record. The tightest implementation we have run required agents to read the consent disclaimer verbatim, scored any deviation as an automatic fail rather than a coaching note, and logged opt-in and opt-out status on every contact record.
What should an agent say when someone asks to be taken off the list?
Confirm, log, end. The script gives agents one short line and no room to improvise, because the failure mode here is an agent trying in good faith to keep the conversation alive.
Most of the ways this goes wrong start with a few extra seconds nobody authorised.
The Telemarketing Sales Rule is unusually specific here, and it prohibits several things that look like ordinary sales behaviour. It is a violation to require someone to listen to a sales pitch before their request is accepted, to hang up on them, to require them to call a different number, to charge for honouring it, or to require them to identify the seller before it counts. Each has a script equivalent. “Before I do that, can I just tell you why I called” is the first. “You’ll want to call our 800 number for that” is the third. Both appear in scripts that have been through review.
On the FCC side, consent is revocable by any reasonable method, and the rule names words that are automatically sufficient: stop, quit, end, revoke, opt out, cancel, unsubscribe. Agents do not judge whether a phrasing was clear enough. Once made, the request is recorded at the time it is made, honoured within a reasonable time that cannot exceed ten business days, and kept for five years. Callers also cannot currently designate one exclusive channel for revocation, so a script cannot route people to a single method and treat everything else as invalid.
One more line belongs in the script and rarely is. Companies making telemarketing calls maintain a written do-not-call policy available on demand, so an agent needs something to say when a caller asks to be sent it. Without a line, they invent one.
See how your current script scores
Four checks in, you know what to look for. The compliance audit quiz asks four questions covering TCPA, TSR and state rules, takes under a minute, and sends the score and recommendations by email.
Where state law changes the words on the page
Federal compliance is the floor. More than a dozen states run their own telemarketing statutes, and the ones modelled on Florida’s go further than federal law on consent, call frequency and calling hours.
Some prescribe the disclosure wording closely enough that it stops being a training matter and becomes a script approval matter: the words are set, and the only question is whether your page carries them.
Calling hours show the problem most clearly. Federal rules put outbound calls between 8 a.m. and 9 p.m. local time at the called party’s location, and the FCC and FTC rules agree. Several mini-TCPA states cut the evening end shorter and cap how many times you may call about the same subject in a day. A dialer configured to the federal window is compliant everywhere and non-compliant in several states at once.
Recording changes the opening too. In states requiring all-party consent, the recording notice belongs in the opening rather than appended at the end, so a single national script either carries the notice everywhere or splits by state.
Running one script across several regulatory environments is normal work. Our insurance programmes have run simultaneously across California, Connecticut, Maryland and Ohio, with the Ohio campaign alone passing 40,000 dials, and the script variants are maintained per state rather than reconciled into one.
A compliant opening, line by line
Below is a skeleton opening for an outbound B2B sales call with no prize promotion and no recording notice required. It is not a script: it is the compliance layer a script gets built on.
The persuasive work is left to you.
Sample opening structure
Opening
Four things do the work there. The seller is named before anything is asked. The selling purpose is stated, not implied. The identification answer carries all three items the FCC requires. And the opt-out response contains no rebuttal, no redirect to another number, and no request that the person identify who they want to stop hearing from, because each of those is independently prohibited.
How often should you re-review a telemarketing script?
Twice a year is the baseline, with an immediate review triggered by a federal rule change, a new state entering the footprint, a new offer, a new channel, or agents drifting off the page.
That last trigger is the most useful and the easiest to skip. Repeated drift in one spot means the script is hard to say, not that agents are careless.
Hold any script review open right now rather than closing it. On 9 September 2026 the FCC released a draft Report and Order and Further Notice of Proposed Rulemaking that would rework the consent revocation framework, including allowing callers to designate an exclusive revocation method provided that method is clearly and conspicuously disclosed on the call itself. If adopted, that disclosure lands in the script. The draft was scheduled for consideration at the Commission’s open meeting on 30 September 2026, with final rule changes taking effect thirty days after Federal Register publication.
A script that has been through this once is not finished. It is current. Script review belongs inside an ongoing compliance programme rather than a project with an end date.
Frequently asked questions
What has to be included in a TCPA-compliant telemarketing script?
What should an agent say when someone asks to be put on the do-not-call list?
Confirm the request, tell the caller they are being added, and end the call. The agent must not deliver a rebuttal first, redirect the person to a different number, or ask them to identify which seller they want to stop hearing from. Each of those is separately prohibited by the Telemarketing Sales Rule. The request is recorded when it is made and honoured within ten business days at the outside.
Does a telemarketing script have to change from state to state?
Is the FCC one-to-one consent rule still coming?
No. The Eleventh Circuit vacated it in January 2025 on the basis that the FCC had exceeded its statutory authority, and the FCC removed the vacated language and reinstated the prior definition of prior express written consent in August 2025. Consent forms and scripts rewritten in anticipation of the rule can revert to the earlier standard. Guidance published since that describes the rule as pending is wrong.
How often should telemarketing scripts be reviewed for compliance?
Twice a year is the baseline, with an immediate review triggered by any federal rule change, a new state in the calling footprint, a new offer, a new outreach channel, or a QA pattern showing agents deviating at the same point. Regulations in this area change often enough that an annual cycle leaves scripts out of date.
Model it against your own volumes
The outreach compliance risk calculator takes a monthly call volume and an estimated non-compliance rate, and returns the statutory exposure under the TCPA and the TSR side by side.
