Skip to main content

Configure caller disclosure and data minimization

Wirevox does not determine which disclosure or consent rule applies to your organization, caller, location, sector, or use case. Obtain qualified legal advice and configure the agent accordingly.

Voice disclosure is customer-configured​

The inbound voice runtime does not automatically add a universal AI, transcription, or recording disclosure. Put the required notice in the Custom Greeting or system prompt and test that it is spoken before sensitive information is collected.

A practical opening may need to disclose:

  • that the caller is interacting with an AI agent;
  • that audio is being processed and the conversation transcribed;
  • whether audio is recorded for the configured deployment;
  • the purpose of collection; and
  • how the caller can decline or reach a person.

Do not claim a call is recorded unless the deployed recording path has been verified. Do not rely on a prompt instruction alone where a jurisdiction requires a particular form of consent or recordkeeping.

Minimize collection​

For every collected field, ask:

  1. Is it required to complete the caller's request?
  2. Is the agent allowed to collect it?
  3. Which system will store it?
  4. Who can access it?
  5. How will it be corrected or deleted?
  6. Can a less sensitive value accomplish the same purpose?

Avoid passwords, one-time codes, full payment-card details, government identifiers, health details, or legal case data unless the entire deployed service and contract are approved for that information.

Prompt rules​

Include rules such as:

PRIVACY
- Collect only the fields required for the caller's current request.
- Never ask for passwords, authentication codes, or full payment-card details.
- Repeat sensitive contact details only when necessary for confirmation.
- Do not reveal another person's information.
- If the caller declines required processing, offer the configured human or offline alternative.

Prompt rules guide the model; server-side function validation and least-privilege permissions remain necessary.

Beta Website Chat privacy controls​

Website Chat deployments can show a configurable privacy notice, link to a policy, and require explicit acceptance before starting. When accepted, Wirevox stores the acceptance time, notice text, and policy URL in the session contact data.

This feature is Beta. A checkbox is not proof that the notice is legally sufficient. Match it to the deployed website, allowed origins, collected pre-chat fields, provider flow, and applicable policy.

Testing​

Verify the disclosure with a new live call, not only a browser test. Test refusal, human handoff, correction of contact details, unknown callers, and attempts to obtain another person's data.