Skip to main content
Telnyx AI Assistants support multiple speech-to-text (STT) models for transcribing caller audio. The model you choose affects transcription accuracy, supported languages, and response latency. You can also tune provider-specific transcription behavior, such as end-of-turn detection, formatting, keyterm boosting, and Azure region selection.

Available models

deepgram/flux supports English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch. For broader language coverage, use deepgram/nova-3, deepgram/nova-2, azure/fast, assemblyai/universal-streaming, xai/grok-stt, or nvidia/parakeet-v3.

Selecting a model

Portal

In the AI Assistants tab, edit your assistant and navigate to the Voice tab. Select your preferred STT model from the Transcription Model dropdown. AI Assistant Transcription Model Selection When you change models in the Portal, related settings are reset to the defaults for that provider. For example:
  • deepgram/flux supports explicit languages, auto, and multi for its supported languages, and applies Flux end-of-turn defaults.
  • Other Deepgram models enable smart_format and numerals by default.
  • assemblyai/universal-streaming applies AssemblyAI turn detection defaults.
  • azure/fast defaults the Azure region to latency, which auto-selects the closest supported Telnyx-managed region.
  • nvidia/parakeet-v3 uses automatic multilingual transcription.

API

Set the transcription.model field when creating or updating an assistant:
You can also set the transcription language explicitly. If omitted or set to auto, supported models auto-detect the language:

Languages

Supported language options depend on the selected model. If your assistant has a language filter set elsewhere in the Voice tab, the Portal only shows transcription models and language choices that are compatible with that language.

Deepgram settings

Deepgram Flux end-of-turn detection

deepgram/flux is optimized for live voice agents. It provides end-of-turn detection so the assistant can start responding as soon as the caller finishes speaking. It also supports eager end-of-turn, which starts large language model (LLM) processing before the caller fully stops speaking to reduce perceived response latency. When you select deepgram/flux in the Portal, these settings are applied by default: eager_eot_threshold must be less than or equal to eot_threshold. Setting both thresholds to the same value effectively disables eager end-of-turn behavior because the system waits for final end-of-turn confirmation before starting LLM processing.
The eager_eot_threshold field is controlled by the FE-eager-eot-threshold Portal feature flag. When that flag is disabled, the Portal hides the field, but API payloads can still include it if your account supports the setting.
When using Flux, the Portal may also prompt you to lower the assistant’s start speaking plan timings. Flux works best with low start speaking delays, such as 0.1 seconds for wait time and endpointing plan thresholds.

Keyterm Boost

deepgram/flux and deepgram/nova-3 support keyterm, a comma-separated list of terms to boost during recognition. Use it for product names, customer names, acronyms, or domain-specific vocabulary. Keyterm Boost also supports dynamic variables. Use variables when boosted terms are caller-specific, such as a customer name, participant names, account name, or product names passed into the assistant at conversation start.

Smart Format and Numerals

For Deepgram models other than Flux, the Portal exposes these settings and enables both by default when you select the model:

AssemblyAI settings

assemblyai/universal-streaming supports configurable turn detection. When you select it in the Portal, these defaults are applied: min_turn_silence must be less than or equal to max_turn_silence.

Parakeet settings

nvidia/parakeet-v3 supports multilingual transcription with automatic language detection. It does not require provider-specific transcription settings.

Azure settings

azure/fast supports region selection and an optional Azure API key reference. Common Telnyx-managed regions include latency, australiaeast, centralindia, eastus, northcentralus, westeurope, and westus2. Additional Azure regions are available when using your own Azure API key.

Configure advanced settings via API

Create an assistant with tuned transcription settings: