Voice · Coming Soon

Agentix Voice is coming soon

Voice is being prepared as a public Agentix product for defined business call workflows.

What Voice is intended to solve

Voice is intended to help a business operate a defined call workflow without implying unrestricted autonomy.

01
Work within a defined business purpose.
02
Keep agent provisioning, number binding and provider routing as separate steps.
03
Keep human responsibility over actions that change the runtime environment.

The evidence below applies to managed deployments; public product access remains Coming Soon.

01
An administrator can execute an approved provisioning action that creates a provider-side voice agent and leaves it paused.
02
An existing imported number can be bound in Agentix as a separate database step; binding does not change provider routing.
03
Provider routing changes only through a separate approved attach action with provider read-back.
04
Protected Console pages display call records and transcripts when the data is present.

The following capabilities are not part of the current public product:

01
An administrator creates or selects a draft agent.
02
Provisioning requires a matching approval and creates the provider agent in a paused state.
03
An existing imported number is bound in Agentix; provider routing is still unchanged.
04
A separate approved attach action changes provider routing and verifies the provider read-back.
05
Call records and transcripts are reviewed through protected Console routes and applicable permissions.

01
Each managed deployment starts from a bounded business configuration.
02
Provisioning and provider routing remain separate administrator actions with approval gates.
03
Console visibility depends on the user’s role and the data available for each call.

Agent Firewall’s currently proven public scope is supported WhatsApp inbound automated replies.

This page does not present Voice calls as a path currently protected by Agent Firewall.

01
Managed Voice provisioning uses ElevenLabs.
02
Other provider names shown in the Console catalog are examples, not selectable Voice integrations.
03
The voice_llm routing row can be stored, but it has no live Voice call site.
04
The Console can store a per-language voice ID and an eleven_v3 preference; the current wizard does not apply them to the live Voice runtime.
05
TTS and STT run implicitly inside the ElevenLabs-managed runtime; they are not standalone public products.

Existing Voice deployment is assisted and approval-gated.

It is not a public self-service flow.