Do DNC Rules Apply to Service and Appointment Calls?
DNC LATAM · Compliance guides
Sometimes — a service reminder, appointment confirmation, or recall notice into Mexico or Argentina can sit outside REPEP’s and the Registro Nacional No Llame’s scope, but only if the call stays purely transactional from open to close. The moment it adds a sales pitch, a renewal offer, or an upsell, it stops being a service call for compliance purposes and becomes the kind of commercial contact both registries are built to screen. Auto dealerships, home services companies, and insurers running outbound “just checking in” calls are the teams most likely to get this line wrong, usually by assuming the whole call category is exempt rather than checking what each individual call actually says.
The test is purpose, not department or label
Neither Mexico’s REPEP (run by PROFECO) nor Argentina’s Registro Nacional No Llame, created by Law 26.951 and administered by AAIP, carves out a blanket exemption for calls labeled “service” or “account management.” Both registries already draw this exact line for messages: our posts on SMS, WhatsApp, and RCS business messages all cover the same OTP-and-transactional carve-out: a delivery notification, appointment confirmation, or account-servicing message stays outside scope because of what it says, not because of the app or protocol it travels over. A call runs on the identical logic. A dealership calling to confirm a scheduled oil change, a home-services company calling to confirm a technician’s arrival window, or an insurer calling to confirm a claim document was received are all account-servicing contact about something the customer already asked for or already has — not an unsolicited commercial offer to a number that may be registered.
That is a narrower exemption than it sounds, and it is easy to lose by the end of the call. We covered the same purpose-over-label reasoning for collections calls that assume “not marketing” clears them automatically — it doesn’t, and the same scrutiny applies in reverse here. A call that opens as a service reminder and closes with “while I have you, we have a loyalty discount on your next service” has added a commercial element partway through. Both registries look at what the call actually contained, not what the agent’s talk track was supposed to be.
Where this breaks down in practice
The failure mode isn’t usually a dealership or home-services team deciding to ignore the registries outright — it’s treating an entire call type as pre-cleared and never checking what individual agents actually say once they’re live on a call:
- Script drift. A service-reminder script that starts transactional gets a line added by a sales manager wanting to capture more revenue per call — “ask if they want to hear about our current offers” — and the whole campaign quietly becomes commercial without anyone updating its compliance classification.
- Mixed-purpose campaigns. A recall notice that also promotes an extended warranty, or a claim-status call that pivots into a renewal pitch, is a single call serving two purposes — and the commercial half is what the registry review will weigh.
- List provenance gets conflated with call purpose. A number pulled from a service history or policy file is not automatically cleared just because the relationship is transactional in nature; what matters is whether this specific call stays transactional, not where the number came from. Win-back and reactivation campaigns run into the mirror-image version of this mistake — assuming a past relationship clears a call that is, in substance, commercial.
For verticals that run high call volumes of this kind — see DNC for home services, DNC for insurance outbound, and multi-country DNC API for dealers — the safer operating posture is to keep the transactional and commercial sides of the business on separate scripts and separate campaigns, rather than trusting a single agent, mid-call, to hold the line consistently across hundreds of dials a day.
The opt-out standard doesn’t bend for “but it was a service call”
Whatever the commercial-scope determination turns out to be, it has no bearing on what happens when a customer says “stop calling me” during a service call. That instruction gets honored immediately, exactly as covered in training agents to handle a live DNC opt-out request — a customer doesn’t have to frame their opt-out as “I don’t want marketing calls” for it to count, and an agent who reasons “this is just a service account, the opt-out is about marketing” is drawing a distinction the registry doesn’t recognize. That request still belongs in the same internal Do Not Call list every other opt-out feeds into, not a service-desk-only suppression file the rest of the dialer never checks.
What this looks like operationally
For a US-based outbound operation running service, appointment, or recall calls into Mexico or Argentina, the practical standard is narrower than “service calls are exempt” and broader than “scrub everything the same way”:
- Write transactional scripts to stay transactional, with no bolt-on sales line at the end. If a service call needs to also sell something, treat the whole campaign as commercial and scrub it against the current REPEP or No Llame release before dialing.
- Don’t let list source stand in for call purpose. A service-history or policy file doesn’t pre-clear a call; what the agent says on that specific call does.
- Audit scripts periodically, not just at launch, since script drift toward “while I have you” upsells is the most common way a transactional campaign quietly becomes a commercial one.
- Route every opt-out into one suppression list, checked at the same pre-dial gate described in DNC API integration for dialers and CRMs, regardless of which desk the call came from.
- Keep the scope determination with counsel. Whether a specific script counts as transactional is a judgment call for someone familiar with Mexican and Argentine commercial-contact rules; DNC LATAM runs the official registry check and returns a dated screening record, it doesn’t make that call for you.
The practical takeaway
A purely transactional service or appointment call can sit outside REPEP’s and No Llame’s reach — the same purpose-based line both registries already draw for OTPs and account-servicing messages extends cleanly to calls. The risk isn’t the exemption itself; it’s assuming an entire call category is covered by it and never checking what agents actually say once a script has been live for a few months. Authorities can sanction per call, so the safer default for any campaign that might drift commercial is to scrub it the way a marketing campaign would, and to treat the opt-out standard as constant no matter what the call was supposed to be about — the same contact center compliance baseline every other calling program runs on.