Yes. A customer-facing voice agent should identify itself as automated at the start, name the business and explain how to reach a person. Adopt this as an explicit business policy, with recording and privacy wording reviewed for your actual setup. A friendly voice should still give callers a clear understanding of who, or what, is answering.
For a South African business considering AI chatbots or voice support, the useful output is a call-opening policy staff can review, implement and test. The recommendations below are proposed workflow rules, rather than a claim that every telephone service has the same legal disclosure requirement.
Choose an introduction that gives the caller a decision
Compare three approaches. A human-sounding greeting with no disclosure leaves the caller guessing. A lengthy explanation of the technology delays help. A short, transparent introduction gives the caller enough information to choose whether to continue.
A hypothetical repair business could say: “Hello, you’ve reached Example Repairs. I’m an automated voice assistant. I can help with repair enquiries, or you can ask to speak to a person.” That wording is suitable only if those tasks and the human route are available.
Avoid an introduction such as “Hi, I’m Thandi from customer care” without explaining the automated role. A name can remain part of the brand, but the role should be explicit. Prefer “automated voice assistant” to technical terms customers must interpret.
State the role before collecting the caller’s story. If the caller interrupts, acknowledge them and finish the essential disclosure before requesting details. This opening choice belongs in your broader AI automation design, alongside the assistant’s permitted tasks.
Separate disclosure, recording notices and permission
These statements answer different questions: “Am I speaking to a person?”, “What happens to this conversation?” and “Was the business entitled to contact me?” Saying that the assistant is automated does not answer the other two.
Map whether the system processes live audio, saves recordings, creates transcripts or stores summaries. Give your privacy adviser that map, the purposes, recipients and retention settings. Ask them to approve the notice, any permission step and the response when a caller objects. Do not improvise a universal consent rule from an API guide.
OpenAI’s supplied data-controls documentation distinguishes abuse-monitoring logs from application state and describes endpoint-specific retention and approval-dependent controls. Those distinctions mean that “we do not save recordings” cannot stand in for an explanation of every system handling call content. Source: OpenAI data controls
Use concrete wording after review: identify what is retained and why. Avoid “for quality purposes” if the actual purpose also includes preparing service requests. Keep a fuller explanation available through a real existing contact route.
If a caller declines recording, offer only an alternative that has been verified. A staff transfer may still be recorded. Until the organisation has a working alternative, the assistant should explain the available next step without promising an unrecorded call.
Match the human option to the channel
“Ask for a person” needs a defined destination. During staffed hours, that might be a transfer queue. Outside those hours, it might be a callback request or a published contact route. The opening should distinguish these situations instead of suggesting that someone is always waiting.
For WhatsApp specifically, the supplied policy requires prompt, clear and direct escalation paths when businesses use automation to respond during its customer-service window. It also addresses opt-in for subsequent messages or calls and recommends separate call opt-in as a best practice. These are channel-specific points; they do not establish a blanket rule for ordinary telephone calls. Source: WhatsApp Business messaging policy
Review the selected channel’s current policy before deployment. Check product, account, plan and region eligibility for the proposed setup, rather than assuming a documented option is enabled for your business.
Your agent-versus-automation comparison should include this question: does the opening require flexible conversation, or would a fixed greeting and reliable routing serve callers better? Disclosure should remain consistent either way.
Reusable call-opening policy
The following is a proposed policy for internal review. Replace the placeholders and approve the applicable notice before use.
Purpose: Give callers an informed choice before collecting their enquiry.
Owner: [Customer-service manager]. Privacy reviewer: [Named adviser]. Applies to: [Inbound/outbound calls and selected channel].
- Identify the business and automation. Say: “Hello, you’ve reached [business]. I’m an automated voice assistant. I can help with [approved task].” For outbound calls, use “I’m calling from [business]” and state the approved purpose; confirm contact permission before placing the call.
- Explain the human route. During staffed hours, say: “You can ask to speak to a person.” Outside staffed hours, say: “Our team is unavailable now. I can [verified callback or contact option].” Never promise a transfer or response time without operational confirmation.
- Give the applicable privacy notice. Before substantive collection, use the reviewed wording for recording, transcription and other retained call content. Include any required permission question. Do not claim the call is unrecorded unless the complete route supports that statement.
- Handle interruption and uncertainty. If disclosure is interrupted or inaudible, repeat the essential information. If a required response is unclear, clarify it; do not mark it accepted. Offer a person when clarification fails.
- Respect the caller’s choice. On a human request or objection, stop the enquiry questions and use the approved alternative. Collect only the details needed for that alternative, under the applicable notice.
- Confirm routing outcomes. Report a transfer or callback request as successful only after the receiving system confirms it. Check for an existing matching callback request before creating another; send uncertain matches to staff.
- Keep a limited opening record. Record the script version, notice-delivery status, any required response, human request and confirmed routing result. Use “unknown” where evidence is missing. Restrict access and apply the organisation’s reviewed retention rules.
Release check: The owner confirms accurate opening wording and working human routes; the privacy reviewer approves notices and objection handling; the operator demonstrates ordinary, interrupted, ambiguous and duplicate-request cases.
Work through ordinary and difficult calls
All businesses and situations in these examples are hypothetical. The handling rules are proposals for review.
Ordinary enquiry: A caller asks Example Repairs about booking an appliance assessment. The assistant gives its identity, explains the human route and delivers the applicable notice before taking booking details. The caller continues. Staff reviewing the interaction should be able to establish which opening was used and whether any required response was obtained. Continuing alone must not be treated as consent where the reviewed process requires an explicit answer.
Missing disclosure: The caller speaks over the opening, asking whether the shop is open. The assistant can acknowledge the question, then repeat its automated identity and any notice needed before collecting details. If playback evidence is unavailable, mark delivery unknown. A human reviewer should decide whether follow-up is needed; a generated summary saying “disclosure completed” is insufficient evidence.
Ambiguous response: After a required permission question, the caller says, “Fine, but don’t keep my voice.” This is a condition to resolve, not an uncomplicated acceptance. The assistant should explain the verified options or route the issue to staff. The human handler checks whether the requested restriction can actually be honoured before proceeding.
Duplicate callback: A caller asks for a person, disconnects and calls again. An existing callback request may already cover the enquiry. Check the confirmed request before adding another. Where identity or purpose is uncertain, staff should compare the records without merging different customers merely because they share a telephone number.
Verify the opening and the handover separately
Listen to the actual opening through the intended call route. Check audibility, interruptions, supported language wording and what happens when a caller says “person” rather than the scripted phrase. Do not offer a language option without verifying the complete enquiry and handover in that language.
Then test the destination. A transfer request is not proof that a staff member received the call. OpenAI’s function-calling documentation describes model requests followed by application-side execution; successful routing therefore needs evidence from the receiving system. Source: OpenAI function calling
Use the custom AI agent workflow guide to plan these connections. The custom AI agent definition explains the concept; your policy determines what this particular assistant may say and do.
FAQ: voice-agent call openings
Must every call begin with a lengthy AI disclaimer?
Use a brief role statement, a real human option and the applicable privacy notice. Let the organisation’s reviewer determine required wording. Test the complete opening aloud so essential information is understandable rather than buried in a rushed paragraph.
What if the caller immediately asks for a person?
Honour the request through the approved route. Avoid making the caller complete the automated enquiry first. Explain any notice applicable to the handover and confirm the outcome; if nobody is available, offer the verified alternative.
Should the agent repeat the disclosure after a dropped call?
As a proposed rule, disclose again on a new connection because you cannot assume the earlier opening was heard. Check existing service requests separately. Repeating the introduction should not automatically create another callback or reset a caller’s recorded preference.
If your business needs help turning this policy into a practical voice-support brief, get in touch to review the opening, privacy questions and human handover against your actual service setup.