AI & Call Recording Disclosure
Review draft · not effective. Professional review and factual verification pending.
Contents
1. An AI agent may answer
Businesses using Voice AI may answer incoming calls with an AI-powered voice agent. Speech and relevant context may be processed to understand requests, answer questions, collect orders and provide requested support. AI can make mistakes; verify important details and use the business’s available human-contact channel for assistance.
2. Recording is configuration-dependent
A voice interaction does not mean that every call is recorded. Recording, transcription and retention depend on the business’s configuration, selected providers and applicable law. Real-time speech processing can occur even when no audio recording is retained. Businesses must verify actual settings and explain storage and processing accurately.
3. Business notices and caller choices
The business is responsible for delivering required notices and obtaining applicable consents before the relevant processing. The notice must identify the business and purposes, explain required/voluntary information and consequences of refusal, relevant recipients, rights and a working contact route. Add sector and jurisdiction requirements. Do not rely on continued speech as universal consent. Where consent is required, implement and test a valid choice before processing and a lawful alternative for refusal.
4. Providers and more information
AI, speech and telephony providers may assist with processing, potentially outside Israel. The business must supply its deployment-specific privacy notice and rights mechanism. Callers should contact the business they called for access or correction requests. Morganext’s draft Privacy Policy and Subprocessors notice explain the respective roles and verification gaps.
5. Sample opening — AI interaction
“Hello, you have reached [Business]. I am an AI voice assistant helping with [purpose]. For information about how your details are used, or to contact our team, [tested contact option].” This is a short introduction to combine with the full required notice, not a complete legal notice. Replace every bracketed field and test the option offered.
6. Sample addition — only if recording is enabled
“This call will be recorded and transcribed for [specific purposes]. For information about retention and your rights, [privacy contact or notice route]. If you prefer another way to contact us, [available alternative].” Use only the processing verbs that are true. If consent is needed, replace this informational wording with counsel-approved consent steps and do not start the relevant processing before those steps are completed.
7. Configuration checklist and status
Before launch: verify AI identification, actual audio/transcript settings, providers and purposes; translate announcements for each supported language; confirm legal requirements; test notice timing, refusal paths and human-contact options; record the approved version and revisit it after changes. Do not promise an immediate human transfer if it is unavailable. Draft dated 12 November 2026; not approved for live calls.