1. AI answers; people manage the service
Caller-facing conversations use artificial intelligence and a synthetic voice. Your Voice Partner is a human who configures, tests, supports, and updates the service; this does not mean a human is listening to every call or available to answer immediately. The operator must not falsely claim to be human and should identify itself truthfully when asked. Additional upfront disclosure is used where required by the approved configuration or applicable law.
AI can misunderstand speech, accents, names, dates, intent, or business instructions, and can produce incomplete or incorrect answers and summaries. Background noise, interruptions, language limitations, and network failures affect results. You must review important outcomes and keep suitable human follow-up. The service does not promise revenue, perfect accuracy, a completed transfer, or successful emergency help.
2. Live audio, transcripts, and optional recordings
Audio is processed in real time by our voice and AI providers to conduct the conversation. Call information may be transcribed, summarized, classified, and stored for the approved service, follow-up, quality review, billing, or troubleshooting, subject to the Privacy Notice and Data Processing Addendum. Recording being off does not mean there is no audio processing or transcript.
Stored audio recording is disabled by default. Turning it on requires a separately approved lawful configuration and the required caller notices and permissions. Do not describe every call as unrecorded without checking both our settings and any customer-controlled carrier or connected service. Authorized service personnel may review necessary call records for support and quality purposes.
3. Notices and permissions before activation
The business customer must identify its lawful purpose for processing calls, provide an appropriate caller privacy notice, and obtain any notice, consent, or other authorization required for AI interaction, transcription, recording, transfers, and data sharing. Requirements can differ depending on where callers and the business are located and what information is handled. A customer’s checkout acknowledgment is not the caller’s consent.
We will help implement the approved disclosure and call-handling configuration, but do not provide legal advice or determine that every caller jurisdiction permits it. We retain responsibility for our own legal obligations and must not follow unlawful instructions. If required permission cannot be obtained or a caller objects, use an approved alternative contact route or end the affected processing as the lawful workflow requires. Do not enable a workflow that cannot honor the required choice.
A starting point for counsel to adapt is: ‘You’re speaking with the AI assistant for [business]. Your call is processed by our service providers and may be transcribed to help with your request. Please don’t share payment-card details or sensitive personal information.’ This example is not a universal consent script; recording, consent collection, and alternative-contact wording must match the actual setup.
5. Public demonstrations
The public demo is an illustration using a sample business, not your production line or a promise of every feature. Microphone access lets the demo process the audio you choose to provide. Do not enter confidential business details or sensitive personal information. Limits may apply to call length, number of sessions, or availability to prevent abuse. Browser permission alone does not replace legally required notice or consent for other people you record.