Last updated 2026-07-11
TL;DR
TCPA requires prior express written consent before you autodial or robocall a cell phone. That consent has to be informed. The person must actually understand what they agreed to. If your lead form was in English and your prospect speaks Mandarin or Spanish, a court or the FCC can void the consent. You need language-matched disclosures, translated recordings, and records you can produce fast.
What does TCPA actually require for outbound call consent?
The Telephone Consumer Protection Act, 47 U.S.C. § 227, bars any call made with an automatic telephone dialing system (ATDS) or a prerecorded voice to a wireless number unless you have prior express written consent. [1] The statute dates to 1991. The FCC tightened the consent definition sharply in its 2012 rulemaking, which took effect in October 2013. [2]
The regulation that does the work, 47 CFR § 64.1200(a), says the consumer must sign a written agreement "that clearly and conspicuously authorizes" the calls and describes "the telemarketing goods or services." [12] The word "clearly" carries the whole thing. A disclosure buried in a Terms of Service page, set in 8-point font, or written in a language the consumer cannot read does not clear that bar.
Live-agent calls to residential lines placed by predictive dialers get treated as ATDS calls by most courts and the FCC, so they need the same prior express written consent for telemarketing. Purely informational calls with no commercial pitch need only prior express consent, oral or written, but you still need some affirmative yes.
If you are cold calling landlines, the consent standard drops. The National DNC rules still apply, in every language. More on that below.
Does TCPA or FCC guidance specifically address non-English speakers?
No federal rule says the words "translate your consent form." 47 U.S.C. § 227 never uses the word "language." [1] That silence protects nobody. The FCC's requirement that consent be "clear and conspicuous" has been read by courts to mean a reasonable person in the consumer's shoes actually understood what they agreed to.
The FCC's 2012 Report and Order (CG Docket No. 02-278, released February 15, 2012) put weight on consumers making an informed choice. [2] If a reasonable Spanish speaker cannot read your English-only disclosure, the "informed" part collapses.
State consumer protection law adds a second layer. California's CCPA and its regulations require certain notices in a consumer's preferred language when you have reason to know that preference. The California Department of Financial Protection and Innovation has issued guidance requiring financial services disclosures in languages other than English when the marketing itself ran in that language. [3] New York and several other states have laws requiring contracts and consumer-facing documents in languages common to certain service areas. [4]
The Federal Trade Commission's Telemarketing Sales Rule (16 CFR Part 310) bars deceptive telemarketing, and a consent form written in a language the consumer cannot read is a deceptive omission in practice. [5]
So here is the honest read. There is no bright-line federal command to translate. But stack the TCPA's "clear and conspicuous" test, state language-access laws, and FTC deception doctrine, and you get real liability if you skip translation.
What makes consent invalid when a campaign operates in multiple languages?
Consent breaks in multilingual campaigns three ways.
First, the consent form and the marketing channel speak different languages. Your Spanish-language Facebook ad sends traffic to an English-only consent page. The consumer clicked expecting Spanish, hit a language they may not read, and checked a box anyway. That is not informed consent. Courts have voided consent over smaller procedural slips than that.
Second, translated disclosures that read fine but miss required elements. A word-for-word Mandarin rendering of an English TCPA disclosure can still fail if the translator dropped the autodialer line to save space, or used casual phrasing that waters down "you may receive automated calls." Every translated consent form needs legal review, not only linguistic review.
Third, consent from a third-party lead generator whose form used a different language than your campaign. Buy leads from an aggregator whose opt-in ran in English, then call Vietnamese-speaking consumers, and the consent problem is yours. The FCC's one-to-one consent rule, released in December 2023 and set to take effect in early 2025, required consent to name your specific company rather than a generic partner list. [6] That rule was later vacated by the Eleventh Circuit in January 2025, but the underlying "clear and conspicuous" standard survives, and several state mini-TCPA laws still push toward company-specific, language-matched consent. Treat one-to-one, language-appropriate consent as the safe default.
The litigation risk is not theoretical. TCPA class settlements routinely run into the millions. The Cash App TCPA class action settlement and the Credit One TCPA settlement show courts do not shrug these off as technicalities.
How should you structure consent forms for non-English campaigns?
The consent form, whether it is digital, paper, or IVR, has to be in the language your consumer used to reach it. That means a real version for each language your campaign touches. Not a footnote at the bottom of an English form reading "Para español, llame al...".
Each language version needs, at minimum:
1. Your company's name (and any DBA you use on the phone). 2. The phone number or short code you will call or text from. 3. A plain statement that calls or texts may use an autodialer or prerecorded message. 4. A statement that consent is not a condition of purchase. 5. A description of the goods or services the calls will cover. 6. Instructions for revoking consent.
That last one gets underestimated. The FCC's 2024 revocation rules confirmed consumers can revoke consent by any reasonable means, including replying STOP, calling your main line, or mailing a letter. [6] Your translated form has to spell out that right in the consumer's own language. If a Haitian Creole speaker never learns they can opt out, your low opt-out rate is hiding a problem, not proving compliance.
For IVR consent (an automated call asking the consumer to press 1 to confirm), the recorded prompt has to be in the language the consumer expects. An English prompt played to a Vietnamese-only speaker captures nothing valid. Record and store a separate IVR file per language.
Recordkeeping detail that saves cases: store the exact language version of the consent form next to the timestamp, IP address for web forms, and session metadata. When a demand letter lands, that record is often the only thing between you and a check.
What are the rules for prerecorded messages in non-English campaigns?
47 U.S.C. § 227(b)(1) governs prerecorded messages. A robocall has to identify who is calling and offer an interactive opt-out during or right after the message. [1] The FCC's 2012 order said that opt-out mechanism must work throughout the call. [2]
Language does not change the rule. It changes whether you break it. An English opt-out prompt at the end of a Spanish robocall is a failure waiting to happen. The consumer never registers that they were told how to stop. They hang up, get called again, and turn up as a named plaintiff.
The recording has to be in the consumer's language. The opt-out prompt ("press 2 to stop receiving calls") has to be in the consumer's language. The company identification should be in the consumer's language, or at least clear enough that a non-English speaker can write it down and look it up.
In practice, you keep a separate audio library for every language. Version-control the files. When legal updates the opt-out wording, update every language version and log the change date. This is dull work. It is also exactly what a plaintiff's attorney asks for in discovery.
One more thing. Prerecorded calls to numbers on the do not call list are not saved by consent in any language. DNC rules sit on top of consent rules, not in place of them.
How do you screen multilingual campaigns against the DNC registry?
The National Do Not Call Registry does not care what language you call in. A residential number on the registry is off-limits for telemarketing, full stop. [7] You scrub before you call, and you re-scrub at least every 31 days if the campaign runs past a month. [7]
You can get the do not call list through the FTC's Telemarketer Registration system. Access costs $75 per area code per year, capped at $19,725 for all area codes nationally (2024 pricing from donotcall.gov). [8] That price does not move with the language of your campaign.
Here is the trap. DNC scrubbing does not stand in for consent. You need both. A number that is not on the registry, and valid consent. Plenty of teams treat DNC and TCPA consent as one thing. They are separate. A consumer who opted in on a Spanish-language form and later registered on the DNC has effectively revoked consent for telemarketing. The FTC's rule is plain that even an established business relationship does not override a DNC registration for general telemarketing. [5]
If you target mobile numbers, the mobile phone do not call list question comes up a lot. Mobile numbers have been registerable on the national DNC since 2003, and the TCPA wireless rules (consent required for ATDS calls whatever the DNC status) make cell phone compliance stricter than landline compliance, not looser.
How do you document and store multilingual consent records?
Documentation is where multilingual campaigns fall apart most often. Here is a structure that holds up in litigation.
For each opt-in, capture and store the exact version of the consent form (put a hash or version number in the database field), the language of that form, the timestamp in UTC, the consumer's phone number, the IP address for web forms, the session ID or confirmation number, and the campaign or ad source that drove the opt-in.
Store it somewhere tamper-evident. A spreadsheet edited on Google Drive is not tamper-evident. A database with write-once records, or an audit log that timestamps every change, is. You do not need enterprise software for this. A simple insert-only table plus a separate audit log table is defensible.
For translated forms, keep the source English version alongside each translation and the date of each translation. If a plaintiff argues your Tagalog form was inaccurate, you want to hand the court the English original, the translator's credentials, and the date of any updates.
Retention: the FTC's Telemarketing Sales Rule requires you to keep records for 24 months. [5] Some state laws demand longer. California's CCPA enforcement has targeted companies that could not produce records more than companies with bad consent. Keep records at least four years to cover the TCPA's four-year federal statute of limitations under 28 U.S.C. § 1658, and five is safer once overlapping state claims enter the picture.
LeadCompliant's free compliance kit includes a consent record template with fields for language version tracking, if you want a head start instead of building it from scratch.
What should your callers say in non-English languages to stay compliant?
If your agents make live calls, they need a script, and that script has to exist in every language they use. The FTC's Telemarketing Sales Rule requires prompt identification of the seller and the purpose of the call. [5] An agent who switches from Spanish to English to deliver the required disclosures has missed the point of that rule.
A compliant live-agent opening in any language covers the agent's name, your company's name, the fact that this is a sales or marketing call, and, for recorded or autodialed calls, how to opt out. For cold calls to consumers who never opted in, agents must honor any do-not-call request immediately and log it to your internal DNC list within 30 days. [5]
Internal DNC lists matter enormously in multilingual campaigns. If a Spanish-speaking consumer says "no me llames," that is a do-not-call request. Honor it. Your system cannot demand the consumer say "remove me from your list" in English first. Train agents to recognize opt-out requests in every language your campaign runs, and log them on the spot.
Audio training clips per language earn their cost fast. A five-language call center with English-only training materials produces agents who miss non-English opt-outs. That is a straight line to do not call telemarketer list enforcement and individual lawsuits.
How do state laws change the consent rules for multilingual campaigns?
State law is the wild card, and it is genuinely messy. Florida, Washington, and Oklahoma run mini-TCPA statutes with their own consent requirements. Some are stricter than federal TCPA, and they do not all defer to FCC interpretations. [9]
California is the most aggressive. The California Invasion of Privacy Act (CIPA, Penal Code § 632) requires all-party consent for recorded calls. Record a call with a Spanish-speaking California consumer without disclosing the recording in Spanish, and you face CIPA liability stacked on top of TCPA exposure. [10] California courts have certified CIPA class actions, and the statutory damages of $5,000 per violation pile up fast.
New York Executive Law § 296-a and related regulations require certain businesses to provide services and consumer-facing documents in languages a real share of their customers use. It aims mainly at financial services and housing, but the theory has crossed into litigation in other sectors. [4]
Illinois's Telephone Solicitations Act has its own registration and disclosure rules. Texas's Business and Commerce Code Chapter 305 adds state telemarketing rules. None of these statutes flatly demand translated consent forms, but all of them use "clear disclosure" or similar wording that courts have applied to language-access questions.
The practical line I draw: if more than 10 to 15 percent of your leads in a state come from a non-English-speaking population, talk to a licensed attorney in that state before you launch. That is not legal advice from this article. It is the honest observation that state exposure is real and varies more than most compliance guides admit.
What does a compliant multilingual consent workflow look like end to end?
Here is a workflow a small outbound team can actually build.
Step 1: List every language your campaign touches. Not only the languages you call in, but the languages of the ads, landing pages, and lead forms feeding the campaign.
Step 2: Create a separate, legally reviewed consent form for each language. English original first, then professional legal translation (not Google Translate), then review by a bilingual attorney or compliance consultant who knows TCPA language requirements.
Step 3: Route each consumer to the form matching their language. Usually that means setting a language parameter in your CRM at the lead-gen stage and carrying it through to the consent workflow.
Step 4: At consent, capture the language version ID, timestamp, IP, phone number, and campaign source. Write it to a tamper-evident store.
Step 5: Before any call, scrub the number against the national DNC registry and your internal suppression list. [7] Both checks, every time.
Step 6: For a prerecorded or autodialed call, play the language-matched audio file. Never mix English audio with Spanish-consented leads.
Step 7: Log every call attempt, outcome, and opt-out request. For opt-outs in a non-English language, translate and log the substance of the request, not only the fact that one arrived.
Step 8: Honor opt-outs within 10 business days (the TSR floor), though 24 to 48 hours is the standard I would hold your team to. Suppress the number across every language and campaign for that consumer.
Step 9: Audit consent records quarterly. Pull a random sample, confirm the stored language version matches the language of the originating campaign, and check that DNC scrubs are current.
Text components follow the same rules. Our article on text message marketing covers SMS-specific consent in more depth, including the CTIA guidelines carriers now enforce at the platform level.
What happens if you get sued over multilingual consent failures?
TCPA gives any person who got an illegal call a private right of action worth $500 per violation, or $1,500 per violation if the court finds the conduct willful. [1] There is no damages cap on class actions, which is why TCPA suits have produced some of the largest consumer settlement funds in U.S. history.
Language matters most at class certification. Plaintiffs' attorneys hunt for systematic failures, and a consent form consistently served in the wrong language is precisely the common question that supports certification. Use one English-only form for 50,000 Spanish-speaking leads and you are looking at 50,000 potential violations at $500 to $1,500 each. Run the math.
The FCC has its own enforcement power under 47 U.S.C. § 503. It can assess forfeitures up to $23,727 per violation (inflation-adjusted through 2024) and up to $1,913,265 for a single continuing violation. [11] FCC actions over language-related consent are rarer than private suits, but the Commission has cited "clear and conspicuous" disclosure failures in its enforcement orders.
Most cases settle. Settling still costs money, attorney's fees, and management hours. And a class settlement usually forces you into remedial compliance measures under court monitoring. Those monitoring costs over three to five years often run past the settlement itself.
The best defense is documented, language-matched consent you can produce fast when a demand letter arrives. Plaintiffs' attorneys size up cases largely on whether the defendant can produce records. A company that can hand over 50,000 clean consent records in the right language is a worse target than one that can produce nothing.
Frequently asked questions
Does TCPA require consent forms to be in the consumer's native language?
The statute (47 U.S.C. § 227) does not say so in those words, but it requires consent to be "clear and conspicuous," which courts and the FCC read to mean the consumer must actually understand what they agreed to. A form in a language the consumer cannot read fails that test. California and New York add language-access duties for certain industries on top of that.
Can I use Google Translate to create a Spanish or Mandarin consent form?
Not if you want it to survive litigation. Machine translation produces phrasing that can be inaccurate or too informal, softening required disclosures. A TCPA consent form has to convey precise legal obligations. Pay a professional legal translator, then have a bilingual attorney confirm every required element is present and accurate. That cost is a fraction of defending a class action.
What if my lead vendor provided the consent in English and I'm calling Spanish speakers?
You own that risk. If the language of the consent form did not match the consumer's language, the consent was likely invalid no matter which company obtained it. The FCC's 2023 one-to-one consent rule pushed toward company-specific consent before it was vacated in early 2025, but state mini-TCPA laws and the "clear and conspicuous" standard still apply. Audit your vendors' forms before you call a single number.
Do DNC rules apply differently for non-English-speaking consumers?
No. The National Do Not Call Registry covers all residential and mobile numbers regardless of language. You must scrub before calling and re-scrub every 31 days. The FTC makes no language-based exceptions. A Spanish-speaking consumer who registered gets the same protection as an English speaker, and you face the same per-violation penalty, up to $51,744 in 2024, for calling them.
How do I handle opt-out requests made in a non-English language?
Honor them immediately. The FCC's rules let consumers revoke consent by any reasonable means. Refusing to process a Spanish-language opt-out because your system only recognizes English keywords is a violation. Train your agents, configure your IVR to detect STOP-equivalents in your target languages, and log non-English opt-outs with a translation note in your suppression system.
What is the statute of limitations for TCPA claims related to multilingual consent?
Federal TCPA claims have a four-year statute of limitations under 28 U.S.C. § 1658. Some states allow their own analogs or consumer protection claims with different timelines, often three years. California CIPA claims for recorded calls run one or three years depending on the theory. Keep consent records at least four years, ideally five, to cover overlapping state claims.
Do the same consent rules apply to SMS and text message campaigns in other languages?
Yes, and then some. TCPA's ATDS consent requirement applies to texts the same way. The CTIA's carrier guidelines add a layer: carriers now filter messages from non-compliant senders, and a language-mismatched opt-in flow can trigger filtering before any lawsuit. Your STOP handling has to work in every language you message in, and opt-in confirmations should be in the consumer's language.
How much does TCPA per-violation exposure cost if multilingual consent is invalid?
Each call or text to a number without valid consent can cost $500 per violation, or $1,500 for a willful violation under 47 U.S.C. § 227(b)(3). There is no statutory cap on class actions. A campaign that made 10,000 calls to consumers who consented in the wrong language could face $5 million to $15 million in statutory damages before any attorney fee multiplier.
Does recording a call with a non-English-speaking consumer require special disclosures?
Yes. Every state with a two-party or all-party recording law (California under CIPA, Washington, Illinois, Florida, and others) requires all parties to be notified of the recording before it begins. That disclosure has to be in a language the consumer understands. An English-only "this call may be recorded" delivered to a Mandarin-only speaker does not satisfy California's Penal Code § 632.
Can I get consent through a bilingual agent on a live call rather than a written form?
For telemarketing calls to cell phones using an autodialer, you need prior express written consent, meaning a signed agreement before the call. A live agent cannot obtain that during the same call that would be the violation. For live calls to landlines or informational (non-telemarketing) calls, oral consent on a recorded call can work, but it still has to be in the consumer's language to mean anything.
What are the FCC's current rules on consent for automated calls after 2024?
The FCC's December 2023 Report and Order aimed to require prior express written consent on a one-to-one basis, one consent per seller rather than a blanket consent for an aggregator's network. The Eleventh Circuit vacated that one-to-one provision in January 2025. The "clear and conspicuous" standard and the written-consent requirement remain, so language-matched, company-specific consent forms are still the safe approach for autodialed campaigns.
How do I verify that a third-party lead generator obtained valid multilingual consent?
Ask for a sample of actual consent records, including the exact form version used, the timestamp, and the language of the form. Get a contractual representation and warranty that consent was obtained in the consumer's language and complies with 47 CFR § 64.1200. Audit a random 5 to 10 percent of leads before calling. If the vendor cannot produce records or resists audits, stop buying from them.
Is there a safe harbor if a consumer lies about their language preference during opt-in?
There is no explicit TCPA safe harbor for consumer misrepresentation at opt-in. Courts do weigh whether the company took reasonable steps to match the consumer's language. If your system defaulted to English for someone who completed a Spanish-language ad flow, that is on you. If the consumer chose English from a language selector, that is a different and more defensible fact pattern.
What tools or processes help manage consent records across multiple languages?
CRM systems with custom fields for language version ID and consent form hash work well at small scale. Larger campaigns benefit from a consent management platform that stores immutable records with timestamps, IP addresses, and form version snapshots. Whatever you use, verify it exports records fast, since demand letters tend to arrive with tight response windows.
Sources
- U.S. Government, 47 U.S.C. § 227 (TCPA statute text via Cornell LII): TCPA prohibits ATDS/prerecorded calls to wireless numbers without prior express written consent; allows $500-$1,500 per-violation damages
- California Department of Financial Protection and Innovation: California DFPI requires financial services disclosures in languages other than English when marketing is conducted in that language
- New York State Legislature, Executive Law § 296-a: New York law requires certain businesses to provide consumer-facing documents in languages used by a significant portion of customers
- FTC, Telemarketing Sales Rule 16 CFR Part 310: TSR prohibits deceptive practices in telemarketing; requires prompt identification; mandates 24-month recordkeeping; requires internal DNC list within 30 days of opt-out request
- FTC, National Do Not Call Registry: Telemarketers must scrub against the DNC registry before calling and re-scrub at minimum every 31 days; applies to all residential and mobile numbers regardless of language
- FTC, National Do Not Call Registry (donotcall.gov): DNC registry access costs $75 per area code per year as of 2024, capped at $19,725 for all area codes nationally
- Florida Legislature, Florida Telephone Solicitation Act (FTSA) § 501.059: Florida FTSA imposes state-level consent requirements for autodialed calls that differ from federal TCPA in certain respects
- California Legislature, Penal Code § 632 (CIPA): California CIPA requires all-party consent for recorded calls; $5,000 statutory damages per violation; courts have certified class actions under this statute
- U.S. Code, 47 CFR § 64.1200 (FCC implementing regulations for TCPA): 47 CFR § 64.1200 requires prior express written consent that clearly and conspicuously authorizes calls and describes the telemarketing goods or services