Telnyx Platform Deep Mastery 2026-02-26

description: Comprehensive Telnyx platform mastery covering all capability domains: AI Assistants, Call Control, Messaging, Numbers, WebRTC, Storage, and MCP integration.

source: RLM ingestion from developer docs, API audit, live account inspection, and web research


Telnyx AI Assistants API

list: GET /v2/ai/assistants

create: POST /v2/ai/assistants

get: GET /v2/ai/assistants/{id}

update: PATCH /v2/ai/assistants/{id}

delete: DELETE /v2/ai/assistants/{id}

sms_chat: POST /v2/ai/assistants/{id}/chat (SMS conversational)

web_chat: via widget or API

test_suite: Built-in test suite for assistants

canary: Canary deployments with traffic splitting

versioning: Multiple versions per assistant with A/B testing

scheduled_events: POST /v2/ai/assistants/{id}/scheduled_events — schedule calls/SMS

knowledge_bases: Upload files or URLs, drag-drop in portal, no-code setup

groups: Insight groups for conversation analytics

webhooks: Post-call insight delivery via webhooks

memory: use_insights_for_memory for persistent cross-call memory

widget_settings: Embeddable web widget with theme, colors, position, branding

outbound_calls: POST /v2/texml/ai_calls/{texml_app_id}

api_coverage: 95% — nearly everything configurable via API except master telephony toggle (portal only)

notes: 54 models available, 32 assistants on our account, 9 AU phone numbers


Telnyx AI Assistant Tool Types

type: webhook

description: HTTP API calls to external systems

config: url, method, headers, body_parameters, async flag, timeout_ms

async_mode: AI continues talking while webhook fires — critical for CRM writes

sync_mode: AI waits for response — use for availability checks

type: hangup

description: End the call gracefully

config: Simple toggle, LLM decides when to use

description: Transfer to another AI assistant mid-call

unified: Same voice, seamless, user unaware of switch

distinct: Different voice, explicit transfer announcement

config: target_assistant_id, mode, description for LLM

type: transfer

description: Transfer call to named SIP target or phone number

config: target, description

description: SIP REFER-based transfer

config: target SIP URI

description: Send DTMF tones for IVR navigation

config: digits string

description: Model Context Protocol integration for extended tool access

config: name, url, api_key_ref

transport: SSE (Server-Sent Events)

note: Passes telnyx_conversation_id in _meta of every request

enterprise_integrations: Salesforce ServiceNow Jira HubSpot Zendesk Intercom GitHub Greenhouse


Telnyx Voice Configuration

tts_providers: Telnyx NaturalHD (2287 voices, zero additional cost)

stt_providers:
Telnyx (Whisper)
Deepgram (flux model — recommended)
Azure

style: Australian female, warm professional

recommended: YES — default for all AU business receptionists

style: Australian male, professional

use: Male persona agents

Slow, deliberate — complex info delivery

Natural professional — RECOMMENDED DEFAULT

Standard pace

Snappy, energetic

wait_seconds: Baseline pause before responding (0.3=snappy, 0.4=natural, 0.6=polite, 1.0+=IVR)

on_punctuation: After period/question (0.1=minimal)

on_no_punctuation: Mid-sentence handling (1.5=dont interrupt)

on_number_seconds: Digit sequence handling (1.0)

background_audio:
silence
office
custom URL

recommended_model: deepgram/flux


Telnyx AI Model Catalog

advantage: Lowest latency, no API key cost, MoE architecture

recommended_for: Default for all SubAIVA agents

advantage: Massive context for knowledge-heavy use cases

advantage: Best reasoning, highest quality

advantage: Fast and low cost

decision_tree: Lowest latency + no key = Qwen3 | Large KB = Gemini Flash | Best quality = Opus | Cheapest = Flash Lite


Telnyx AI Assistant Memory System

description: Telnyx provides native cross-call memory via Insights + dynamic variables webhook

insight_memory: Set use_insights_for_memory: true — assistant recalls previous call insights

phone_linking: Omnichannel — links memories to phone number across calls and SMS

query_language: Flexible query mirroring List Conversations API — filter by user, timeframe, metadata

custom_metadata: Webhook can inject custom metadata fields, future queries can filter on them

insight_filtering: Can limit retained info to specific insight IDs for granular control

purpose: Telnyx calls this URL at conversation start to inject context

timeout: 1 second — if fails, call proceeds best effort

receives: conversation_id, channel_type, agent/user numbers, STIR/SHAKEN status

returns: JSON with custom variables available as {{var_name}} in instructions

our_implementation: Genesis Voice Bridge MCP server provides memory via Supermemory, Qdrant, PostgreSQL, and FalkorDB — deeper than Telnyx native memory


Telnyx Call Control API

description: Full programmable voice control — answer, bridge, dial, transfer, record, gather, speak, fork, stream

answer: POST /v2/calls/{id}/actions/answer

bridge: POST /v2/calls/{id}/actions/bridge

dial: POST /v2/calls — initiate outbound call

transfer: POST /v2/calls/{id}/actions/transfer

record_stop: POST /v2/calls/{id}/actions/record_stop

speak: POST /v2/calls/{id}/actions/speak

send_dtmf: POST /v2/calls/{id}/actions/send_dtmf

fork_start: POST /v2/calls/{id}/actions/fork_start

fork_stop: POST /v2/calls/{id}/actions/fork_stop

hangup: POST /v2/calls/{id}/actions/hangup

features:
Answering machine detection
DTMF (RFC 2833)
Conference calling
Media streaming (WebSocket)
Real-time transcription
Dual-channel recording
Custom storage (S3/GCS/Azure)

description: XML-based call control for complex call flows

endpoint: POST /v2/texml/ai_calls/{texml_app_id}

api_coverage: 100% — all call control operations available via REST API


Telnyx WebRTC Widget & SDKs

element: <telnyx-ai-agent>

jwt: Backend token exchange for production security

theme: light/dark

audio_visualizer: color, preset (roundBars)

text: start_call, thinking, interrupt text

position: fixed/inline

state: collapsed/expanded

branding: logo_icon_url, custom colors

install: npm install @telnyx/ai-agent-lib

features:
Real-time transcription
Connection management
Conversation state
Event handling
Text messaging during call
Image upload (vision models)

use: Direct low-level control for custom implementations

features:
Customizable dimensions
Icon-only mode
Multiple UI states
Audio visualizer
Theme support
Call controls
Transcript view

repo: team-telnyx/ios-telnyx-voice-ai-widget

features: audioVisualizerColor userBubbleBackgroundColor agentBubbleBackgroundColor widgetSurfaceColor

repo: team-telnyx/telnyx-webrtc-android

cost: $0.002/min for browser WebRTC (vs $0.06/min for conversational AI phone calls)

demo_spore: Anonymous login, zero backend, hardcoded assistant ID per niche domain

production_scale: JWT token exchange, per-client SubAIVA, usage tracking, rate limiting


Telnyx Phone Number Management

order: POST /v2/number_orders

list_owned: GET /v2/phone_numbers

get_detail: GET /v2/phone_numbers/{id}

update: PATCH /v2/phone_numbers/{id}

advanced_order: POST /v2/number_orders (advanced — manual sourcing)

requirement_groups: GET /v2/requirement_groups

identity: Name, last name, contact phone, passport/ID copy

address: Australian address + proof dated within 3 months

processing: ~72 hours after documentation received

identity: Same as local

address: Worldwide address + proof within 3 months

identity: Name, last name, contact phone (no ID copy)

address: Worldwide address

identity: Name, DOB, company name, local ID verification

address: Australian address + utility bill under 3 months

extra: Must declare number of other activated prepaid services

process: Submit porting request, identity verification, carrier coordination

note: Complex services on number cancelled during porting

number_reservation: 30-minute hold available (not all numbers support this)

api_coverage: 90% — search, order, manage all via API. Regulatory docs may need portal upload.


Telnyx Messaging API

sms: Send/receive SMS globally

mms: Send/receive MMS with media attachments (number must be MMS-enabled)

ai_sms_chat: AI assistants can engage in SMS conversations natively

send_message_tool: send_message tool allows AI voice agents to send SMS during/after calls

scheduled_sms: Via scheduled_events API on AI assistants

send: POST /v2/messages

get: GET /v2/messages/{id}

list: GET /v2/messages

messaging_profiles: GET/POST/PATCH /v2/messaging_profiles

e164: All numbers must be E.164 format (+61...)

messaging_profile: Numbers must be assigned to a messaging profile

10dlc: Required for US messaging to external carriers (not needed for AU)

on_net: No carrier registration needed for Telnyx-to-Telnyx

sdks: Node Python Ruby Go Java .NET PHP

whatsapp: Available via third-party integrations (Zapier, Invent), not native Telnyx API

api_coverage: 95% — full SMS/MMS via API, WhatsApp requires third-party connector


Telnyx Cloud Storage

description: S3-compatible cloud storage for recordings, files, and CDN

buckets: Unlimited buckets, no extra charges

file_types: Any file type supported

s3_compatible: Point S3-centric apps at Telnyx endpoints

public_buckets: Publicly accessible buckets for CDN use

ssl: Custom SSL certificates for public domains

recording_storage: Call recordings can be stored in own S3/GCS/Azure buckets

create_bucket: POST /v2/storage/buckets

list_buckets: GET /v2/storage/buckets

upload: PUT /v2/storage/buckets/{name}/{key}

download: GET /v2/storage/buckets/{name}/{key}

delete: DELETE /v2/storage/buckets/{name}/{key}

list_objects: GET /v2/storage/buckets/{name}

default: Stored in Telnyx-owned S3, download links expire in 10 minutes

custom: Configure own S3/GCS/Azure via POST /v2/custom_storage_credentials/{app_id}

webhook: call.recording.saved delivers metadata with recording URL

channels: single dual

cdn_use: Public buckets with SSL = cost-effective CDN for voice recordings, demos, assets

api_coverage: 100% — fully API-driven, S3-compatible


Telnyx MCP Integration (Dual)

description: Telnyx AI Assistants can call external MCP servers as tools during conversations

auth: Bearer token via api_key_ref integration secret

conversation_id: Passed in _meta of every MCP request

portal: AI Assistants > MCP Servers tab

api: mcp_servers array in assistant payload

genesis-memory-bridge

status: Configured but using rotating Cloudflare tunnel URLs

issue: URLs break on tunnel restart — need persistent domain

description: Official Telnyx MCP server for Claude Desktop / Cursor / agents to control Telnyx

repo: github.com/team-telnyx/telnyx-mcp-server (Python — DEPRECATED)

tools: Make calls, hang up, transfer, play audio, send DTMF, TTS

tools: List/purchase phone numbers, update configs

tools: Cloud storage: create buckets, upload/download files

install: uvx or npm, configure in claude_desktop_config.json

webhook_support: ngrok integration for receiving Telnyx webhooks

description: Our custom MCP server exposing Genesis memory to Telnyx AI assistants

backends:
PostgreSQL (Elestio)
Qdrant (vectors)
Redis (cache)
Supermemory (semantic)
FalkorDB (knowledge graph)

auth: Bearer token middleware

transport: SSE and Streamable HTTP


name: Telnyx AI Assistant Versioning & Canary Deployment

description: Create multiple versions of an AI assistant, A/B test, and gradually roll out changes

version_management: Create and manage multiple versions of same assistant

canary_testing: Route portion of traffic to new version while keeping rest on stable

performance_comparison: Compare versions in real-world environments

gradual_rollout: Scale up new version based on performance metrics

isolation: Each version has its own prompt, model, tools, settings

workflow: 1. Create new version with changes → 2. Route 10% traffic via canary → 3. Monitor insights → 4. Scale to 100% or rollback


Telnyx AI Assistant Scheduled Events

description: Schedule automated SMS or calls from AI assistants

use_cases:
Follow-up calls after service visits
Appointment reminders
Payment reminders
Satisfaction surveys
Seasonal check-ins

integration: Works with AI assistant context — scheduled event triggers the assistant which can use tools


Telnyx Enterprise CRM Integrations

native_integrations: Salesforce ServiceNow Jira HubSpot Zendesk Intercom GitHub Greenhouse

zapier_mcp: Connect to thousands of apps via Zapier MCP server

webhook_custom: Any system with REST API can be integrated via webhook tools

ghl_pattern: Use webhook tool with GHL endpoint: https://services.leadconnectorhq.com/hooks/{LOCATION_ID}/webhook-trigger/{TRIGGER_NAME}


Telnyx Cost Structure 2026

phone_calls: $0.06/min (includes STT + TTS + inference for native models)

webrtc_browser: $0.002/min (browser-to-brain, no phone infrastructure)

outbound_calls: Varies by destination, check rate cards

inbound: Varies by number type and region

outbound: $0.01-0.03/min for AU domestic

recording: Included in call cost, storage extra if using own S3

au_local: ~$1-2/mo per number

au_toll_free: ~$3-5/mo per number

au_mobile: Higher, varies

sms_au: $0.04-0.08 per segment

mms: Higher, varies by media size

buckets: Free (unlimited)

storage: $0.023/GB/mo (S3-compatible pricing)

bandwidth: Varies

native_qwen3: $0/min additional (included in conversational AI rate)

external_models: Billed by token via your own API key (not Telnyx cost)

use_qwen3: For default agents — no API key cost, lowest latency

use_webrtc: For demos/websites — 30x cheaper than phone calls

batch_provisioning: Order numbers in bulk for volume discounts

own_storage: Use Telnyx storage instead of external S3 for recordings


Australian Number Provisioning Workflow

type: workflow

description: Step-by-step process to provision a new AU phone number for a customer

action: Create Requirement Group

api: POST /v2/requirement_groups

country_code: AU

phone_number_type: local

action: ordering

note: Pre-fill regulatory docs once, reuse for all AU orders

action: Upload Regulatory Documents

method: Portal upload or API

docs_needed: Australian address proof (utility bill, bank statement) dated within 3 months

processing: ~72 hours for validation

action: Search Available Numbers

note: For Cairns: starts_with=6174, Brisbane: 6173, Sydney: 6129, Melbourne: 6139

action: Reserve Number (Optional)

api: POST /v2/number_reservations

hold: 30 minutes

action: Order Number

api: POST /v2/number_orders

requirement_group_id: from step 1

action: Assign to TeXML App

api: PATCH /v2/phone_numbers/{number_id}

action: Create/Update AI Assistant

api: POST or PATCH /v2/ai/assistants

action: Verify End-to-End

checks: Call the number, verify assistant answers

checks: Check enabled_features contains telephony

automation_potential: Steps 1-7 fully automatable via API. Step 2 may need portal for document upload. Step 8 can be automated with test calls.


type: analysis

name: Telnyx Portal-Only Operations (Browser Use Required)

operation: First-time telephony enablement

reason: Master telephony toggle cannot be enabled via API — portal UI required

workaround: Use Collaborative Browser Handoff — human logs in past Cloudflare, AI enables toggle

operation: Regulatory document upload

reason: Identity/address verification documents for AU numbers

workaround: Can prepare requirement_groups via API, but doc upload needs portal or support ticket

operation: MCP server URL updates

reason: When Cloudflare tunnel rotates, need to update MCP server URL in portal

workaround: Use persistent tunnel domain to avoid this entirely

operation: Account billing changes

reason: Payment method, plan changes

workaround: Not needed for operations, only for billing

operation: API key creation

reason: New API keys require portal login

workaround: Existing key works for all operations

operation: Portal login

reason: Blocked by Cloudflare Turnstile — requires human authentication

workaround: Collaborative Browser Handoff protocol

fully_api_operations:
All assistant CRUD
All phone number search/order/manage
All call control operations
All messaging operations
All storage operations
Model listing and selection
Integration secrets management
Outbound call triggering
Webhook tool configuration
Widget settings
Insights configuration
Scheduled events
Canary deployment/versioning