AI voice agents

Scalix 2027 evaluation: Minimal tamper‑evident consent receipt & evidence export for ADAD outbound AI voice agents in Canada

· 14 min read · Scalix, Calgary

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

Quick answer

This Scalix 2027 evaluation gives Canadian procurement, privacy and technical buyers a single implementable minimal specification to demand from vendors of ADAD/predictive dialing outbound AI voice agents. It maps ISO/IEC TS 27560 consent‑receipt fields to an auditable export: signed consent token (JWT), raw call audio with SHA‑256, transcript provenance (engine/version/job ID + hash), a time‑stamped RAG retrieval log, hash‑chained tamper evidence and a machine‑readable revocation record. The brief includes buyer acceptance tests, a short hypothetical worked example and starter contract clauses. Request a Scalix free audit to convert this into acceptance tests tailored to your environment.

Executive summary and immediate buyer action (Scalix offer)

Scalix presents a minimal, interoperable evidence specification buyers can require from ADAD/predictive dialing vendors: an ISO/IEC TS 27560‑aligned JSON consent_receipt, anchored notice metadata, a signed consent token, raw call audio + transcript with cryptographic hashes, a tamper‑evident manifest linking items, and a time‑stamped RAG retrieval log when RAG is used.

Buyers should include the acceptance tests in RFP evidence lists or bring vendor responses to a Scalix free audit; Scalix will map vendor exports to the minimal spec and produce tailored acceptance tests and remediation steps.

  • One‑line need: auditable express consent and linked evidence for ADAD outbound calls.
  • Buyer action: demand the minimal evidence spec and the acceptance‑test deliverable in bids or request a Scalix free audit.
  • Deliverables Scalix can map in a free audit: machine‑readable consent JSON, signed consent token, audio/transcript hashes, RAG retrieval log, revocation record.

Regulatory snapshot — what buyers should verify from vendors

CRTC Unsolicited Telecommunications Rules require express consent and clear disclosure/identification at call start for outbound automated dialing; buyers should require number‑specific, timestamped express consent evidence before ADAD campaigns are run. The CRTC text is the reference for ADAD obligations.

The Office of the Privacy Commissioner (OPC) and PIPEDA guidance treat voiceprints/biometrics as sensitive in many contexts; express, informed and purpose‑specific consent is expected and buyers should demand vendor proof of voiceprint lifecycle controls and deletion on request.

  • ADAD express consent should be tied to the called number and include timestamps and notice reference.
  • Voiceprint collection/retention frequently triggers stronger consent expectations; require explicit retention, deletion SLA and proof.
  • Third‑party processors (ASR/RAG) must be contractually accountable; require provenance exports and audit rights.

Minimal evidence specification — what to require in RFPs

Base the consent_receipt JSON on ISO/IEC TS 27560 fields and include anchored notice metadata (notice_version_reference + integrity hash) so buyers can correlate what notice/version the caller received before consenting.

Require these exported evidence items per call or per consent event: consent_receipt JSON (TS 27560 fields), a signed consent token referencing consent_receipt_id, raw call audio with a content hash, transcript with ASR provenance and hash, exported RAG retrieval log when used, a tamper‑evidence manifest linking all items, and a machine‑readable revocation record when consent is withdrawn.

  • Essential consent_receipt fields: controller_id, notice_id, consent_timestamp, consent_method, purposes, data_types, retention_period, notice_version_reference.
  • Anchored notice metadata: notice_version_reference + integrity hash (align with Kantara ANCR patterns where available).
  • Signed consent token: cryptographically signed JWT referencing consent_receipt_id with signer key metadata included in the export.

Technical implementation patterns — signatures, hashes and manifests

Signed consent token: use a standard JWT (RS256 or stronger) that embeds consent_receipt_id, signer_kid and issuance timestamp; vendors must provide the public key or a verifiable key reference in the evidence export so buyers can verify signatures.

Audio/transcript linkage and tamper evidence: store raw call audio (WAV/FLAC), compute SHA‑256 over raw bytes and record the hash in the consent_receipt; store transcript with its file hash and ASR provenance (engine, model_version, job_id, timestamps). Create a signed manifest that hash‑chains consent_token → audio_hash → transcript_hash → RAG_log_hash.

  • Audio file metadata: call_id, calling_number, called_number, PSTN timestamps, recording_id and SHA‑256(audio_file).
  • Transcript provenance fields: asr_engine, model_version, asr_job_id, transcript_timestamp_range and SHA‑256(transcript_file).
  • RAG retrieval log fields: query_id, retrieval_timestamp, document_ids, retrieval_hash and prompt_template_version if used.

Buyer acceptance tests and a short hypothetical worked example

Acceptance tests are executable checks buyers or auditors can run on an evidence bundle. Require vendors to provide a signed export package and the public signing key (or key reference). Tests should include signature verification, hash recomputation, ASR/RAG provenance cross‑checks and revocation flow validation.

Hypothetical worked example (short): BankCo runs an ADAD campaign. For one call sample the vendor provides: consent_receipt.json (with consent_timestamp and notice_version_reference), consent_token.jwt (signed), recording.wav, transcript.txt, rag_log.json and manifest.signed. Buyer test: verify JWT signature with provided public key; recompute SHA‑256(recording.wav) and SHA‑256(transcript.txt) and confirm matches manifest; check rag_log.json entries for retrieval_ids and timestamps; confirm revocation if BankCo submitted deletion request.

  • Signature test: verify consent_token JWT signature and confirm consent_receipt_id consistency.
  • Hash linkage test: recompute SHA‑256(audio) and SHA‑256(transcript) and confirm presence in signed manifest and consent_receipt.
  • ASR/RAG provenance test: match ASR job_id and model_version with vendor console logs; verify RAG retrieval_ids and retrieval_hashes in vendor retrieval logs.

Sample contractual clause seeds (starter language)

Below are concise, buyer‑facing clause seeds. Buyers must have counsel review and adapt these to jurisdictional and procurement needs. Scalix will map these clauses to your procurement terms in a free audit and produce measurable acceptance tests.

Clauses address ADAD express‑consent evidence, voice biometric retention/deletion, ASR/RAG provenance and third‑party audit rights. They are starter language, not legal advice.

  • ADAD express‑consent evidence: "Vendor shall supply, per call, a signed consent_receipt JSON (ISO/IEC TS 27560 fields), signed consent token, raw audio file and transcript with cryptographic hashes within [X] days of request. Consent evidence must link to the called number and timestamp."
  • Voice biometric retention/deletion: "Vendor shall treat voiceprints as biometric data: retention period declared in the consent receipt, deletion on verified request within [Y] days, and provide cryptographic proof of deletion (signed deletion manifest)."
  • ASR/RAG provenance and audit: "Vendor shall preserve ASR engine, model_version and job_id and RAG retrieval_ids for retention period; notify buyer 30 days before material model or prompt‑template changes; permit vendor‑provided or third‑party audit of provenance records under NDA."

Next steps, limitations, three‑item shortlist checklist and Scalix free audit

If your procurement or privacy team wants a runnable acceptance‑test package, a one‑page machine‑readable consent JSON example or contract clause mapping, request a Scalix free audit (30–90 minutes). Scalix will map vendor evidence to this minimal spec and produce buyer acceptance tests tailored to your environment.

Limitations and dated assumptions: this brief is evaluation material, not legal advice. Standards and guidance evolve — ISO/TS 27560 exists as a baseline but profiles/extensions (e.g., Kantara ANCR) were in public review in 2026; buyers should re‑check sources when drafting final RFP language. Availability of vendor features (signed tokens, export formats, RAG logs) depends on vendor roadmaps.

  • Request a Scalix free audit to convert this brief into an implementation scope and runnable acceptance tests.
  • Three‑item shortlist checklist (quick prescreen for vendors): 1) Can the vendor produce a TS‑27560‑aligned consent_receipt JSON and signed consent token on demand? 2) Can the vendor export raw call audio + transcript with SHA‑256 hashes and a signed manifest linking them?
  • Use counsel to adapt timelines (e.g., deletion SLA) to legal risk; do not treat this brief as legal advice.

Common questions

Which ISO/IEC TS 27560 consent‑receipt fields are essential for auditable ADAD consent in Canada?
Require a consent_receipt JSON containing at minimum: controller_id, notice_id, consent_timestamp, consent_method, purpose(s), data_types, retention_period and notice_version_reference. These map to ISO/IEC TS 27560 and let buyers correlate consent to notice content and timing. See ISO/IEC TS 27560 for details: https://www.iso.org/standard/80392.html.
How should buyers demand tamper‑evident linkage between a signed consent receipt, call audio/transcript and RAG retrievals?
Require a signed manifest or hash chain that includes: signed consent token referencing consent_receipt_id, SHA‑256(audio), SHA‑256(transcript), and retrieval_hashes for any RAG results. Buyers should verify signatures and recompute hashes against exported files as acceptance tests; include public key or verifiable key reference in the export.
What minimum retention, revocation and deletion timelines should vendors commit to for voiceprints under PIPEDA/OPC expectations?
OPC expects express, informed, specific consent for biometrics; buyers should require the consent receipt to declare an explicit retention period, require deletion on verified request within an SLA (example ranges seen in procurement are 30–90 days), and require signed proof of deletion. Legal counsel should confirm exact timelines based on risk and contractual context. See OPC guidance: https://www.priv.gc.ca/en/opc-news/news-and-announcements/2026/nr-c_261008.
What evidence proves ASR/RAG provenance for transcripts produced during calls?
Ask vendors for ASR_engine, model_version, asr_job_id, transcript file hash and transcript timestamps, and vendor console logs showing the job_id and engine/version. For RAG, require query_id, retrieval_timestamp, document_ids and retrieval_hash so you can link surfaced content back to stored documents. Preserve these fields for the retention period stated in the consent receipt.

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