AI Voice in Canada 2026: CRTC, LERG Routing, and the June Call-Traceback Rule

Canada looks like an extension of the US numbering plan, and operationally it is, but the CRTC enforces a parallel set of rules: the Unsolicited Telecommunications Rules, the National DNCL, CASL on the messaging side, and from 25 June 2026 a mandatory call-traceback obligation on every voice TSP. AI voice agents that can't answer a traceback in 24 hours will lose carrier contracts.

How telephony works there

Canada uses the North American Numbering Plan (NANP) with country code +1, identical area-code structure to the US, and shared LERG (Local Exchange Routing Guide) data. NPA-NXX assignments are administered by the Canadian Numbering Administrator (CNA) under CRTC oversight; iconectiv operates the LERG. CRTC also runs Local Number Portability and recently mandated all voice TSPs to participate in call traceback as a condition of providing service.

Major carriers (Bell, Rogers, Telus, Videotron) interconnect via class-4 IP softswitches, and CLEC/VoIP providers like Twilio Canada plug in through wholesale agreements. Twilio offers Canadian local DIDs, toll-free (8YY shared with the US), and TF Canada-only ranges; the Toronto edge gives sub-50 ms RTT to most Canadian users. STIR/SHAKEN has been mandatory for IP-originated traffic since 30 November 2021 (Compliance & Enforcement Telecom Decision 2019-402, updated 2021-123).

Regulatory landscape

The CRTC's Unsolicited Telecommunications Rules cover four categories: telemarketing rules, automatic dialling-announcing devices (ADAD) rules, fax rules, and the National DNCL. AI voice agents are explicitly classified as ADADs when they play a recorded or synthesised message. ADAD calls require either prior express consent or a pre-existing business relationship, must identify the caller in the first sentence, must include a real callback number, and cannot be made before 9 am or after 9:30 pm local time. The DNCL must be scrubbed within 31 days of the call, and operator registration with the National DNCL is mandatory.

CASL (Canada's Anti-Spam Legislation) governs SMS and email follow-ups; the maximum fine is CAD 10 million per business per violation. From 25 June 2026, every TSP, including resellers, must participate in the call-traceback process within 24 hours of an inbound traceback request, and CISC has until 28 September 2026 to report on automation.

CallSphere implementation

Explore a live demo and compare current plans to find the right fit for your business.

Build and launch steps

flowchart LR
 A[Twilio CA subaccount + Toronto edge] --> B[Provision NPA local DID or 8YY TF]
 B --> C[STIR/SHAKEN attestation A via Twilio]
 C --> D[Register operator on National DNCL]
 D --> E[CASL consent + ADAD identity disclosure]
 E --> F[Traceback automation within 24h]

1. Create a Twilio Canadian subaccount and select the Toronto media edge.
2. Provision a local NPA DID (416, 604, 514, 403) or an 8YY toll-free, with STIR/SHAKEN attestation A.
3. Register as a telemarketer on the National DNCL and set up daily list-scrub.
4. Capture CASL-grade express consent for outbound campaigns; store consent record for at least 3 years.
5. Configure the AI agent to identify itself in the first sentence and offer a 9-am-9:30-pm calling window.
6. Wire the CallSphere traceback API to respond to inbound CRTC traceback requests in under 24 hours.

FAQ

Are AI voice calls legal in Canada? Yes, with consent, ADAD identity disclosure, DNCL scrub, and the 9 am to 9:30 pm window.

What changes on 25 June 2026? Every voice TSP, including resellers, must participate in CRTC call traceback as a condition of providing service. Late or missing responses can put the licence at risk.

Do I need a Canadian entity to get a Canadian number? No, Twilio Canada DIDs can be provisioned on a US Twilio account, but Bell-A and Rogers-A wholesale routes prefer a verified Canadian operating address for trust scoring.

How does the National DNCL differ from the US one? The CRTC operates a separate national list at LNNTE-DNCL.gc.ca; you must subscribe and scrub even if you've already scrubbed the US DNC.

Sources

• CRTC: Unsolicited Telecommunications Rules
• CRTC: Compliance and Enforcement Decision 2026-52 (call traceback)
• National DNCL Operator Registration
• CASL (Canada's Anti-Spam Legislation)

Explore a live demo and compare current plans to find the right fit for your business.

AI Voice in Canada 2026: CRTC, LERG Routing, and the June Call-Traceback Rule: production view

AI Voice in Canada 2026: CRTC, LERG Routing, and the June Call-Traceback Rule sounds like a single decision, but in production it splits into eval design, prompt cost, and observability. The deeper you push toward live traffic, the more those three pull against each other — better evals catch silent failures, prompt cost limits how often you can re-run them, and weak observability hides which retries are actually saving conversations versus burning latency budget.

Serving stack tradeoffs

The big fork is managed (OpenAI Realtime, ElevenLabs Conversational AI) versus self-hosted on GPUs you operate. Managed wins on cold-start, model freshness, and zero-ops; self-hosted wins on unit economics past a certain conversation volume and on data residency for regulated verticals. CallSphere runs hybrid: Realtime for live calls, self-hosted Whisper + a hosted LLM for async, both routed through a Go gateway that enforces per-tenant rate limits.

Latency budgets are non-negotiable on voice. End-to-end target is sub-800ms ASR-to-first-token and sub-1.4s first-audio-out; anything beyond that and turn-taking feels stilted. GPU residency in the same region as your TURN servers matters more than choosing a slightly bigger model.

Observability is the unglamorous backbone — every conversation produces logs, traces, sentiment scoring, and cost attribution piped to a per-tenant dashboard. HIPAA aligned isolation keeps healthcare traffic separated from salon traffic at the storage layer, not just the API.

FAQ

What's the right way to scope the proof-of-concept? CallSphere runs 37 production agents and 90+ function tools across 115+ database tables in 6 verticals, so most workflows you'd want already have a template. For a topic like "AI Voice in Canada 2026: CRTC, LERG Routing, and the June Call-Traceback Rule", that means you're not starting from scratch — you're configuring an agent template that's already been hardened across thousands of conversations.

How do you handle compliance and data isolation? Day one is integration mapping (scheduler, CRM, messaging) and prompt tuning against your top 20 real call transcripts. Day two through five is shadow-mode running, where the agent transcribes and recommends but a human still answers, so you can compare side-by-side. Go-live is the moment your eval pass-rate clears your internal bar.

When does it make sense to switch from a managed model to a self-hosted one? The honest answer: it scales until your tool catalog gets stale. The agent is only as good as the integrations it can actually call, so the operational discipline is keeping schemas, webhooks, and fallback paths green. The platform handles the rest — observability, retries, multi-region routing — without your team owning the GPU layer.

Talk to us

Explore a live demo and compare current plans to find the right fit for your business.