TCPA basics for outbound teams: questions to resolve before calling
Published · Updated
Ryan Erkal
Founder, Redialler
TCPA basics for outbound calls start with classification. Before a team dials, identify the recipient, purpose, caller technology, number type, consent record, do-not-call status and local time. The federal overview below is operational education for questions to take to qualified counsel. It is not a complete compliance program, a legal opinion or permission to call.
Start with scope: federal overview, not a full program
The Telephone Consumer Protection Act, or TCPA, is a federal statute with FCC implementing rules. The FTC's Telemarketing Sales Rule, or TSR, adds requirements for covered telemarketing, and states can impose stricter rules. A team can therefore satisfy one narrow federal test and still fail a state, contract, recording or platform requirement.
Write down the call purpose, recipient relationship, number type, technology, seller, caller and state before deciding what applies. Keep the decision with the campaign record. A policy that says all B2B calls are exempt or all calls are robocalls is too broad to guide a real queue.
The FCC's current rules and the FTC's current business guidance should be the starting points for counsel review. Recheck them when the recipient, script, voice technology, vendor or jurisdiction changes.
Separate live manual calls, ATDS questions and artificial voice
A live manual call is a rep choosing a number and speaking to the recipient. It can still raise do-not-call, caller-ID, calling-time, recording and state-law questions. Manual does not mean automatically lawful.
An automatic telephone dialing system, or ATDS, is a defined term in the FCC rules. The current rule describes equipment with the capacity to store or produce telephone numbers to be called using a random or sequential number generator and to dial those numbers. Whether a particular platform, workflow or configuration meets that definition is a legal and technical question. Preserve the vendor's architecture and settings for counsel rather than guessing from a feature name.
An artificial or prerecorded voice is a separate trigger. In its 2024 AI Declaratory Ruling, the FCC confirmed that the TCPA restrictions cover current AI technologies that generate human voices. The ruling says such outbound calls to consumers require prior express consent absent an applicable emergency purpose or exemption, and the rules include identification and opt-out requirements. A human rep who uses a normal live conversation is not the same call type as a prerecorded or AI voice message.
Determine consent by call type, purpose and recipient
Consent is not one field that applies to every campaign. Ask what the recipient agreed to receive, from which seller, at which number, by which method and for which purpose. Keep the source, wording, timestamp and version with the record. A form that says a person may be contacted is not automatically the prior express written consent required for every artificial or prerecorded telemarketing call.
The FCC rule defines prior express written consent as a signed agreement that clearly authorises the seller to deliver advertisements or telemarketing messages using an ATDS or artificial or prerecorded voice to the specified telephone number. The rule also contains disclosures and other conditions. Counsel should map the actual form, seller and call method to that text.
Do not revive the vacated one-to-one consent rule as if it were current federal law. A 2025 FCC and Department of Justice filing states that the Eleventh Circuit vacated that rule and that the government would not seek further review. That court development does not create a blanket permission for automated or artificial-voice calls, and it does not answer state-law or entity-specific questions.
Check national and entity-specific DNC and local time
Separate the National Do Not Call Registry from an entity-specific do-not-call list. The national registry is a federal screening source with scope and exemptions. An entity-specific request is the recipient telling your business to stop. A person can be outside the national registry and still require your business to suppress the number.
The FTC's safe-harbor guidance calls for written do-not-call procedures, trained personnel, a recorded entity-specific list, a process that prevents calls to listed numbers and a recent National Registry download no more than 31 days before a covered call. It also calls for monitoring and enforcement. Keep evidence of the version used and the screening result.
For covered consumer telemarketing, the TSR generally limits calls to 8 a.m. through 9 p.m. local time at the location called unless prior consent permits another time. The FCC rule, state statutes and industry rules can add requirements. Resolve the prospect's timezone instead of using the rep's clock, and treat an unknown timezone as a counsel or operations decision.
Handle revocation and suppression across teams
Capture a request to stop in the channel where it arrives, then copy it into one durable suppression process used by every list, rep, retry and vendor. Record the number, matched person, exact words or action, timestamp, actor, source and scope. A rep's note that says do not call is not enough if the queue and provider cannot read it before the next attempt.
The FCC's January 2026 DA 26-12 Order extends the effective date of one narrow part of section 64.1200(a)(10) until 31 January 2027. The extension concerns applying a revocation made in response to one type of informational message to all future robocalls and robotexts on unrelated matters. The Order says it does not alter the status quo for other revocation rules. Treat this as a limited effective-date caveat, not a general revocation delay.
The safe operating choice is to suppress the requested number and pause related outreach while counsel determines whether a narrower scope is required. Do not assume that an entity-specific request disappears because a consent category or business unit differs. Test a retry, import, ownership transfer and parallel leg after the suppression is saved.
Keep evidence, audit settings and obtain state review
Use this decision checklist for a live B2B call. Identify whether the number is a business line, a personal mobile used for work or an unknown destination. Record the live or automated method, seller, purpose, caller ID, consent source, national and entity-specific DNC results, local time and state. Then ask counsel to classify the call. The checklist does not declare the call lawful.
Use a different checklist for an artificial-voice marketing call. Confirm the consent wording and number, script and disclosures, opt-out mechanism, DNC screening, calling time, recording rule, vendor contract, state requirements and retention owner. Preserve the configuration and a test result before a campaign starts. The FCC AI ruling makes the voice classification material even when the generated voice sounds human.
Redialler can enforce durable phone suppression, number checks and configured calling-window controls before a call reaches the carrier. State-specific policy still belongs to the team. Technology can enforce a decision that counsel has defined; it cannot make that decision for the team. For the workflow controls around first-answer calling, see Parallel dialing explained. To review a real campaign, discuss your calling workflow.
Explore Redialler
Sources and review
Reviewed 2026-09-08. Product details and provider policies can change.
- Complying with the Telemarketing Sales Rule (checked 2026-09-08)
- 47 CFR 64.1200 Delivery restrictions (checked 2026-09-08)
- FCC Declaratory Ruling on AI-generated voices (checked 2026-09-08)
- FCC DA 26-12 Order on limited revocation effective date (checked 2026-09-08)
- FCC and DOJ filing confirming one-to-one rule vacatur (checked 2026-09-08)