What Does a Compliance Officer Do in Pay Per Call?

A compliance officer in [pay per call](/networks-buyers-and-compliance/tcpa-compliance-for-pay-per-call-what-you/) keeps a network out of court. That's the short version. The longer version means reading a lot of call recordings, memorizing rules most people have never heard of and telling salespeople "no" during their favorite quarter. It isn't glamorous. But it's the difference between a business that scales and one that gets a letter from a law firm.

Let me explain what the job actually looks like day to day, because the title makes it sound like a person filing paperwork in a beige room. In practice it's closer to refereeing a game where half the players would happily cheat if nobody watched.

The rules they're paid to know cold

The centerpiece is the Telephone Consumer Protection Act, the TCPA, on the books since 1991 and still generating lawsuits at a healthy clip. Penalties run roughly $500 to $1,500 per violating call. That per-call math is what makes plaintiff attorneys smile. One bad campaign that dials thousands of numbers can turn a rounding error into a seven-figure problem overnight.

A compliance officer's whole job is to keep that number at zero.

Then there's the FTC's Telemarketing Sales Rule, the TSR, which covers deceptive practices, required disclosures, and the National Do Not Call Registry. The two overlap in annoying ways, and knowing where they diverge is part of what you're paying a compliance person for. They also track the 2021 Facebook v. Duguid decision, where the Supreme Court narrowed what counts as an autodialer, or ATDS. That ruling changed how a lot of calls can legally be generated, and a good officer factors it into every conversation about dialing tech.

The newer headache is one-to-one consent. Recent FCC actions require that a consumer's consent name a single specific seller. No more bundling one opt-in across twelve companies and calling it a day. If your consent form says a person agreed to hear from "our partners," well, that's now a nice way to light money on fire.

What they actually do all day

Here's the part people underestimate. A compliance officer listens to calls. Real ones.

Most teams audit a sample of call volume, usually somewhere between 1% and 10%, depending on how nervous they are and how many lawyers they've already met. The officer pulls recordings and checks two things: whether the agent followed the approved script, and whether consent was captured correctly before anything sensitive happened. These aren't abstract checks. A missing disclosure in an insurance transfer is the kind of thing that shows up in a demand letter eighteen months later.

Disclosure requirements get specific by vertical. Insurance, home services, and legal all have their own rules, and some states mandate exact language before a call transfers to a buyer. So the officer isn't just checking "did they disclose." They're checking whether the agent said the exact words this particular state requires, in this particular order, before the handoff. It's finicky. That's the job.

They also keep records. Consent, opt-outs, and suppression lists usually get retained for four to five years to line up with FTC expectations. If a regulator ever asks how you got permission to call someone in March of two years ago, you want an answer better than "trust me." A suppression list that actually works is boring and unglamorous and will save your business someday.

Tools matter here. Compliance teams lean on platforms like Ringba, Retreaver, and Invoca for call tracking, recording, and routing controls. Industry groups like the Professional Association for Customer Engagement, PACE, publish guidance officers reference when the law is vague, which is often. None of these tools do the thinking for you. But they give a compliance person the receipts to prove what happened on a call.

The part almost everyone gets wrong

Anyway, here's the mistake I see over and over. People assume compliance is about the offer and the buyer. It isn't. It's mostly about the traffic.

A network can be held liable for a partner's illegal calls even when the network did nothing wrong directly. Read that again if you run a network. Your publisher runs a shady dialer, generates calls that violate the TCPA, and the exposure lands on you. That's why a real compliance officer spends serious time vetting upstream traffic sources and publishers, not just the end campaign.

Vetting means asking uncomfortable questions. Where did this traffic come from? Show me the consent language. What's your dialer setup after Duguid, and can I see a sample of your call recordings? Publishers who get defensive at those questions are telling you everything you need to know. I've watched networks skip this step because a publisher was sending volume and the numbers looked great. The volume was great right up until it wasn't. I wrote more about publisher vetting habits over on AdamYoung.com, because it deserves its own long conversation.

The uncomfortable truth is that good compliance costs you some short-term revenue. You'll turn away traffic that would have paid this month. A weak compliance officer folds under that pressure. A good one holds the line and lets you sleep.

What it pays, and whether you need one

Compliance roles in pay per call and lead generation generally run between $60,000 and $130,000 a year. The spread comes down to experience, company size, and where you are. A junior person reviewing call samples sits at the low end. A senior officer who can talk to regulators, redesign consent flows, and defend a deposition sits near the top, and is worth every dollar.

Do you need a full-time person? If you're a small affiliate running a couple of offers, probably not yet. You need to understand the rules yourself, which is a good reason to read something like The Pay Per Call Revolution before you scale anything. But once you're a network routing calls from multiple publishers to multiple buyers, the answer flips fast. One bad quarter of unvetted traffic can cost more than a compliance salary for a decade.

So here's the honest framing. A compliance officer is insurance you can talk to. They cost money up front and their whole value shows up as things that didn't happen. No lawsuit. No FTC inquiry. No buyer dropping you because your calls tanked their own audit.

FAQ

Is a compliance officer the same as a lawyer? No. A compliance officer manages ongoing operations, call reviews, consent records, and publisher vetting. A lawyer handles litigation and formal legal opinions. Good compliance officers know when to stop guessing and call the lawyer, which is a skill in itself.

How much of my call volume should get audited? Most teams sample between 1% and 10%. Newer publishers and higher-risk verticals like legal and insurance deserve the higher end. Once a source proves clean over time, you can dial the sampling down, but never to zero.

Can I outsource compliance instead of hiring? Yes, and plenty of smaller networks do through consultants or platform partners. It works fine until your volume or risk gets high enough that you need someone watching daily. The tricky verticals rarely stay simple for long.

What's the single biggest risk a compliance officer prevents? Liability from traffic you didn't generate. Vet every publisher's consent and dialing setup before you route a single call, and keep those records for at least four years.