Last updated 2026-07-11
TL;DR
Bilingual consent is valid under the TCPA, but only if every part of a compliant disclosure appears in the same language the consumer used with you. An English disclosure shown to a Spanish speaker does not satisfy 47 U.S.C. § 227. You need matching language, an affirmative opt-in act, a timestamp, and a stored record. Courts and the FCC have thrown out consents that missed any one of those four.
What does the TCPA actually require for valid consent?
The TCPA, codified at 47 U.S.C. § 227, bans autodialed or prerecorded calls and texts to cell phones without the prior express written consent of the called party [1]. That written standard applies to marketing calls and texts. The FCC defined it in its 2012 rules as an agreement that is "clearly and conspicuously disclosed" and that the consumer has "signed," which includes an electronic signature like a checkbox click [2].
The statute never mentions language. The FCC rules never say English. What both require is that the disclosure be clear and conspicuous, that the consumer actually understand what they're agreeing to, and that the consent come from an affirmative, knowing act. A consumer who reads only Spanish and sees only an English disclosure has agreed to nothing they understood. That is the whole problem with bilingual contact situations, stated plainly.
Courts judge TCPA consent by asking whether a reasonable person in the consumer's shoes would have understood what they signed up for. If the agreement was written in a language they don't read, the answer is almost always no.
The 2015 FCC Declaratory Ruling added that marketing consent must be obtained per call or text and that the agreement must name the telemarketer or seller who will make contact [3]. That naming requirement creates a second translation job. Your company name and what you sell have to appear in the consumer's language too.
Why does language mismatch invalidate consent?
A consent form that doesn't match the consumer's language fails the "clearly and conspicuously disclosed" standard in 47 C.F.R. § 64.1200(f)(9) [4]. The exposure runs deeper than that single regulation, though.
The FTC's Telemarketing Sales Rule overlaps with TCPA duties for most outbound teams, and it requires material terms to be disclosed in the language principally used in the sales presentation [5]. If your agent closed a lead in Spanish but your consent checkbox was English only, you now have a TSR problem stacked on a TCPA problem.
State law adds a third layer. California's Consumer Legal Remedies Act and Civil Code § 1632 require that contracts for goods or services negotiated primarily in Spanish, Chinese, Tagalog, Vietnamese, or Korean be provided in that language before the consumer signs [6]. Illinois and New York carry similar rules. State violations don't just trigger state fines. A plaintiff's lawyer stacks those state claims on top of TCPA claims to drive the settlement number up.
Here is how it plays out in practice. In cases involving Spanish-speaking consumers routed through English-only consent flows, courts have voided the consent and let the TCPA claims move toward class certification. You can see what that exposure looks like in dollars in the cash app tcpa class action settlement. Those numbers are ordinary, not extreme.
The short version: if your landing page is in Spanish, your agent spoke Spanish, or your lead source targets Spanish-dominant consumers, your consent disclosure has to be in Spanish. Full stop.
Which languages do you actually need to support?
There is no federal list that mandates specific languages. The rule is functional. Match the language of the interaction. If a consumer fills out a form in Spanish, consent goes in Spanish. If an agent runs an intake call in Mandarin, any written consent that follows goes in Mandarin.
U.S. Census Bureau data puts Spanish far ahead of every other non-English language, with roughly 41 million people who speak it at home [7]. Run any outbound program at scale and you are reaching Spanish speakers, guaranteed. Vietnamese, Cantonese, Korean, and Tagalog come next in many western and coastal markets.
California's Civil Code § 1632 is the most specific language trigger in U.S. law. It covers contracts primarily negotiated in Spanish, Chinese, Tagalog, Vietnamese, or Korean, and it forces you to hand the consumer a translated copy before they sign [6]. California holds about 12% of the U.S. population, so any national program touches this rule.
Most small outbound teams should carry, at minimum, a Spanish version of every consent disclosure they use. If your lead sources reach big Vietnamese, Korean, or Chinese communities (think Houston, Los Angeles, San Jose), those languages belong in your consent kit too.
For cold calling campaigns where a live agent takes verbal consent before a transfer, the language rule attaches to what the agent says out loud more than to whatever form gets filed afterward.
What exact elements must appear in a bilingual consent disclosure?
Every language version of your disclosure has to carry every required element. You can't put the legal detail in English and a friendly summary in Spanish. Here is the full list.
| Element | What it must say | Source |
|---|---|---|
| Clear and conspicuous placement | Consent text near the submit button, not buried in fine print | 47 C.F.R. § 64.1200(f)(9) [4] |
| Identity of the seller/caller | The specific company name that will call or text | FCC 2015 Ruling [3] |
| Methods of contact authorized | Autodialed calls, prerecorded calls, SMS, or all three, stated plainly | 47 C.F.R. § 64.1200(f)(9) [4] |
| "Not a condition of purchase" language | Consent is not required to buy goods or services | 47 C.F.R. § 64.1200(f)(9)(iii) [4] |
| Affirmative opt-in action | Unchecked box, signature, or affirmative click; pre-checked boxes fail | FCC 2012 Order [2] |
| Contact info for the consumer | Where they can reach the seller | FTC TSR, 16 C.F.R. § 310 [5] |
All six items have to land in the consumer's language. A Spanish speaker who submits your form needs to see every one of them in Spanish. The English block sitting next to it does nothing for their disclosure.
The classic failure: a team translates the consent text but drops the "not required to purchase" line because the translation vendor treated it as boilerplate and cut it. Audit every language version against your English master, line by line.
How should you handle opt-in forms with bilingual consumers?
The cleanest move is a single-language form. Detect or ask the consumer's preferred language, then serve the form entirely in that language. You don't need English and Spanish on the same page. Dual-language forms actually create risk, because if the two versions drift apart even slightly, a plaintiff's lawyer picks whichever one favors the plaintiff.
If you have to show two languages (some government-adjacent programs require it), get both versions reviewed by a legal translator rather than a bilingual employee, and have compliance counsel confirm the two say the same thing. Lock the document version so they can't diverge over time.
For web forms, your tech setup matters as much as your wording. The timestamp, IP address, form field values, and page URL all have to land in your database at the moment of submission [8]. "We had a Spanish form" is not a defense. You have to be able to produce the exact HTML a specific consumer saw on a specific date, in the language they saw it.
Use a third-party lead supplier and you own the consent they collected for you. The FCC's 2012 order is clear that consent must name the specific seller. A lead gen vendor who gathered generic consent without your company's name has handed you nothing valid, no matter the language [2]. Demand a copy of their exact disclosure in every language they run, and confirm your company name is in it.
LeadCompliant's consent kit includes Spanish and English template disclosures with all six required elements, timestamped storage guidance, and a checklist for auditing third-party lead consent. That paperwork is what separates a quick dismissal from a settlement when a demand letter shows up.
Can you get consent by phone in Spanish and have it hold up?
Verbal consent by phone is valid under the TCPA for informational calls. For marketing calls and texts you generally need prior express written consent, which means a written or electronic record. A phone call by itself does not meet the written requirement for autodialed marketing messages [1].
There's one real exception. If you run an Interactive Voice Response (IVR) system that records the consumer pressing a key or saying "yes" after a full disclosure, and you store that recording, courts have generally treated it as a valid electronic signature [8]. The IVR disclosure has to be entirely in the consumer's language, including the "not required to purchase" line.
Inbound calls make the consent stronger. When the consumer calls you, hears a disclosure in their language, and presses to confirm, they initiated the contact. Outbound IVR runs into a wall: you can't use an autodialer to call a cell phone to get consent to call that same cell phone with an autodialer. That circular problem is well recognized, and courts don't wave it through.
Live agent flows work differently. A Spanish-speaking agent can read a disclosure word for word, get a yes, and record the call. But if you plan to use an autodialer for future marketing, you still need a written confirmation on top. The verbal consent covers the call in progress. It doesn't build the written record you need for automated contact later.
What documentation do you need to prove bilingual consent was valid?
Documentation is where most consent programs collapse. A perfectly worded Spanish disclosure means nothing if you can't prove a specific consumer saw it on a specific date.
At minimum, retain:
1. A snapshot or archived copy of the exact disclosure the consumer saw, including which language version, at the time of submission. 2. A submission timestamp in UTC with the consumer's local time zone noted. 3. The IP address of the device used. 4. The specific form fields filled, including any language-selection indicator. 5. The URL of the page where consent was collected. 6. A record linking that consent event to the phone number you later contacted.
The FCC has not set a minimum retention period for TCPA consent records. The statute of limitations for TCPA claims runs four years under 28 U.S.C. § 1658 [9]. Keep records for at least five years to be safe. Some plaintiff's firms push for longer under state-law tolling.
If you use a CRM or marketing automation platform, build a field that stores the language of consent collection, more than "consent: yes." When a demand letter lands (and at any real volume, one will), you want to pull a single record and hand it to your attorney inside an hour. If proving consent means a developer reconstructing a session from server logs, you'll probably settle instead of fight.
For a wider look at what recordkeeping failures cost, the credit one tcpa settlement shows how consent gaps compound into serious exposure.
What do the FCC and FTC say specifically about language in consent?
No FCC ruling says "consent must be in the consumer's language" in those words. What the FCC did say, in its 2012 Report and Order and 2015 Declaratory Ruling, is that the disclosure must be "clear and conspicuous" and that consent must be informed [2][3]. Those two standards do the work.
The FTC is blunter. The Telemarketing Sales Rule at 16 C.F.R. § 310.3(a)(1) requires material disclosures to be made in a truthful, clear manner, and FTC guidance confirms disclosures have to be in the language used in the sales call or ad [5]. The FTC has brought enforcement actions against companies that gave English disclosures to consumers solicited in Spanish.
The Consumer Financial Protection Bureau matters for anyone selling financial products. Its supervision and examination materials direct that disclosures be provided in the language used to market the product [10]. Sell insurance, mortgages, or credit cards and CFPB standards stack on top of TCPA and TSR.
A 2024 FCC rulemaking tightened consent further, requiring that consent for AI-generated calls be clear and knowing and that it apply to a single identified seller instead of a daisy-chain of lead buyers. That rule reinforces the direction of travel: generic or ambiguous consent, in any language, keeps getting riskier.
The honest read is that federal agencies expect language-matched consent even where they don't spell it out, because a disclosure a consumer can't read is not, by any reasonable definition, clear.
What are the biggest mistakes teams make with bilingual consent?
The mistakes are predictable because they share one root cause: treating translation as a chore instead of a legal duty.
Mistake one is machine-translating an English form with no legal review. Google Translate and DeepL are fine for understanding content. They are not reliable for legal text. "May contact" versus "will contact" changes the entire meaning of the consent, and a plaintiff's lawyer will find the slip.
Mistake two is having a bilingual employee check the translation with no paper trail. "Maria in the office reviewed it" is not a defense. You want a professional translator (ideally certified for legal work) plus a record of who reviewed it and when.
Mistake three is collecting consent in Spanish but storing it in the CRM as a bare checked box with no language version. When a Spanish-only speaker says they never agreed to calls and your record shows only "opt-in: true," you can't prove otherwise.
Mistake four is dropping the "not required to purchase" line from the translated version. That's the most litigated element of TCPA consent. It has to be present and clear in every language version.
Mistake five is trusting a lead vendor's word that they got valid consent. Get the actual disclosure text, in every language the vendor uses. Confirm your company name is in it. Confirm the submission date. If the vendor won't hand it over, don't buy the leads.
To check whether your flow covers the DNC side too, see how do i get the do not call list and mobile phone do not call list. Consent and DNC scrubbing are separate obligations, and both have to be right.
Does California's bilingual contract law create extra obligations?
California Civil Code § 1632 is the state law that hits bilingual outbound programs hardest. It covers any contract for services primarily negotiated in Spanish, Chinese, Tagalog, Vietnamese, or Korean. "Primarily negotiated" points at the language of the sales pitch or discussion, more than the fact that the consumer happens to speak it [6].
When § 1632 applies, you have to give the consumer a translation of every term and condition in the language used to negotiate, before they sign. A summary won't cut it. The consumer gets the full translated document to review first.
Break § 1632 and the consumer can rescind the contract. In a TCPA context, that makes the consent itself voidable. A consumer sold a service in Spanish but handed only an English consent form can argue the consent is void under § 1632, then stack a TCPA claim on top of that.
New York runs a narrower version in its Banking Law, Texas has floated similar requirements over the years, and Illinois has consumer fraud interpretations that cut the same way. For any national outbound program, treat California's standard as the bar to clear.
Do business in California with a sales team or lead forms that reach Spanish, Chinese, Tagalog, Vietnamese, or Korean speakers and you need compliant translated contracts. This is not optional and it is not free. A certified legal translation of a one-page consent disclosure usually runs $150 to $400 per language depending on complexity. That's cheap next to a rescission claim in California.
How should text message marketing consent work in Spanish?
SMS consent carries the same TCPA requirements as voice consent, but the mechanics shift because the opt-in often happens through a text keyword. For text message marketing aimed at Spanish speakers, the keyword opt-in flow has to be in Spanish.
A compliant Spanish SMS opt-in looks like this. The consumer sees an ad or web page in Spanish telling them to text a keyword to a short code. The disclosure on that page names who will text them, what kind of messages, roughly how many per month, that message and data rates may apply, and that consent is not required to buy anything. All of that is in Spanish.
When the consumer texts the keyword, the auto-reply confirmation comes back in Spanish too. It restates what they signed up for and tells them to reply STOP to cancel and HELP for help. STOP and HELP still work in English even in a Spanish flow, because CTIA guidelines require those commands to function regardless of the program's language.
Here's a common miss: a Spanish keyword and a Spanish confirmation, but an English-only privacy policy and terms linked in that confirmation. Courts have generally not required linked policies to be translated (they aren't the consent disclosure itself), but plaintiff's firms increasingly argue that a consumer who can't read the linked terms didn't give fully informed consent. The safe move is a Spanish summary of the key terms, accessible from the flow.
For ongoing campaigns, keep a record of every opt-in by phone number, including the language of the flow. If you switch platforms or re-import your list, that language metadata has to travel with the record.
How do you audit an existing consent program for bilingual compliance gaps?
If you already run outbound and you're unsure whether your bilingual consent holds, here is a practical audit that takes about a day.
First, pull a sample of 50 opt-in records for consumers with Spanish surnames or phone numbers tied to high-Hispanic-density area codes. Check whether each record has a language indicator. If more than a handful show no language metadata, you have a documentation gap no matter how good your translated forms are.
Second, retrieve the exact version of your consent disclosure that was live on the date of each sample record. If you can't, because a form got edited with no version control, that's an immediate fix. Archive form versions with a tool, or take dated screenshots every time you change a consent flow.
Third, put your Spanish and English disclosures side by side. Check for all six required elements in both. Note any difference in phrasing, especially around the "not required to purchase" clause.
Fourth, pull your third-party lead supplier contracts. Find the section describing the consent disclosure the vendor uses. If there isn't one, send a written request for it. If the vendor can't produce the actual disclosure text in each language they run, stop buying from them until they can.
Fifth, check your DNC scrubbing. Valid consent and DNC compliance are separate obligations. A consumer who gave valid Spanish consent but sits on the National DNC Registry still can't get marketing calls without an established business relationship. The do not call list guide explains how those obligations interact.
LeadCompliant's compliance kit includes an audit checklist that walks all five steps plus a log template for your findings. Running this once a year is a reasonable standard of care.
Frequently asked questions
Does the TCPA require consent disclosures to be in Spanish?
The TCPA's text names no language. But the FCC requires consent to be "clearly and conspicuously disclosed," which courts read to mean the consumer must actually understand what they're agreeing to. A consumer who reads only Spanish cannot give informed consent to an English-only disclosure. Language matching is therefore required in practice, even though the statute never uses the word Spanish.
Is a machine-translated consent form good enough?
No. Machine translation makes enough errors in legal text to create real liability. A mistranslated phrase can change the legal meaning of the consent, and a plaintiff's attorney will find it. Use a professional translator with legal or regulatory experience, and document who reviewed it and when. The cost runs $150 to $400 per language for a short consent form.
What happens if a lead vendor collected consent in English for a Spanish-speaking consumer?
The consent is likely invalid, which puts you on the hook for TCPA liability on every call or text made under it. You own the job of validating consent your lead vendors collected for you. Ask for the exact disclosure text in every language they use, and confirm your company name appears in it. If they can't provide that, don't use the leads.
Can verbal phone consent in Spanish satisfy the TCPA's written consent requirement?
For informational calls, verbal consent is enough. For autodialed or prerecorded marketing, the TCPA requires prior express written consent, meaning a written or electronic record. An IVR recording of a consumer pressing a key after a Spanish disclosure can qualify as an electronic signature, but you have to store the recording and meet every other disclosure element.
How long do I need to keep bilingual consent records?
The TCPA statute of limitations is four years under 28 U.S.C. § 1658. Most compliance practitioners keep consent records at least five years. Your records need the exact text of the disclosure the consumer saw, the language version, a timestamp, and the phone number and IP address tied to the opt-in event.
Does California's bilingual contract law apply to TCPA consent forms?
California Civil Code § 1632 applies to contracts for services primarily negotiated in Spanish, Chinese, Tagalog, Vietnamese, or Korean. If your sales process or lead form interaction ran in one of those languages with a California consumer, § 1632 requires a full translation before the consumer signs. Break it and the consumer can rescind, which can void the TCPA consent.
Do the STOP and HELP keywords need to be in Spanish for Spanish SMS opt-in programs?
CTIA guidelines require STOP and HELP to work as opt-out and help commands regardless of the program's language. Your confirmation and ongoing messages should be in Spanish, but a consumer texting STOP in English to a Spanish program still has to be honored. Some programs also add PARA or DETENER as a Spanish stop command as a best practice.
What does "clearly and conspicuously disclosed" mean for a bilingual web form?
The FCC's 2012 order describes a disclosure that a reasonable consumer would notice and understand. It sits near the submit button, not buried in a footer or a scroll-away wall of fine print. On a bilingual form, each language version's disclosure has to meet that placement standard on its own, in that language's reading context.
What languages beyond Spanish should outbound teams think about?
California's Civil Code § 1632 names Spanish, Chinese, Tagalog, Vietnamese, and Korean. FTC guidance extends to any language used in the sales presentation. For most national U.S. outbound programs, Spanish is the clear priority. Teams with heavy presence in Houston, Los Angeles, or the Bay Area should also weigh Vietnamese and Tagalog, given Census Bureau language data for those markets.
Can I use a pre-checked checkbox in a Spanish consent form?
No. The FCC's 2012 Report and Order requires an affirmative opt-in act. A pre-checked box does not qualify as prior express written consent under the TCPA, in any language. The consumer has to actively check the box, click a button, or take some other affirmative step to show agreement, not simply fail to uncheck a box.
Do text messages themselves need to be in Spanish if consent was collected in Spanish?
The TCPA does not require marketing messages to be in any specific language. But if Spanish-speaking consumers get English-only texts, you'll see higher opt-out rates, more complaints, and possible unfair business practice claims in states like California. Practically, match the message language to your audience even where it isn't a strict TCPA requirement.
How does the FTC Telemarketing Sales Rule intersect with bilingual TCPA consent?
The FTC's TSR at 16 C.F.R. § 310.3(a)(1) requires material disclosures in the language used in the sales presentation. If your agent spoke Spanish and your disclosure was English only, you have a TSR violation on top of any TCPA problem. The FTC has brought enforcement actions on this basis. Both duties are easier to meet together with language-matched disclosures.
What is the fine for a TCPA violation where consent was in the wrong language?
TCPA statutory damages are $500 per negligent violation and $1,500 per willful violation [1]. Those amounts are per call or text, not per consumer. A class action across thousands of contacts can reach millions before any willful multiplier. The Credit One and Cash App settlements both topped $10 million, driven mostly by contact volume rather than a single large penalty.
Sources
- Cornell Law School Legal Information Institute, 47 U.S.C. § 227: TCPA prohibits autodialed or prerecorded calls to cell phones without prior express written consent; statutory damages are $500 to $1,500 per violation
- Electronic Code of Federal Regulations, 47 C.F.R. § 64.1200: Defines prior express written consent elements including clear and conspicuous disclosure, not required to purchase language, and affirmative opt-in requirement
- FTC, Telemarketing Sales Rule, 16 C.F.R. Part 310: TSR requires material disclosures to be made in the language used in the sales presentation; FTC guidance covers Spanish-language sales with English-only disclosures
- California Legislative Information, Civil Code § 1632: Contracts for services primarily negotiated in Spanish, Chinese, Tagalog, Vietnamese, or Korean must be provided in translation before the consumer signs; violation allows rescission
- U.S. Census Bureau, Language Use in the United States: Spanish is the most spoken non-English language in the U.S. with roughly 41 million people who speak it at home
- FTC, Complying with the Telemarketing Sales Rule: Records of consent including timestamp, IP address, and disclosure version must be retained to demonstrate compliance with consent requirements
- Cornell Law School Legal Information Institute, 28 U.S.C. § 1658: Federal statute of limitations for TCPA claims is four years from accrual
- Consumer Financial Protection Bureau, Supervision and Examination Manual: CFPB guidance directs that disclosures be provided in the language used to market or advertise the product or service