Calling Cell Phones: TCPA Consent Rules

As of October 16, 2013 in the USA, the FCC revised its rules on placing phone calls and sending text messages to cell phones using an ATDS, an automatic telephone dialing system. Under the TCPA, you now need prior express written consent from the person you are calling before an auto-dialer touches a wireless number. This is the heart of the Cellphone calling rule, and it is the difference between a routine outbound campaign and a stack of statutory damages. The same standard applies to texts, so an SMS blast to cell phones is treated like an auto-dialed call.

Operators sometimes assume the rule only covers obvious robocalls. It does not. It reaches any campaign where the equipment can dial cells without a person triggering each call, which describes most predictive and progressive setups. So the question to ask before any wireless outreach is simple: do I have written consent for this number, and if not, am I dialing it by hand?

What the Cell-Phone Rule Actually Requires

The rule is narrow but strict. It applies to cell phones, not landlines, and it applies when the call or text goes out through an ATDS. The consent you collect has to be written and specific, not a vague checkbox buried in terms of service. That standard of consent is itself a defined thing, the kind of Express written consent that names the caller, the number, and the purpose, and discloses that an automated system may be used. Without it, your two safe paths are to get that signed agreement or to call wireless numbers only by Manual dialing (click to dial) from a system that has no auto-dial capacity at all.

On the dialer side, the practical defense is keeping wireless numbers out of any auto-dialed Lead list unless you hold consent for them. That means tagging consent on the record as you collect it, and running a daily scrub that flags cells so they cannot slip into a predictive campaign. This work overlaps heavily with the do-not-call process, which we walk through in the VICIdial compliance overview, and with the federal registry described in what is the federal Do Not Call list. Treat cell-phone scrubbing as a sibling task to DNC scrubbing and you will run both from the same routine.

Keep in mind that following the FCC reading of the rule protects you from FCC actions and fines. It does not guarantee a clean result in civil court, where a judge may interpret the statute more broadly and treat any call to a cell as a potential violation. That is why most operators stay conservative: consent on file or no auto-dial, with no gray area in between.

The Consent Decision Flow

sequenceDiagram
  participant L as Lead record
  participant S as Scrub step
  participant D as Dialer
  participant C as Consumer cell
  L->>S: Is this a cell phone number?
  S-->>L: Flagged as wireless
  L->>D: Do we hold written consent?
  alt Consent on file
    D->>C: Auto-dial allowed
  else No consent
    D->>C: Manual dial only or do not call
  end

The flow shows the two checks every wireless lead should pass before an auto-dialer reaches it: is it a cell, and do you have consent. If either answer is wrong, the number drops to manual dialing or out of the campaign entirely. Build those two gates into your import and your nightly scrub, and the rule mostly enforces itself.

VICIfast configures dialing modes and scrubbing so cell-phone consent rules are enforced by default, not bolted on later. See pricing to set up a compliant campaign.