Who Is Liable for a DNC Violation: Brand or BPO?
DNC LATAM · Compliance guides
Compliance attaches to whichever party actually places the call, but that doesn’t settle liability on its own: the brand still owns the campaign and still gets named first in a client audit or a regulator’s complaint file, regardless of which company’s agent dialed the number. In a BPO relationship calling into Mexico, Argentina, or Colombia, the only thing that actually decides who answers for a violation is what the contract says about who runs the scrub, who keeps the record, and who produces it on request. Silence on that point doesn’t split the risk evenly — it just means nobody finds out who owns it until a complaint forces the question.
Why “compliance attaches to the dialer” isn’t the whole answer
It’s tempting to treat DNC liability like a simple rule: whoever places the call is responsible for checking the number first, so the BPO is on the hook. That’s true as far as it goes, but it misses how these relationships actually get audited. A US brand running a Mexico or Argentina expansion through a nearshore floor doesn’t get to point a regulator or its own compliance team at the BPO and walk away — the brand’s name is on the product being sold, the brand signed off on the campaign, and the brand is the one a consumer complaint or a client audit names first. The floor placed the call. The brand owns the logo. Both facts are true at once, which is exactly why an MSA that’s silent on who scrubs leaves a gap that shows up at the worst possible time: during someone else’s review of a specific, already-dialed campaign.
This is a different question from the operational one covered in our DNC compliance checklist for nearshore call centers, which walks through what a floor needs to check before every campaign. That checklist assumes someone has already agreed to run it. This post is about the contract decision that comes before the checklist: which party that someone actually is.
Put it in the contract, not in a general compliance clause
“Vendor will comply with applicable DNC laws” shows up in a lot of master service agreements, and it resolves nothing. It doesn’t say whether last cycle’s REPEP file is acceptable for this campaign, whether Argentina needs a current AAIP consult before a specific list goes live, or who is holding the screening record when a client’s audit desk asks for it six months later. A contract that actually protects both sides names, before the first +52 or +54 campaign dials a single number:
- Which party runs the official registry check — the BPO, the client, or a shared vendor both sides can point to.
- Which registries are in scope for this engagement: REPEP / PROFECO for Mexico, No Llame / AAIP for Argentina, RNE / CRC for Colombia — not a generic reference to “DNC compliance” that doesn’t say which country’s registry applies.
- Who retains the screening record, for how long, and who has the right to export or request a copy of it.
- What happens when one program spans two destination countries on the same list, since a single campaign calling both Mexico and Argentina numbers needs both registries checked, not one.
None of this needs to be adversarial. The point of naming it explicitly is that it’s cheaper to agree on paper, before any numbers are dialed, than to reconstruct who was supposed to be doing what after a complaint has already landed.
What an auditor actually asks for, and why it matters here
When a brand’s compliance desk — or a regulator responding to a consumer complaint — opens a review, it doesn’t ask for a general assurance that the vendor relationship is compliant. It asks for a dated, campaign-specific screening record: which registry and release the list was checked against, on what date, and how many numbers came back prohibited, safe, or invalid. A BPO that can produce that record for the exact campaign under review has a very different conversation than one that can only say “we scrub our lists” without a specific artifact to show for it.
This is where the liability question actually gets decided in practice, not in the abstract. If the contract named the BPO as the party running the check, the BPO needs to be the one who can produce that record on short notice — and the brand needs confirmation, in writing, that the BPO retains it long enough to cover the brand’s own audit window. If the contract named the client brand, the brand needs to be pulling and storing that record itself rather than trusting a verbal assurance from the floor that “it’s handled.” Either arrangement works. What doesn’t work is neither side being sure which one is true until the record gets requested and nobody has it.
Multi-client floors raise the same question per account
A BPO running Client A’s US book and Client B’s Mexico expansion on adjacent teams can’t resolve liability once for the whole floor — the contract question has to be answered per client relationship, because each client’s MSA may assign the scrub differently. One brand might buy and hold the DNC LATAM access itself and hand the BPO a clean, pre-scrubbed list; another might require the BPO to run the check and simply ask for the screening record on demand. Both are legitimate setups. The failure mode is a floor that assumes the arrangement is the same across every client because that’s how it worked for the last one — and discovers otherwise when the client that didn’t buy its own access gets audited and has nothing to produce.
The practical takeaway
Liability for a DNC violation in a BPO relationship isn’t split evenly by default, and it isn’t automatically the dialer’s problem either — it’s whatever the contract says, and the gap only shows up when the contract didn’t say anything. Before a campaign into Mexico, Argentina, or Colombia launches, both sides should be able to answer, in one sentence: who runs the official check, who keeps the record, and who produces it if asked. For the broader floor-level controls that sit underneath that contract decision — calling hours, consent logs, opt-out handling — see contact center compliance and the nearshore compliance checklist. For the commercial relationship itself, including when the BPO versus the client should be the one holding registry access, see DNC for BPOs running Mexico and Argentina.