1. Regulatory focus
In June 2026, Chile’s Subtel tightened the boundary for mass communications using the 600 range. Only automated or large-scale contacts directly tied to a service the user expressly requested or already contracted can use 600. The clarification is broader than a voice rule: it expressly covers verbal, written, pre-recorded, and AI-generated communications, including SMS and MMS. If the main purpose is to promote a new product, upsell an add-on, or contact users without a qualifying request or contractual basis, the outreach belongs in the 809 category instead of a trusted-looking 600 flow.
2. Business impact
The operational impact is that companies can no longer bundle renewal reminders, support callbacks, delivery notices, and cross-sell campaigns into one automated outbound stream under a single trusted identity. Once the primary purpose shifts toward selling an additional or different service, the communication may need to move from 600 to 809 even if it targets an existing customer and comes from the same brand. For CPaaS teams, collections workflows, SMS fallback, robocall programs, and CRM orchestration, this turns message taxonomy, trigger logic, consent records, and numbering allocation into audit items rather than routine routing choices.
3. Operating recommendations
A practical response starts with purpose mapping. Reclassify Chile traffic into requested service notices, contract-performance support, unsolicited marketing, and collections-related exceptions, then bind each template to its legal basis, user action, timestamp, and delivery channel. If one journey mixes OTP, billing, support, plan upgrades, and add-on sales, split it into separate campaigns, number resources, and audit trails. Teams using AI dialing or AI-assisted copy should also add sampling reviews, because the rule explicitly reaches AI-generated communications and a promotional drift inside a 600-class workflow is exactly the kind of misclassification the update is designed to stop.