AI communications

Consent & transparency guide for intelligent voice systems

This page is informational and not legal advice. It describes practical patterns to keep automated outreach transparent, respectful, and compliant when using real-time transcription, large language models, and natural speech to conduct human-quality conversations and take action.

Overview

Core principles

Be explicit that an AI assistant is speaking. Match consent strength to channel and purpose. Offer a fast human path. Provide easy opt-out everywhere. Keep an auditable consent record. Separate transactional and promotional content.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>Clear disclosure</h4>
    <p>Introduce the agent as an AI assistant from your company at the start of the interaction. Keep the statement short and natural.</p>
  </div>
  <div class="grid-card">
    <h4>Right tier of consent</h4>
    <p>Automated voice is strictest; promotional content requires stronger consent than informational updates. Text/email are lower friction but still need opt-in.</p>
  </div>
  <div class="grid-card">
    <h4>Human handoff</h4>
    <p>Always provide an immediate way to reach a person (e.g., say “human” or press 0). In chat/SMS, display a clear handoff option.</p>
  </div>
  <div class="grid-card">
    <h4>Opt-out hygiene</h4>
    <p>Support STOP for SMS, unsubscribe in email, and a spoken/keypress stop in voice. Confirm opt-outs right away.</p>
  </div>
  <div class="grid-card">
    <h4>Content separation</h4>
    <p>Do not mix offers into transactional notices. If a message includes promotion, treat it as marketing and use higher consent.</p>
  </div>
  <div class="grid-card">
    <h4>Audit trail</h4>
    <p>Store consent text/version, timestamp, IP, method, and opt-out events. Be able to retrieve a user’s record on request.</p>
  </div>
</section>

Direction

Inbound and outbound intelligence

These are not IVRs. Agents use live transcription and LLMs to parse speech, reason about intent, and act in real time with natural two-way conversation and sub-second turn-taking.

Inbound: Caller initiates. The agent listens, understands context, and executes tasks (scheduling, CRM updates, lookups) while speaking naturally. It escalates when human input adds value, not by necessity.

Outbound: Agent initiates. It adapts mid-conversation, follows consent and frequency rules, and completes follow-ups (texts, emails, records) without breaking flow.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>Natural two-way speech</h4>
    <p>Handles interruptions, back-channel cues, and timing like a human. Latency tuned for fluid dialogue.</p>
  </div>
  <div class="grid-card">
    <h4>Real-time reasoning</h4>
    <p>Every turn passes through transcription → LLM reasoning → action planner to decide the next best move.</p>
  </div>
  <div class="grid-card">
    <h4>Connected actions</h4>
    <p>Update CRMs, book meetings, send SMS, trigger workflows during or immediately after the call.</p>
  </div>
  <div class="grid-card">
    <h4>Context & memory</h4>
    <p>Recall prior interactions and preferences to personalize each conversation across sessions.</p>
  </div>
  <div class="grid-card">
    <h4>Ethical defaults</h4>
    <p>Transparent disclosure, logged consent, respectful cadence, and fast human access.</p>
  </div>
  <div class="grid-card">
    <h4>Unified experience</h4>
    <p>Inbound and outbound share the same knowledge and rules so users get continuity across channels.</p>
  </div>
</section>

Channels

Voice, SMS, email, chat

Choose the lightest channel that fits the goal. Voice automation needs the strongest consent; SMS and email are lower friction but still require clear opt-in and easy opt-out.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>Voice (strict)</h4>
    <p>Identify automation and brand early, offer human path, provide stop option, and keep scripts purpose-specific.</p>
  </div>
  <div class="grid-card">
    <h4>SMS (pragmatic)</h4>
    <p>Brand in first line, concise copy, STOP/HELP keywords, and sensible quiet hours for your audience.</p>
  </div>
  <div class="grid-card">
    <h4>Email (clear)</h4>
    <p>Transparent subject, recognizable sender, visible unsubscribe. Split transactional from marketing streams.</p>
  </div>
  <div class="grid-card">
    <h4>Chat (contextual)</h4>
    <p>Ask for consent inline, show exactly what users will receive, and link to preferences to refine choices.</p>
  </div>
  <div class="grid-card">
    <h4>Cadence</h4>
    <p>Define default limits per channel (e.g., one promo SMS/week; transactional as needed). Display cadence in preferences.</p>
  </div>
  <div class="grid-card">
    <h4>Accessibility</h4>
    <p>Use clear language and appropriate pacing. Offer alternatives on request and respect language preferences.</p>
  </div>
</section>

Consent

Low-friction capture patterns

Keep the ask short and visible. Use unchecked checkboxes, confirmations where helpful, and a preferences page so users can adjust later.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>Signup checkbox</h4>
    <p>“I agree to receive automated or AI-assisted calls, SMS, and emails from [Company]. Message frequency may vary. Reply STOP to opt out.”</p>
  </div>
  <div class="grid-card">
    <h4>Double opt-in (SMS)</h4>
    <p>[Company]: Reply YES to confirm texts about your account and updates. Msg &amp; data rates may apply. Reply STOP to unsubscribe.</p>
  </div>
  <div class="grid-card">
    <h4>Email confirm</h4>
    <p>Send a link the user clicks to confirm outreach. Log the click with timestamp and the consent text/version.</p>
  </div>
  <div class="grid-card">
    <h4>In-widget prompt</h4>
    <p>Before starting chat, show a one-line disclosure and capture an explicit Yes. Link to full terms for details.</p>
  </div>
  <div class="grid-card">
    <h4>Phone consent</h4>
    <p>If provided during a human call, record the statement and follow up with written confirmation.</p>
  </div>
  <div class="grid-card">
    <h4>Transactional vs promo</h4>
    <p>Keep streams separate. If any promotional content is included, treat as marketing and use higher consent.</p>
  </div>
</section>

Snippets

Language you can adapt

Short, readable phrases increase comprehension and reduce friction. Adjust tone to fit your brand voice.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>Voice intro</h4>
    <p>“Hi, this is the automated assistant for [Company]. I’m calling about [reason]. Say ‘human’ or press 0 to talk to a person.”</p>
  </div>
  <div class="grid-card">
    <h4>Consent clause (TOS)</h4>
    <p>“By providing your phone number and agreeing to the Terms, you consent to receive automated or AI-assisted calls, prerecorded messages, SMS, and emails from [Company] for account updates and offers. Consent is not a condition of purchase. Opt out anytime by replying STOP or contacting support.”</p>
  </div>
  <div class="grid-card">
    <h4>SMS opt-in</h4>
    <p>[Company]: Reply YES to confirm you want texts about your account and updates. Msg &amp; data rates may apply. Reply STOP to unsubscribe.</p>
  </div>
  <div class="grid-card">
    <h4>Email confirm</h4>
    <p>“Confirm your communication preferences with [Company]: [link]. You can update or opt out anytime.”</p>
  </div>
  <div class="grid-card">
    <h4>Opt-out confirm</h4>
    <p>[Company]: You are unsubscribed and will no longer receive messages. To rejoin later, update preferences at [link].</p>
  </div>
  <div class="grid-card">
    <h4>Human handoff</h4>
    <p>“Need a person? Say ‘human’ or press 0 and we’ll connect you right away.”</p>
  </div>
</section>

Records

Audit & data hygiene

Keep consent logs secure and searchable. Test unsubscribe and handoff flows regularly. Remove contacts that bounce, complain, or opt out.

<section class="feature-grid-2x3">
  <div class="grid-card">
    <h4>What to store</h4>
    <p>User identifier, contact method, exact consent text or terms version, timestamp, IP, user agent, consent method, and opt-out events.</p>
  </div>
  <div class="grid-card">
    <h4>Verification</h4>
    <p>Be able to export a single user’s consent history on request. Redact nonessential data before sharing internally.</p>
  </div>
  <div class="grid-card">
    <h4>Security</h4>
    <p>Restrict access, encrypt where feasible, and monitor for spikes or unusual outreach patterns.</p>
  </div>
  <div class="grid-card">
    <h4>Review cadence</h4>
    <p>Schedule periodic reviews of templates, logs, and opt-out handling. Update language as regulations or practices evolve.</p>
  </div>
  <div class="grid-card">
    <h4>Team playbook</h4>
    <p>Document who can send what, to whom, how often, and through which channels. Train teams on consent and opt-outs.</p>
  </div>
  <div class="grid-card">
    <h4>Escalation</h4>
    <p>Provide a clear route for complaints or confusion and prioritize fast human intervention when needed.</p>
  </div>
</section>

Closing

Transparency builds better conversations

Clear disclosures, simple choices, easy opt-outs, and reliable records make automation work for everyone. Keep it honest, useful, and human-centric.