Lead generation agents
Scalix Guide: Auditable ADAD Express-Consent Capture for Canadian Outbound AI Voice Agents
· 12 min read · Scalix, Calgary
Published by Scalix. For questions or corrections, contact us.
Quick answer
This guide answers a distinct Canadian buyer need: a minimally sufficient, auditable 'express consent' capture and storage flow for outbound AI voice lead‑generation agents that aligns with CRTC ADAD/Unsolicited Telecommunication Rules and OPC/PIPEDA guidance on call recording and biometric voice data. It prescribes a stepwise consent pattern (pre-call gating, recorded opt-in, ADAD identification wording, human-handoff confirmations, explicit biometric consent where voiceprints are derived, CRM audit fields, and immediate revocation handling), a 7-step technical integration map, a hypothetical worked example for vendor evaluation, limitations and a three-item checklist. Scalix offers a no-charge audit to scope gaps (implementation scoping, not legal advice).
Introduction: scope, audience and what this guide delivers
This practical guide gives Canadian buyers a minimally sufficient, auditable express-consent capture flow for outbound AI voice lead-generation agents and the technical integration points a CRM must provide to support CRTC and OPC/PIPEDA review.
Scalix wrote this evaluation guide to help marketing and ops leaders decide whether to build or buy an outbound voice agent and what to request during a Scalix free audit (Scalix provides no-charge scoping, not legal advice).
Assumptions and limits: this is implementation guidance based on public sources checked on 2026-11-11; confirm with legal counsel and re-check regulator pages before launch.
- Primary audience: Canadian SMBs and mid-market product/ops evaluating ADAD or predictive dialer voice agents.
- Goal: produce an auditable consent record linking explicit, contemporaneous acceptance to outreach category, wording and recording/transcript.
- Deliverables: step-by-step consent flow, 7-step technical map, minimal CRM data model, hypothetical example, three-item checklist.
The minimally auditable express-consent flow (step-by-step)
Produce a consent trail that links an explicit, contemporaneous acceptance to the exact outreach category (ADAD vs live/predictive), the wording used, and an immutable recording or transcript. Prefer pre-call recorded opt-in when feasible.
Steps below describe the minimum elements to capture and store to create auditable evidence for both telemarketing rules and privacy guidance around recordings and biometric voice data.
- 1) Pre-call audience gating: filter DNCL and tag list source in CRM before dialing; retain a listVersionID, hash and timestamp for audit.
- 2) Consent source step (preferred): obtain express ADAD consent via recorded web form or IVR opt-in that names caller, phone numbers and purpose, and explicitly states automated/synthesised voice use; store recordingURI and transcriptURI.
- 3) ADAD message opening: start with organisation name and brief purpose; provide an email or postal address and a local or toll-free number; keep contact info valid for 60 days and repeat ID if message >60s.
- 4) Human handoff: when transferring to a live agent, record immediate confirmation with agentID and an audio snippet where the consumer confirms consent or revokes it.
- 5) Biometric voice data: if deriving or storing voiceprints, obtain separate express consent that documents purpose, retention period and access controls; disable voiceprint derivation if consent is missing.
- 6) CRM audit link: store consentId, sourceChannel, exactWordingID, recordingURI, transcriptURI, timestamp, legalBasis, expiry/revocationFlag, listSourceID and auditorURI.
- 7) Revocation and enforcement: implement a realtime revocation API and log any 'remove me' requests immediately with revocationAudioURI and timestamp.
7-step technical integration map (implementation-ready checklist)
Use this 7-step map when scoping a vendor or a Scalix free audit. Each step lists the minimal technical artefact the system must produce or check to create an auditable trail. Design for immutability, exportability and realtime consent checks before any ADAD attempt.
- 1) List ingestion & DNCL check — artefact: listVersionID, source, hash, timestamp, DNCL-compliance flag.
- 2) Consent capture module — artefact: recorded opt-in URI, transcriptURI, consentWordingID, captureMethod (web/IVR), timestamp.
- 3) Dialer config & classification — artefact: dialerMode (ADAD/predictive/live), campaignID, messageTemplateID, recordedMessageURI.
- 4) ADAD message runtime guard — artefact: runtime injection of valid contact info and enforcement of 60-day validity for that contact info.
- 5) Handoff recorder & confirmation — artefact: handoffEvent with agentID, confirmationAudioURI and confirmationTranscriptURI.
- 6) Biometric processing guard — artefact: biometricConsentID, documented purpose, retentionPeriod, storageLocation and accessControls; block voiceprint derivation if consentMissing.
- 7) CRM audit & revocation API — artefact: consentRecord (consentId, wordingID, recordingURI, timestamp, revocationFlag), exportable auditBundle (JSON + recordingURIs) and realtime revocation endpoint.
Minimal CRM data model and immutable audit log fields
A CRM that supports ADAD compliance must store consent as a first-class, immutable record and link it to calls, list versions and campaign artefacts so an auditor can reconstruct events.
- Consent record fields: consentId, userId, phoneNumber, sourceChannel (web/IVR/agent), exactWordingID, recordingURI, transcriptURI, timestamp, legalBasis (express/EBR), expiryDate, revocationFlag, listSourceID.
- Campaign/call link fields: campaignID, dialerMode (ADAD/predictive/live), messageTemplateID, callAttemptID, callStartTimestamp, callEndTimestamp, agentID (if human).
- Audit log requirements: immutable append-only store, exportable auditBundle (JSON + recordingURIs), retentionPolicy reference, auditorURI and chain-of-custody metadata.
Hypothetical worked example: a Canadian SMB evaluating vendors
This concise, hypothetical example shows how the flow and technical map combine. Assumptions are illustrative and not Scalix results.
- Scenario: a mid-sized Alberta retailer wants to trial an outbound AI lead-generation campaign using a synthesised voice for appointment reminders and product offers and needs auditable ADAD consent handling.
- Step A — Pre-call: retailer imports a marketing list; CRM tags listSource='newsletter-signup-2026' and runs DNCL check; listVersionID stored.
- Step B — Pre-consent capture: retailer sends a recorded IVR opt-in invite and a web form stating organisation name, phone numbers, purpose and that calls may use an automated/synthesised voice; opt-in recorded and stored (recordingURI + transcriptURI).
- Step C — Dialer selection: retailer configures ADAD mode for non-EBR prospects and predictive/live for EBR contacts; messageTemplateID references the approved disclosure text previously recorded.
- Step D — Call event: ADAD message opens with required ID and contact info kept valid for 60 days; system logs callAttemptID and template used.
- Step E — Handoff: if consumer requests more info and transfers to agent, system records agentID and immediate consent confirmation audio; CRM links handoffEvent to consentId.
- Step F — Biometric decision: retailer disables voiceprint extraction unless separate biometricConsentID present; if present, biometricConsent fields are stored and accessible via auditorURI.
- Step G — Revocation: spoken 'remove me' on call triggers realtime revocation API; CRM sets revocationFlag and logs timestamp and revocationAudioURI.
Three-item buyer checklist, limitations and next steps (Scalix free audit)
Use this short checklist to prioritise during vendor evaluation or a Scalix free audit. The checklist condenses key, auditable requirements buyers must verify.
Limitations: this guide is implementation guidance, not legal advice. Sources were checked on 2026-11-11; regulatory guidance can change. Scalix can run a free audit to map your systems to the checklist and produce a deployment plan (no obligation).
- 1) Confirm dialer class & pre-consent: document whether outreach will use ADAD (automated/synthesised) or predictive/live dialing and capture express opt-in (recordingURI + transcriptURI) before ADAD use where feasible.
- 2) Mandate auditable records: require immutable consent records in CRM (consentId, exact wordingID, recordingURI, timestamp, listVersionID) and a realtime revocation API that vendors must support.
- 3) Treat voiceprints as biometrics: if any voiceprint/biometric extraction will occur, require separate explicit biometric consent, documented purpose, retention, and vendor access controls per OPC guidance.
Common questions
- Does the CRTC treat AI-synthesised voice messages as ADAD requiring express consent?
- The CRTC treats pre-recorded or otherwise automated messages used for telemarketing under ADAD rules; express consent is typically required for telemarketing ADAD outreach. Buyers should verify campaign classification with legal counsel. https://crtc.gc.ca/eng/phone/telemarketing/tobligations/rules-regles.htm
- What identification elements must appear at the start of an ADAD message and how long must contact info remain valid?
- ADAD messages must begin with clear identification (organisation name and purpose) and provide an email or postal address plus a local or toll-free number. The contact information should remain valid for 60 days and the ID should be repeated if the message exceeds 60 seconds. https://crtc.gc.ca/eng/phone/rce-vcr/guidecan.htm?utm_source=openai
- When does voice data become 'biometric/voiceprint' under OPC guidance and require separate consent?
- Per the OPC update (Oct 8, 2026), voice-derived identifiers used for biometric recognition (voiceprints) are sensitive; extracting or storing them requires explicit, separate consent documenting purpose and retention, beyond ordinary call-recording notices. https://www.priv.gc.ca/en/opc-news/news-and-announcements/2026/nr-c_261008?utm_source=openai
- Can an existing business relationship (EBR) replace express ADAD consent for automated/synthesised outbound lead-generation?
- EBR can affect outreach obligations in certain contexts, but ADAD telemarketing that uses automated or pre-recorded messages generally requires express consent unless a narrow EBR exemption applies. Consult the CRTC guidance and legal counsel to determine applicability to your campaign. https://crtc.gc.ca/eng/archive/2007/dt2007-48.htm?utm_source=openai
Find your biggest time-saver
Book a free AI audit, or call our 24-hour line at (825) 782-4956.