TCPA Prior Express Consent vs. Prior Express Written Consent

Consent is the exception that lets you legally call a number that would otherwise be off-limits — but the TCPA doesn't treat all consent the same way. Getting the distinction wrong is one of the most common compliance mistakes outbound teams make.

Prior express consent

This is the lower bar. Someone gives prior express consent simply by providing their phone number in a context that reasonably implies they're willing to be called about it — for example, giving their number on a form when applying for a loan. It doesn't need to be in writing, and it doesn't need to specifically mention telemarketing. It generally covers informational and non-marketing calls related to the transaction the number was given for.

Prior express written consent

This is the higher bar, and it's what's required for telemarketing calls and texts that use an autodialer or a prerecorded voice. To count, the consent generally needs to:

• Be in writing (including electronic — a checked box or e-signature counts).
• Clearly authorize the specific seller to deliver advertisements or telemarketing messages.
• State that the person doesn't have to agree to this as a condition of any purchase.
• Include the phone number the consent applies to.

A number provided casually — say, on a general contact form with no clear authorization language — usually doesn't meet this bar, even though it might satisfy the lower "prior express consent" standard for non-marketing purposes.

Why the distinction matters operationally

If your calling program only has prior express consent (not written), you're exposed the moment that call becomes a marketing call using an autodialer or prerecorded content. Teams that assume "we have their number, so we're fine" without checking which consent standard actually applies to what they're calling about are one of the most common sources of avoidable TCPA exposure.

Consent doesn't replace scrubbing

Even with solid consent on file, a number can still land on a DNC registry after the fact, or turn out to belong to someone associated with documented TCPA litigation activity. Consent and scrubbing answer different questions — one covers your legal basis for calling, the other covers whether the specific number carries known risk right now. A mature compliance process checks both, not one instead of the other.

Where this fits with Carrier Fence

Carrier Fence doesn't manage consent records — that lives in your CRM or dialer. What it does is catch the numbers that shouldn't be dialed regardless of what consent you think you have, by checking every number against DNC and honeypot data before you call. Get started free.