Free AI audits
Scalix buyer brief: Minimal auditable consent receipt & evidence export for AI voice agents in Canada (2027-ready)
· 8 min read · Scalix, Calgary
Published by Scalix. For questions or corrections, contact us.
Quick answer
This Scalix enquiry brief gives Canadian procurement, privacy and technical buyers a single implementable minimal evidence specification for vendors of outbound AI voice lead agents. It prescribes (1) a machine‑readable consent_receipt.json mapped to ISO/TS‑27560 and Kantara patterns, (2) a tamper‑evident auditable export that ties a signed consent token to call recording, transcript, RAG retrieval log and revocation record, and (3) buyer acceptance tests and contract clause seeds to include in an RFP or use during a Scalix free audit. This guidance is educational and procedural—not legal advice. Sources cited: CRTC ADAD rules, OPC biometric guidance and NIST AI RMF playbook (Govern).
Introduction — purpose, scope and Scalix offer
Scalix prepared this concise buyer brief to give Canadian organisations a single, implementable minimal evidence specification to require from vendors of outbound AI voice agents (ADAD/predictive dialing) that use voice‑biometrics or RAG retrieval.
Use this brief to (A) include explicit evidence fields in an RFP, (B) run the acceptance tests listed here during vendor evaluation, or (C) request a free Scalix audit enquiry; Scalix will scope a one‑hour intake to tailor templates to your procurement context.
- Target outcome: demonstrate express consent for a phone number, prove biometric enrolment consent when used, and show provenance for documents surfaced by RAG.
- Scope: outbound ADAD/predictive dialing, voice‑biometric enrolment/use, and RAG retrieval during calls.
Regulatory foundations and dated assumptions/limitations
CRTC rules for Automatic Dialing–Announcing Devices (ADAD) require demonstrable express consent for calls to a specific number; buyers must ask vendors to export evidence that consent covered the called number at call time. Source: CRTC. (accessed 2026‑11‑16)
The Office of the Privacy Commissioner of Canada (OPC) treats voiceprints/biometric templates as sensitive personal information and expects express, informed and specific consent for enrolment, transparency on retention and clear opt‑out information. Source: OPC. (accessed 2026‑11‑16)
NIST AI governance guidance (AI RMF Playbook — Govern) emphasises auditability and provenance for AI systems; this supports requiring RAG retrieval logs and provenance in audit exports. Source: NIST/AIRC. (accessed 2026‑11‑16)
Dated assumptions & limitations (2026‑11‑16): (1) legal/regulatory interpretation evolves—this brief is procedural, not legal advice; (2) ISO/TS‑27560 and Kantara consent receipt adoption is uneven; (3) some vendors/legacy dialers may not yet provide full RAG tracebacks or key‑managed signed receipts—buyers must include remediation timelines and fallback escrow in contracts.
- Buyer outcome: vendor must export proof that a consent receipt existed prior to or at call start and that any biometric enrolment had express consent recorded.
- Expect vendor constraints (legacy dialers, hosted vector DBs); require staged remediation and escrow if immediate full exports are not available.
Minimal machine‑readable consent receipt — required fields (buyer spec)
Require a single machine‑readable consent_receipt.json per consent event that maps to ISO/TS‑27560 elements and Kantara receipt concepts. The receipt must be exportable and cryptographically signed (JWS/JWT) with key metadata.
Scalix recommends buyers require the fields below and include validation steps in RFPs and acceptance tests. ISO/IEC TS 27560 provides the baseline structure for consent record elements.
- consent_id (UUID) — durable identifier for the consent event
- principal_id — pseudonym or hashed identifier (avoid raw identifiers); method noted
- consent_timestamp (UTC ISO8601) — time of consent capture
- consent_scope/purpose — human and machine label linking to call purpose
- applied_contact — phone number(s) or contact identifiers the consent covers
- consenting_agent — identifier for agent/system that captured consent (agent id, UI/session id)
- signature — detached or embedded JWS/JWT with issuer, key id (kid) and alg
- key_rotation_metadata — issuer public key URL and rotation history reference
- metadata — capture_method (IVR/agent/voice-biometrics-enrolment), locale and record_version
Auditable evidence export: packaging, components and verification
Require a tamper‑evident packaged export for each call that links artifacts to consent_id and includes checksums and signatures. Exports should contain both a human summary and a machine manifest (manifest.json).
Specify delivery formats (for example, a ZIP with manifest.json + detached signature) and include verification steps a third‑party auditor can run; Scalix can provide a template and test scripts during a free audit enquiry.
- manifest.json — lists attachments, filenames, SHA‑256 checksums, consent_id and UTC timestamps
- call_recording.wav (or .mp3) — with start/stop UTC times and checksum; file must match manifest
- transcript.txt — speaker labels and timestamps; link to consent_id
- consent_receipt.json — signed JWS/JWT as specified above
- RAG_retrieval_log.json — array of retrieval entries: retrieval_id, timestamp, prompt, retrieved_doc_ids, similarity_score, snippet_used, vector_db_id and region
- revocation_log.json — consent_id, revocation_timestamp, revocation_method, confirmation of cessation or retention snapshot
- access_audit.json — export actor_id, IP, export_timestamp and signature verifying who produced the package
Buyer acceptance tests (pass/fail) and contract seeds
Scalix recommends including the following pass/fail tests in an RFP or running them during a Scalix free audit. Tests should be runnable by the buyer or an independent auditor using the export package.
Embed contractual SLAs that set export timelines, key‑escrow rules, retention, breach notification windows and staged remediation when vendors lack immediate traceability.
- Verify signature: validate consent_receipt.json JWS against issuer public key in manifest; confirm kid and key rotation metadata.
- Timestamp relationship: consent_timestamp ≤ call_start_timestamp; consent_scope includes call purpose and applied_contact.
- Call linkage: call recording checksum matches manifest; transcript references consent_id and speaker labels align with audio.
- RAG provenance: for each retrieval entry, confirm retrieved_doc_ids exist (or are escrowed), snippet matches document excerpt, and similarity_score and timestamp are present.
- Revocation test: simulate consent withdrawal and verify revocation_log.json contains revocation_timestamp and an export showing cessation of use or applied retention rule.
- Contract seeds: delivery of export within X business days on request; key escrow clause for verification under forensic conditions; breach notification ≤72 hours; obligation to provide reproducible TEVV artifacts for RAG where outputs affect decisions.
Quick buyer checklist (3 essentials), hypothetical worked example and next steps
Use these three essentials as the minimum gate for shortlisted vendors. Scalix can convert this brief into the complete export template and an acceptance test script during a free Scalix audit enquiry (one‑hour intake).
Hypothetical worked example (compact): a vendor export for call 2026‑F3 includes manifest.json linking consent_id=UUID‑1234 to consent_receipt.json (signed JWS), call_recording.wav with matching SHA‑256, transcript.txt referencing consent_id, RAG_retrieval_log.json with retrieval_id entries pointing to document ids stored in escrow, and revocation_log.json showing no revocation. Buyer verifies JWS using issuer public key URL in manifest and confirms consent_timestamp precedes call_start — acceptance passes.
Next step: request a free Scalix audit enquiry; Scalix will scope a one‑hour intake and produce a consent_receipt.json example (ISO/TS‑27560/Kantara mapping), an auditable export sample and a short acceptance test script tailored to your procurement.
- Essentials — require (A) a signed machine‑readable consent_receipt.json that names applied_contact and consent_timestamp, (B) a tamper‑evident export package (manifest + recording + transcript + RAG log + revocation_log) with checksums and detached signature.
- Include fallback remediation timelines and escrowed snapshots for vendors that cannot produce full RAG tracebacks immediately.
- Ask Scalix for a free audit enquiry to validate a sample export and obtain contract clause language for legal review.
Common questions
- What exact fields prove 'express consent' for ADAD calls and voice‑biometric enrolment?
- Require a signed consent_receipt.json containing consent_id (UUID), principal_id (pseudonym/hash), consent_timestamp (UTC ISO8601), applied_contact (phone number), consent_scope/purpose, consenting_agent id and capture_method (IVR/agent/voice_enrolment), plus signature metadata (issuer, kid). These map to ISO/TS‑27560 elements and let an auditor confirm consent was captured for the called number before or at call start. See ISO/IEC TS 27560: https://committee.iso.org/files/live/sites/jtc1sc27/files/news/ISOIEC_TS_27560_2023.pdf
- Which cryptographic and logging controls are minimally sufficient for an evidence export?
- Minimum controls: a signed consent receipt (JWS/JWT) with issuer public key URL and kid; SHA‑256 checksums for artifacts recorded in manifest.json; an access_audit record (actor id, IP, timestamp); and key rotation metadata. Store exports in tamper‑evident object storage or use hash chain/versioning. Require contractual key‑rotation records and a key‑escrow process for forensic verification. See NIST AI RMF Playbook (Govern) for auditability context: https://airc.nist.gov/airmf-resources/playbook/govern/
- What minimal RAG retrieval logs must vendors include in an audit export?
- For every retrieval used during a call include retrieval_id, timestamp, prompt text, retrieved_doc_ids, similarity_score, snippet_used by the agent, and vector_db_id/region. This provides provenance for assertions surfaced by the agent and aligns with NIST traceability recommendations. Buyers should require escrow or reproducible access to referenced documents when outputs affect decisions.
- How should a buyer test a vendor’s evidence export during a Scalix free audit?
- Scalix suggests these verification steps: (1) validate JWS signature against issuer public key referenced in manifest; (2) ensure consent_timestamp ≤ call_start_timestamp and consent scope covers applied_contact; (3) confirm recording checksum equals manifest entry and transcript links to consent_id with matching speaker labels; (4) check RAG entries point to existing or escrowed documents and snippets match; (5) simulate revocation and confirm revocation_log shows cessation or applied retention. Scalix can run these tests on a sample export during a scoped free audit intake.
Find your biggest time-saver
Book a free AI audit, or call our 24-hour line at (825) 782-4956.