TOBi managed LLM

TOBi (type vodafone_tobi) is a managed LLM integration, not a modular STT/TTS vendor. The platform hosts the conversational brain; your flow configures how Delphi forwards SIP context to the bot and which managed actions (transfer, hangup) the bot may trigger.

Rendered on the canvas as the Managed LLM node.

⚑Feature required: additionalProviders

This feature is gated. Operators enable it per deployment in the Delphi Portal; if the flag is off, the surface described below is hidden from the UI and rejected by the API. See Feature flags for the full registry.

Pipeline role

Stage	TOBi
STT / TTS / Realtime	Not configured here — handled by the managed integration
LLM	vodafone_tobi in pipeline LLM slot or Managed LLM node

Key fields

Field	Description
Base URL	Vodafone chatbot API host (with or without /v1/chatbot path suffix)
Client ID / Client Secret	OAuth-style credentials via team variables
Bot name	Managed bot identifier
Callback / response paths	Advanced routing for bot callbacks
Channel Data Forwarding	SIP header → bot context rules — see SIP header context rules
DTMF defaults	Managed DTMF collection defaults for the integration

Managed transfer and hangup actions are configured on the Managed LLM / Managed action inspectors and validated at runtime against platform egress and transfer restrictions.

TOBi often sends multiple text messages before hangup; pipeline mode plays them in order and defers hangup until speech finishes. See Speech playback and hangup.

API reference

Bot callback payloads (transferTarget, hangupSipHeaders, failover, and related fields) are documented in Managed callback actions.

See also

• Speech playback and hangup — multi-message TTS queue and hangup timing for managed integrations
• SIP header context rules
• Managed callback actions
• Providers overview
• Egress trunks — outbound transfer routing