Skip to main content

Deadline · 1 July 2026 · Netherlands

NL Telecomwet — 1 July 2026.

The Netherlands is the only EU market with a dual forcing function: the updated Telecommunications Act for outbound (1 July) plus EU AI Act Article 50 (2 August). The ACM (Autoriteit Consument & Markt) enforces the Telecomwet's outbound consent and telemarketing rules; the Dutch supervisory authority for EU AI Act Article 50 has not yet been definitively designated. For outbound voice AI in the Netherlands: this affects you.

What changes from 1 July 2026

  • Explicit AI disclosure at the start of outbound calls — “You are speaking with an AI assistant”
  • From 1 July you must be able to demonstrate consent for each outbound call (cookie-style logging is not sufficient)
  • Quiet hours strictly enforced (no AI calls 19:00–08:00 + weekends)
  • DNC (Bel-me-niet-register) check required before every outbound call
  • Tamper-evident proof of disclosure + consent for supervisory requests

What Audact’s NL policy engine is designed to do

  • Pre-call DNC + consent check via API integration with the Bel-me-niet-register
  • Quiet-hours blocking with per-postcode time-zone handling
  • Native Dutch disclosure script, prepared for legal review before rollout
  • A tamper-evident consent proof stamped on every outbound call, so you can demonstrate consent on request
  • Telecomwet-specific evidence chain — designed to support both GDPR and the Telecomwet

Dual coverage — no extra setup

Audact’s NL policy engine is designed to support both the NL Telecomwet (1 July) and EU AI Act Article 50 (2 August). No separate configuration. No bolt-on module. One evidence chain for both regimes.