Calling Hours Rules for Telemarketing in Mexico & Argentina
DNC LATAM · Compliance guides
Calling-hours rules for telemarketing into Mexico and Argentina come down to one practical standard: outbound calls should be scheduled around the recipient’s local daytime hours, not the agent’s, and layered on top of — never instead of — a Do Not Call scrub. Neither country publishes a single, centralized “calling window” statute the way the US Telemarketing Sales Rule does, which is exactly why outbound teams expanding into Mexico or Argentina tend to underestimate the contact-rules side of compliance: there’s no one clock to set, so it gets skipped.
Why “daytime hours” isn’t one global rule
US compliance teams are used to a specific, well-known reference point: the Telemarketing Sales Rule sets a defined daytime calling window in the recipient’s local time zone, enforced by the FTC and FCC alongside the National DNC Registry. That single rule covers every US number, regardless of where the calling agent sits.
Mexico and Argentina don’t hand outbound teams an equivalent single number to program into a dialer. Both countries regulate telemarketing contact through their broader consumer-protection frameworks — the same authorities that run each country’s Do Not Call registry — rather than through one standalone calling-hours statute. That does not mean anything goes. It means the obligation to contact consumers at a reasonable hour sits inside the same general consumer-protection duty that requires checking the registry in the first place, and regulators can act on unreasonable contact patterns the same way they act on calling numbers that were never scrubbed. Our call center compliance guide covers where calling windows sit alongside scrubbing, consent and audit trail as the four pillars of outbound compliance.
The practical rule for Mexico
Mexico’s official Do Not Call registry — REPEP — is the foundational check before any campaign touches a Mexican number, refreshed every 15 days and distributed zone by zone, as we cover in our Mexico Do Not Call guide. Calling-hours expectations in Mexico sit under the same general consumer-protection duty to contact people reasonably: campaigns scheduled around normal daytime hours in the recipient’s local time zone, rather than whatever hours suit an offshore dialer, are the safer default. A campaign that scrubs its list perfectly against REPEP but dials Mexican numbers at hours no reasonable business would call has simply moved its exposure from one rule to another.
Mexico spans multiple time zones — from Baja California in the far northwest to Quintana Roo in the southeast — so a national campaign dialed on a single schedule anchored to one zone will hit some regions during business hours and others well outside them. Segmenting call lists by zone, the same way REPEP itself distributes registry data zone by zone, keeps a national campaign from silently drifting into off-hours calling for whichever region is furthest from the scheduling assumption.
The practical rule for Argentina
Argentina’s Registro Nacional No Llame, created under Law 26.951, is the mandatory check before dialing Argentine numbers — see our Argentina Do Not Call guide for how the registry and its authorized-user requirement work. As in Mexico, Argentina does not publish a separate calling-hours statute distinct from its consumer-protection and Do Not Call framework; the expectation is the same general standard of contacting consumers at a reasonable hour, and authorities can weigh a pattern of unreasonable contact into a sanction alongside a registry violation, without that pattern needing a rule of its own.
Argentina runs a single time zone nationwide, which removes the zone-segmentation problem Mexico presents — but it doesn’t remove the underlying obligation to schedule around the recipient’s day, not a call center’s shift pattern on another continent.
Disclosure still travels with every call
Calling-hours discipline is only half of contact rules. Every call also needs to identify the caller, state the purpose of the contact and give a clear way to opt out — and those disclosures should be scripted per country rather than reused verbatim across markets, since consumer-protection expectations aren’t identical between the US, Mexico and Argentina. Our DNC compliance checklist for nearshore call centers breaks this out as a standing checklist item alongside registry scrubs and consent logging, precisely because nearshore floors running mixed-country campaigns are the most likely to reuse one script across destinations by mistake.
Building calling windows into an outbound program
A few structural habits cover most of the exposure:
- Schedule by destination time zone, not agent time zone. A nearshore floor in Buenos Aires or Mexico City dialing US numbers, or a US-based team dialing into Mexico or Argentina, should route each list through a schedule keyed to where the number rings, not where the seat sits.
- Segment Mexican campaigns by zone. With multiple time zones inside one country, a single national schedule almost guarantees off-hours calling somewhere.
- Treat calling windows as part of the same compliance record as the scrub. A dated DNC scrub certificate proves the list was clean; logging the campaign’s calling-hours policy alongside it gives you both halves of the record a client or regulator might ask for. Our guide to TCPA vs. Mexico and Argentina DNC rules covers why a US-focused compliance stack — hours included — doesn’t automatically carry over once a campaign crosses into either country.
- Don’t let an automated dialer outrun the schedule. Predictive and auto-dialers can start a shift’s calls before checking whether the destination zone has moved into an acceptable window; the scheduling logic needs to gate on the number’s zone, not just the campaign’s start time.
None of this replaces the registry check itself — a call placed at a reasonable hour to a registered number is still a violation. Calling-hours discipline and DNC scrubbing are two separate controls that both have to hold for every call. DNC LATAM handles the country-specific registry side — including current REPEP and Registro No Llame data, scrubbed on demand with dated certificates — so outbound teams can focus their own process on scheduling and disclosure rather than chasing registry access in local government systems.