Call Controls, Privacy and Compliance

On every call

AI disclosure at the start. The agent speaks first, says it is an AI and offers to hand over to a person. Keep that in your workflow (see the authoring guide), and test it in every pilot call.
It never claims to be human. Asked “are you a robot?”, it answers truthfully.
It does not take payment details by voice.
It does not pretend to transfer. If asked for a person, it says someone will call back.
It ignores caller instructions to change its rules.
No prices, valuations, legal or loan advice beyond locked content. Put such answers in hard-locked response nodes.

These are properties of the agent’s workflow, so they are only as good as the workflow you publish. They are the recommended rules for any voice agent and the pilot acceptance tests.

What is stored

Audio is not recorded or stored by Wetel by default. Speech is processed live by speech and language services.
Conversation text is part of the session record, exactly like chat. Treat it as you would a chat transcript.
Usage is metered with the session (speech and model usage).
The join token carries a session credential and is readable by the caller’s browser. See the security note.
If you record calls, the recording notice and the consent are yours to give and keep.

What Wetel does not offer

Cold outbound sales calls, meaning calls to people who did not ask to hear from you. This is Wetel’s policy, not a missing feature.
Voice cloning of real people.

What is in scope: calls the person starts (inbound, the only kind that works today) and, later, callbacks the person asked for and follow-ups with people who already have a relationship with you and agreed to be called, always disclosed as AI. Callbacks and follow-ups are at specification stage, not built, and have no date. Any outbound call will also depend on the local rules on calling people and on the telecom provider’s terms.

What stays with you

Telling callers they are speaking to an AI, in the language they speak.
Consent and notice for any recording you make.
Local rules on calling and contacting people, which differ by country.
A written human fallback for the pilot.
Authenticating your own callers before you start a call for them, and rate-limiting your own start endpoint.

Not available yet

Call records and per-call reports, per-call spending limits, and an enable switch per workspace are planned. Ordinary phone numbers (including Malaysian +60 numbers), SIP, WhatsApp calling, outbound calls, live transfer to a person and joining online meetings are not available. Wetel does not record call audio; what a call leaves behind is the session record, and no separate retention period for call data is published yet.

The per-key daily call cap is built, not planned: sdkStartVoiceCall refuses a key’s call requests past 1,000 per UTC day by default (one limit per environment, the same for every key; Wetel can raise it or turn it off). The refusal is INTERNAL_SERVER_ERROR with extensions.status 429 and the message Daily voice call limit reached for this API key; try again tomorrow (UTC). The cap is in the production code too, but voice calls themselves are still off in production, so in practice it applies only where calls are enabled: staging, on request.