Skip to main content

Review configuration compatibility

Wirevox is capability-aware. A control can be executed natively by a provider, enforced by the Wirevox pipeline, added to the model as guidance, or inactive for the selected architecture.

Support terms​

TermMeaning
NativeSent to and executed by the selected provider.
WirevoxEnforced by a Wirevox runtime component.
GuidedAdded to model or voice instructions; behavior should be tested because it is not a hard provider control.
InactivePreserved where applicable but not executed by the selected pipeline.

Architecture-level controls​

ControlModularRealtime
System promptWirevox prompt compilerWirevox prompt compiler
Custom greetingWirevox call startWirevox call start
Primary languageWirevox speech sessionWirevox speech session and provider context
Primary voiceNative speech providerNative realtime provider
Speaking speedNative where supported; otherwise guidedGuided through realtime voice instructions
Silence prompt timeoutWirevox lifecycleProvider- or Wirevox-managed by provider
Auto-hangup timeoutWirevox lifecycleWirevox lifecycle
Maximum call durationWirevox lifecycleWirevox lifecycle
Knowledge baseWirevox retrievalWirevox retrieval
RAG thresholdWirevox retrievalWirevox retrieval
Post-call webhookWirevox post-call processingWirevox post-call processing
Audio environmentWirevox media outputWirevox media output

Controls that differ by architecture​

ControlModularRealtime
STT providerNative Modular STT selectionInactive; provider owns recognition
STT patience / response speedNative Modular endpointingInactive; use Realtime turn-taking
Interruption sensitivity in wordsWirevox barge-in thresholdInactive; provider emits interruption events
Filler words to ignoreWirevox barge-in filteringInactive
Secondary languageWirevox language routingInactive
Secondary voiceWirevox TTS routingInactive
Responsive / Balanced / Patient turn-takingInactive; use STT patienceNative provider VAD mapping

Realtime provider differences​

ControlOpenAI RealtimeGrok RealtimeGemini Live
Silence prompt timeoutNativeNativeWirevox lifecycle
KeytermsNative transcription contextNative transcription configurationGuided in session instructions
Pronunciation replacementsGuided in session instructionsNative session settingGuided in session instructions
Reasoning effort controlInactiveNative (none or high)Inactive
Turn-taking presetNative provider VADNative provider VADNative provider VAD

The table describes the current Wirevox implementation, not every feature a provider may expose in its own API.

Voice compatibility​

In Modular mode, the LLM and TTS provider can be selected independently from the compatible voice catalog.

In Realtime mode, the voice must belong to the selected realtime provider:

  • OpenAI Realtime uses an OpenAI-compatible realtime voice;
  • Grok Realtime uses an xAI-compatible realtime voice; and
  • Gemini Live uses a Gemini-compatible realtime voice.

When a Realtime model change also changes provider, the editor selects that provider's default voice. Listen to the result and explicitly choose another compatible voice if necessary.

Modular speech-recognition compatibility​

The current Modular editor can offer:

  • Deepgram Nova-3;
  • Deepgram Flux Multilingual;
  • Gladia; and
  • Cartesia Ink 2 for an English-only configuration without a secondary language.

OpenAI Whisper can appear as Soon and is currently disabled in this selector.

The editor can replace or disable an incompatible STT choice when the primary or secondary language changes.

Understand editor diagnostics​

Compatibility messages can be informational or blocking. Current examples include:

  • secondary-language settings are inactive in Realtime;
  • Modular STT patience is inactive in Realtime;
  • word interruption and filler filtering are inactive in Realtime;
  • Realtime turn-taking presets are inactive in Modular; and
  • a registered Coming Soon model is not available.

Do not copy a diagnostic into the system prompt. Change the architecture or configuration if the behavior is required.

Verification checklist​

After changing architecture, model, provider, language, or voice:

  1. Reopen all affected configuration sections.
  2. Confirm the active model and voice.
  3. Check secondary-language and STT availability.
  4. Review Voice Delivery and Conversation Settings.
  5. Resolve blocking diagnostics and understand informational ones.
  6. Run an interruption, silence, pronunciation, and action test.
  7. Check the draft cost breakdown.
  8. Publish before expecting live calls to use the new configuration.

Next steps​