Here's the thing agencies discover the hard way: when your client hands you a list and you press send, "I was just following instructions" is not a defense. The plaintiff's attorney doesn't care whose CRM the numbers came from. They care who transmitted the message. And if you're the agency running the campaign, that's often you.
Full disclosure: I work for Ready, and we sell a standalone litigator/DNC scrub for $0.005 a contact. So I have a horse in this race. But the liability problem I'm describing exists whether you scrub with us, someone else, or not at all — and I'd rather you understand the actual mechanics than take my word for anything.
The "sender" is a fuzzier concept than you think
The TCPA lets a plaintiff go after anyone who "initiates" the call or text, and courts have read that broadly. If your agency built the campaign, uploaded the contacts, and clicked send, you initiated it. The fact that your client owns the relationship and told you to do it doesn't get you off the hook — it might make you co-defendants, but it doesn't move your name off the complaint.
I've written about the split of responsibility in more detail here: When Your Client's Bad List Gets Texted, Who Gets Sued?. The short version is that "the client swore the list was clean" is a business arrangement, not a legal shield. A well-drafted indemnification clause helps you recover money after you've been sued. It does not stop you from being named, served, and dragged into discovery.
So the goal isn't to make yourself un-sueable. It's to make yourself the least attractive defendant in the room, and to have a paper trail that shows you did the reasonable thing before you sent.
What a TCPA text actually costs when it goes wrong
The statutory damages are $500 per violation, trebled to $1,500 per text for willful or knowing violations. Per text. Not per campaign, per text.
Run the math on a modest blast:
- A client hands you a 12,000-contact list.
- Buried in it are 6 known TCPA litigators — people who have filed multiple suits and, in some cases, make a living doing it.
- You text all of them. Say each got 3 messages across the campaign.
- 6 litigators × 3 texts × $1,500 = $27,000 in potential exposure, from six numbers you could have suppressed for three cents total.
That's before legal fees, before the client relationship implodes, before the aggregation risk if any of them files a class action. And it came from a list you didn't build.
What a litigator scrub actually does — and doesn't
Let me be precise, because there's a lot of loose marketing in this category. A litigator scrub is not a magic "block the bad numbers" button. What it does is check each number against known TCPA-litigator lists and DNC-complainer lists — the people and numbers that have a documented history of filing complaints and suits over texts — and auto-suppress the matches before send.
A few honest clarifications:
- A litigator flag doesn't mean the number is illegal to text. It means this specific person has sued over a text before. I unpacked what a hit actually means here.
- A number can pass DNC and still belong to someone who'll sue you. DNC lists and known-litigator databases are different things, which is why a good scrub checks both.
- Scrubbing does not create consent. If the underlying list has no opt-in, a scrub doesn't fix that — it just removes the people most likely to make you pay for it.
So the scrub is a risk reducer, not immunity. Compliance is still ultimately the sender's responsibility. But it's a cheap, high-leverage risk reducer, and — the part agencies underuse — it produces a record.
The record is the point
Here's what most agencies miss. The dollar value of a scrub isn't only the numbers it suppresses. It's the timestamped log proving you scrubbed before you sent.
When you get named in a complaint, your posture is dramatically different if you can produce:
- A scrub record showing the list was checked against litigator and DNC data on a specific date.
- Evidence that flagged numbers were auto-suppressed and never received a message.
- A consent/attestation trail showing where opt-in was claimed.
That combination is what "reasonable diligence" looks like on paper. It doesn't guarantee dismissal. But it moves you from "reckless sender who blasted a raw purchased list" to "operator who ran standard compliance procedures and got caught by a number that slipped the net." Those are very different defendants, and plaintiff's attorneys settle with them very differently.
Ready records opt-in attestation for bulk and API sends and honors STOP/UNSUBSCRIBE automatically across campaigns, so the opt-out propagates and a suppressed contact can't be re-messaged by a later blast. Combined with the scrub log, that's an audit trail you can actually hand to a lawyer.
Timing is the whole game
The most common mistake I see: agencies import a client's list, run a campaign, then scrub before the next one. By then the violation already happened. As I've argued before, scrubbing after import is too late — one text to a flagged number is the violation.
The sequence that actually protects you:
| Step | When | Why it matters |
|---|---|---|
| Receive client list | Day 0 | Treat every list as dirty until proven otherwise |
| Run litigator + DNC scrub | Before first send | This is where the log timestamp lives |
| Suppress flagged numbers | Automatic, pre-send | Flagged contacts never receive a message |
| Send campaign | After scrub clears | Now your paper trail predates the send |
| Re-scrub on cadence | Every ~30 days for active lists | Lists rot — a clean list in January is dirty by March |
That last row matters more than agencies expect. Litigator lists grow, and an aged list picks up new flags over time. A one-time scrub 8 months ago is not the same as a current one.
The math makes this a non-decision
At $0.005 per contact, scrubbing is one of the cheapest line items you'll ever bill.
- 12,000-contact list: $60 to scrub.
- Six suppressed litigators at $1,500 each: $27,000 in avoided exposure.
- Even one avoided willful violation: $1,500 — that's 300,000 contacts' worth of scrubbing.
You don't need the scrub to catch a lot to pay for itself. You need it to catch one. I ran a fuller version of this comparison in Scrubbing 100,000 Contacts Costs $500 — One Complaint Costs $500 to $1,500 Per Text, and the ratio holds at every scale.
For an agency, this is also a billable service, not just an internal cost. You can pass the scrub through to clients as a compliance line item — most clients would rather pay three cents a contact than roll the dice on a list they can't vouch for. And it gives you a legitimate reason to require a scrub before you'll run any imported list, which is a policy worth having in writing.
Build it into your standard operating procedure
The point of all this isn't to scrub once when you remember. It's to make scrubbing a non-negotiable gate every list passes through, so that "did we scrub?" is never a question after a complaint lands.
A workable agency policy:
- No imported client list gets sent until it's scrubbed. No exceptions, no "the client says it's fine."
- Scrub logs are archived per client, with dates, and retained for at least the statute of limitations window (four years, to be safe).
- Active lists get re-scrubbed on a ~30-day cadence.
- Quiet-hours enforcement and STOP handling stay on for every campaign — the scrub is one layer, not the whole stack.
- Your client contract requires the scrub and documents that opt-in is the client's warranty.
The practical takeaway
You can't fully offload TCPA liability to your client, and no amount of contract language moves your name off a complaint if you're the one who pressed send. What you can do is be the defendant who documented their diligence — scrubbed before sending, suppressed the known litigators, kept the timestamped log, honored every opt-out.
That's a $0.005-per-contact habit that turns a potential $27,000 problem into a $60 procedure and a piece of paper that helps you sleep. Ready runs standalone litigator and DNC scrubbing at that price, alongside automatic STOP handling, quiet-hours enforcement, and consent capture — you can see how the compliance pieces fit together on the product page, or just sign up and scrub your next client list before you send it.
Not because it makes you lawsuit-proof. Because it makes you the operator who did the reasonable thing, on the record, before anyone asked.