Telnyx × Elacity ECP

Govern Telnyx Voice AI the way you govern your network.

Telnyx already gives you tier-1 carrier infrastructure, programmable voice, and a built-in path to LLM-powered assistants on Telnyx Inference. ECP adds the institutional layer your CISO will ask for next: prompt versioning, per-assistant policy, tool-call RBAC, and an immutable audit trail for every call that runs across your Telnyx number.

Carrier-grade voice deserves carrier-grade governance

Telnyx customers don't tolerate flaky infrastructure — that's why they're on Telnyx. The same standard now applies to AI behavior. When a Voice AI assistant on a Telnyx number quotes a price it shouldn't, commits to a refund policy that doesn't exist, or drifts after a model update, your number — and your brand — is the one on the call. Telnyx delivers the carrier reliability. Elacity ECP delivers the same level of rigor for the instructions the assistant ran on.

What ECP adds to Telnyx Voice AI

Telnyx owns the network and the runtime. ECP owns the governance surface around it.

  • Tier-1 carrier voice network

    Telnyx native
    With ECP
  • Programmable Voice / SIP

    Telnyx native
    With ECP
  • Telnyx Voice AI / Inference

    Telnyx native
    With ECP
  • Call recordings & transcription

    Telnyx native
    With ECP
  • Prompt versioning & rollback

    Telnyx native
    With ECP
  • Per-assistant policy enforcement

    Telnyx native
    With ECP
  • Tool-call RBAC across assistants

    Telnyx native
    With ECP
  • Cross-assistant drift detection

    Telnyx native
    With ECP
  • Model-swap impact assessment

    Telnyx native
    With ECP
  • Immutable instruction-level audit trail

    Telnyx native
    With ECP
  • HIPAA / SOC 2 governance layer

    Telnyx native
    With ECP

Where ECP sits in your Telnyx stack

Telnyx keeps owning the network, runtime, and inference. ECP owns the configuration, policy, and audit surface — entirely out-of-band of the call audio.

Built for teams running Telnyx Voice AI in regulated environments

Prompt registry across every Telnyx assistant

Every system prompt, instruction, voice config, and assistant template — versioned, diff'd, attributed. Roll back any Telnyx Voice AI assistant to any prior state. End the 'who edited the prompt' archaeology.

Per-assistant policy enforcement

Define what each Telnyx assistant can say, ask, quote, or commit to. ECP enforces the rules at configuration time. Guardrails before the call, not after the support escalation.

Tool-call RBAC

Telnyx Voice AI can call out to your CRM, billing, scheduling, internal services. ECP applies role-based access control and produces a signed log of every tool invocation — per assistant, per call.

Drift detection across the fleet

Running multiple Telnyx assistants per business line? ECP baselines them and surfaces behavioral variance — across deploys, model swaps on Telnyx Inference, and prompt edits — before drift turns into a regulatory event.

Immutable instruction-level audit trail

Per-call, ECP logs the exact prompt, model, voice, allowed tools, and policy state the Telnyx assistant was running with. The audit record sits next to Telnyx's call recording and transcript — and it survives a HIPAA, PCI, or SOC 2 review.

Network-grade reliability for the governance layer

Telnyx customers expect five-nines from the network. ECP is built to match that posture — a control plane your platform team can put behind a Telnyx deployment without becoming the new single point of failure.

Why now

Telnyx already vertically integrated voice — owning the network, the runtime, and now the inference layer. The next vertical is governance: who decides what the assistant on a Telnyx number is allowed to say, who can change it, and who can prove what it did. ECP is that layer, and it doesn't require a re-platform.

Get started

  1. Connect ECP to your Telnyx account via API.

  2. Import your current Voice AI assistants and tool definitions.

  3. Set baseline prompts, per-assistant policies, and tool RBAC.

  4. Turn on drift monitoring and call-level audit capture.

Estimated setup: Less than 1 day to your first governance event

Elacity runs ECP internally across roughly 1,000 active agents — including voice assistants delivered over carrier networks. The same control plane we offer Telnyx customers, in production, today.

Telnyx and ECP solve adjacent problems

We get this question on every Telnyx call, so it's worth being explicit. ECP isn't a Telnyx competitor — it's a layer that makes Telnyx Voice AI defensible inside a regulated business.

Telnyx owns the call
Carrier voice, SIP, telephony, STT/TTS, inference, the actual real-time conversation.
ECP owns the configuration
What the assistant on that call is governed to do — prompt version, policy state, allowed tools, immutable audit trail.
ECP never sits in the audio path
Policy resolution and audit writes happen out-of-band. Telnyx's latency and reliability profile is unchanged.

Pricing that scales with you, not against you.

Flat governance capability pricing. Not per agent. Not per call. Not per token.

No per-minute fee. No per-assistant tax. Telnyx scales however Telnyx scales — ECP stays flat.

Frequently asked questions

Built for the regulated businesses running real numbers on real networks.