Skip to content
AI Voice Agents
AI Voice Agents10 min read0 views

Canada CRTC and CASL: AI Voice Calls and Consent in 2026

Why CASL applies to AI voice calls the same way it applies to human calls, what express versus implied consent looks like for outbound, and how to keep penalties below the CAD $10M corporate cap.

Canada's Anti-Spam Legislation does not care whether the voice on the other end is human or generated. If your AI agent dials a Canadian number with a commercial purpose, you need consent on file. The CRTC's 2025-2026 enforcement posture has visibly tightened.

What the rule says

flowchart LR
  UA[SIP UA] -- REGISTER --> Reg[Registrar]
  UA -- INVITE --> Proxy[SIP Proxy]
  Proxy --> Dispatcher[Kamailio dispatcher]
  Dispatcher --> Worker1[FreeSWITCH worker]
  Dispatcher --> Worker2[FreeSWITCH worker]
  Worker1 --> AI[(AI agent)]
  Worker2 --> AI
CallSphere reference architecture

Canada's Anti-Spam Legislation (CASL, S.C. 2010, c. 23) and the parallel Unsolicited Telecommunications Rules (UTRs) under the Telecommunications Act regulate commercial communication. CASL primarily governs commercial electronic messages (CEMs) including SMS and email; the UTRs (administered by the CRTC) govern voice telemarketing, including consent, identification, and the National Do Not Call List (DNCL). The CRTC has indicated CASL covers voice calls with commercial intent, and AI agents are not exempt. Express consent must be specific, documented, and revocable; implied consent applies only in limited cases (existing business relationship within 24 months, conspicuous publication of the number for business). Administrative monetary penalties (AMPs) reach CAD $10M per corporate violation; individuals up to $1M.

What it means for AI voice agent operators

Three pieces matter for AI voice agents calling Canadian numbers:

First, scrub against the National Do Not Call List (DNCL) before every campaign and at least every 31 days. The DNCL has its own subscription model; you must register as a telemarketer and pay the per-area-code or full-list fee. Calling a DNCL-registered number without an exemption is a per-call AMP exposure.

Hear it before you finish reading

Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.

Try Live Demo →

Second, identification and curfew. UTRs require the caller to identify the individual or organization on whose behalf they are calling, provide a phone number where they can be reached, and call only between 9am and 9:30pm weekdays / 10am-6pm weekends, in the called party's local time.

Third, AI disclosure. CASL itself does not yet mandate AI disclosure verbally on the call, but the CRTC is reviewing CASL for AI-aware updates and the practical, defensible posture in 2026 is to disclose. Disclosure also helps with the consent record: a recorded "this is an automated assistant from Acme; we have your consent on file from {date}" stitches the consent ledger to the call.

How CallSphere stays compliant

For Canadian deployments, CallSphere routes through Twilio Canada infrastructure with Canadian DIDs assigned through Twilio Trust Hub, signing under the Canadian SHAKEN deployment. Sales Calling AI on Canadian campaigns runs DNCL scrubbing through PossibleNOW or an equivalent every 31 days and on every list refresh. The opening line on outbound is: "Hi, this is the AI assistant for {company}; we have your contact consent on file. Is now a good time?" Any verbal "stop", "remove", or "not interested" triggers immediate suppression. Healthcare AI Canadian instances apply PIPEDA-aligned consent in addition to CASL. With 6 verticals, 50+ businesses, 4.8/5 rating, and a 14-day trial, CallSphere ships Canadian compliance presets for the Real Estate, Salon, and Healthcare verticals.

Compliance checklist

  1. Register as a telemarketer with the CRTC's National DNCL operator.
  2. Subscribe to the DNCL by area code or full list before any outbound campaign.
  3. Scrub at least every 31 days; better, scrub on each list refresh.
  4. Capture express consent for marketing AI calls; document in writing or recorded verbal.
  5. Identify the caller, the business, and a callback number at the start of every outbound call.
  6. Disclose AI use clearly; "this is an automated assistant from {company}".
  7. Honor the call curfew: 9am-9:30pm M-F, 10am-6pm weekends, local time.
  8. Honor verbal opt-outs immediately; propagate to a unified suppression list within 14 days max.
  9. Retain consent records for at least three years.
  10. Sign DPAs with sub-processors and ensure cross-border transfers comply with PIPEDA and provincial laws (Quebec Law 25, Alberta PIPA, BC PIPA).
  11. Monitor CRTC enforcement bulletins and the CRTC's CASL FAQ revisions quarterly.

FAQ

Is implied consent enough for an AI cold call? Implied consent (existing relationship, conspicuous publication) is risky for AI. Get express consent or rely only on existing-customer outreach.

Still reading? Stop comparing — try CallSphere live.

CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.

Does the National DNCL apply to B2B? The DNCL covers consumer calls; pure B2B telemarketing has fewer DNCL constraints but still must comply with UTRs (identification, curfew, opt-out).

What about Quebec's Law 25? Law 25 (formerly Bill 64) imposes additional privacy requirements on Quebec-resident data including AI-related transparency. Treat it as a stricter overlay.

How big are the fines in practice? The CRTC has imposed multi-million-dollar AMPs on telemarketers. The deterrent is real; even one DNCL test purchase by an investigator can trigger a six-figure penalty.

Is recording legal in Canada? Canada is a one-party consent jurisdiction federally for criminal purposes (Criminal Code s. 184), but PIPEDA/Law 25 require notice and a justifiable purpose. Always disclose at call start.

Sources

Start a 14-day trial, see pricing, or visit /about.

Share

Try CallSphere AI Voice Agents

See how AI voice agents work for your industry. Live demo available -- no signup required.

Related Articles You May Like

AI Voice Agents

MOS Call Quality Scoring for AI Voice Operations in 2026: Beyond 4.2

MOS 4.3+ is the band where AI voice feels human. Drop below 3.6 and conversations break. Here is how to measure, improve, and alert on MOS in production AI voice using G.711, Opus, and the underlying packet loss / jitter / latency math.

AI Voice Agents

Voice Cloning Consent and HIPAA: When Synthetic Patient Voice Is OK

Cloning a clinician's voice for an AI agent is one design decision. Cloning a patient's voice is another regulatory universe. Here is how HIPAA, state biometric law, and the new federal voice statutes interact in 2026.

Healthcare

Clinical Trials Recruitment with AI Voice Agents: Screening, Consent Pre-Education, and Retention Calls

Clinical research organizations use AI voice agents to pre-screen trial candidates, run consent education calls, and maintain retention across long study arms.

AI Strategy

State Data Residency for AI Voice in Healthcare — Texas, Nevada, Colorado in 2026

Texas SB 1188 requires US-resident EHRs from January 1, 2026; Nevada's consumer-health-data law constrains health data; Colorado AI Act takes effect June 30, 2026. AI voice agents must architect for state-by-state data localization.

AI Engineering

SIP Debugging with sngrep and Wireshark for AI Voice Calls in 2026: The Hands-On Playbook

When your AI voice agent gets one-way audio, missed DTMF, or codec mismatch, sngrep and Wireshark are still the fastest path to root cause in 2026. Here is the playbook.

AI Infrastructure

RTP Transcoding Cost for AI Voice in 2026: Why Edge Placement Beats Central GPU

Transcoding RTP to WebSocket is more CPU-intensive than people expect. For AI voice in 2026, where you place the transcode (edge near the carrier vs central near the model) decides your cost-per-minute.