Lead generation agents

Scalix research brief — Minimal auditable consent receipt & evidence-export for Canadian ADAD AI voice lead-generation agents

· 6 min read · Scalix, Calgary

Published by Scalix. For questions or corrections, contact us.

Quick answer

Canadian buyers of outbound AI voice lead-generation agents (ADAD/predictive dialing) should require a narrowly prescriptive, machine-readable consent receipt (Kantara/ISO fields) plus a tamper-evident evidence-export bundle (signed consent token, call audio + transcript with cryptographic hashes, RAG retrieval log, revocation record). This brief maps candidate Kantara/ISO fields to ADAD disclosures, supplies a three-item checklist and contractual acceptance tests, proposes a falsifiable experiment that tracks accepted Scalix free audit enquiries, gives a hypothetical end-to-end example, and lists limitations and legal checks. Exact primary sources are included for procurement and legal review.

Distinct unanswered buyer question

Unanswered buyer question (distinct): What is the minimum, ISO/Kantara-aligned, machine-readable consent receipt plus tamper-evident evidence-export bundle Canadian buyers should require from vendors of ADAD/predictive-dial outbound AI voice lead-generation agents that (A) use voice biometrics or (B) rely on RAG retrieval during calls, so buyers can prove auditable consent and retrieval decisions under CRTC UTR and OPC/PIPEDA guidance?

    Why this matters to Scalix buyers

    Buyers must combine telecom compliance (CRTC ADAD/UTR) with privacy expectations (PIPEDA/OPC). Public guidance requires express consent for biometric voiceprints but does not mandate a machine-readable receipt or a tamper-evident export format, creating a procurement gap.

    Scalix can help buyers operationalise minimal evidence requirements and acceptance tests so procurement and privacy teams receive auditable artifacts they can use in contract enforcement and vendor selection.

    • This brief targets procurement-ready evidence items (signed consent token, audio/transcript hashes, RAG logs, revocation tokens) a buyer can request in an RFP or during a Scalix free audit.

    Actionable next steps for buyer evaluation (three-step checklist and how Scalix can help)

    Use the three-step buyer checklist below as minimum pre-deployment acceptance tests. Ask vendors to deliver a signed evidence-export bundle for a representative call and request a Scalix free audit to validate the artifacts.

    Scalix will validate cryptographic signatures, artifact hashes, CRM linkage to consentReceiptID and RAG retrieval-log completeness, then produce a one-page buyer-ready acceptance summary with recommended contractual clauses and remediation steps.

    • Three-step buyer checklist: 1) Obtain a signed evidence-export bundle for a sample call (consent receipt JSON signed as JWS, raw audio, transcript, artifact hashes). 2) Verify signatures and that audio/transcript hashes match the values recorded in the receipt.
    • Scalix free audit scope (example): signature verification, SHA‑256 hash checks, CRM record linkage verification, RAG retrieval log completeness test, revocation flow test and a one-page audit summary.
    • Require SLA and key-rotation disclosure, and include schema versioning in contracts (Kantara/ISO version references).

      Quick reference — minimal fields to require (technical)

      Minimum fields buyers should require in the consent receipt and evidence-export index so an auditor can validate integrity and linkage to call artifacts.

      • consentReceiptID (UUID), consentTimestamp (ISO‑8601), jurisdiction ('CA'), collectionMethod (e.g., 'ADAD-voice: spoken-affirmation').
      • controllerIdentity (legal entity), purpose(s), biometricProcessingFlag (true/false), policyURL, retentionPeriod.
      • signedConsentToken (JWS) with signatureKeyID and signatureAlgorithm metadata.
      • callAudioFile ID/path + transcriptFile ID/path and SHA‑256 hashes recorded in the receipt.
      • RAG retrieval log entries: retrievalID, timestamp, queryText, documentID/hash, linked consentReceiptID.
      • revocationTimestamp, signedRevocationToken and deletion/retention audit events with actor IDs.

      Hypothetical worked example — minimal end-to-end consent capture

      A compact, hypothetical example buyers can use as an RFP test case. Timings and identifiers are illustrative only; legal review is required for compliance checks.

      • 1) Pre-call: Vendor registers campaignID and caller number; record controllerIdentity and policyURL in campaign metadata.
      • 2) Call start: ADAD rings and plays a disclosure covering caller identity, purpose, recording, voice-biometric notice and withdrawal method.
      • 3) Affirmative consent: Contact says 'Yes' or presses DTMF; system timestamps consent event and creates consentReceiptID.
      • 4) Generate receipt: Server emits Kantara-aligned JSON with consentReceiptID UUID, consentTimestamp ISO‑8601, jurisdiction 'CA', collectionMethod 'ADAD-voice: spoken-affirmation', biometricProcessingFlag true/false, policyURL.
      • 5) Sign & store: Vendor signs receipt (JWS) producing signedConsentToken; store receipt in CRM linked to callID and contact record.
      • 6) Evidence capture: Save raw call audio and transcript; compute SHA‑256 hashes and record hashes in the consent record and evidence index.
      • 7) RAG logging: If RAG is used, log each retrieval (timestamp, retrievalID, doc-hash, queryText) and link to consentReceiptID.
      • 8) Revocation: Revocation updates consent record with revocationTimestamp and signedRevocationToken; retention/deletion generate signed audit events.
      • 9) Export: Buyer or auditor requests an evidence-export bundle (signedConsentToken, audio, transcript, hashes, RAG log, revocation record) for validation.

      Limitations, assumptions and invitation to a Scalix free audit

      Limitations and assumptions: CRTC UTRs set ADAD disclosure and calling rules but do not define machine-readable consent receipts; OPC guidance requires express consent for biometric voiceprints but does not mandate a schema. Kantara/ISO are candidate standards and may change. Buyers must validate acceptance tests with legal counsel.

      Invitation: Scalix can convert this brief into a scoped, free audit. Scalix will request a vendor sample evidence-export bundle, run cryptographic and linkage validations, and return a one-page buyer-ready audit summary with recommended contract clauses and remediation steps. A Scalix free audit is an operational validation service and is not legal advice.

        Common questions

        Does CRTC or OPC already require a machine‑readable consent receipt?
        No. CRTC UTRs govern ADAD calling practices and disclosures; OPC/PIPEDA guidance requires meaningful or express consent for sensitive uses (for example, voiceprints) but does not mandate a specific machine‑readable schema. Kantara and ISO work provide candidate schemas buyers can require; include schema versioning and acceptance tests in contracts and confirm requirements with legal counsel. See the CRTC and OPC links in sources.
        If a vendor claims they 'store recordings and transcripts', what should buyers ask for to prove auditable consent?
        Request a signed evidence-export bundle for a sample call that includes: the machine-readable consent receipt (signed as JWS), raw call audio + transcript, SHA‑256 hashes for each artifact, RAG retrieval log entries (if applicable), and any revocation record. Ask the vendor to disclose the public key for signature verification. Scalix can validate these items during a free audit.
        What minimal contractual acceptance tests should be required in an RFP?
        Require a vendor to provide a sample evidence-export bundle and pass pre-deployment tests: signed consent receipt validates against vendor public key; audio and transcript hashes match recorded values; RAG retrieval logs are timestamped and linked to consentReceiptID; revocation requests produce signed revocation tokens and logged audit events within agreed SLAs. Include schema version, key-rotation policy and delivery SLA for evidence-export in contract terms.

        Find your biggest time-saver

        Book a free AI audit, or call our 24-hour line at (825) 782-4956.

        More articles

        Start a call24-hour line