Bot configuration
Voxtronics configuration is managed through tenant resources in the Console. Operators create reusable objects and assign them to one or more Bots. The platform validates the resulting graph and compiles the runtime configuration automatically.
Resource model
| Resource | Purpose | Main references |
|---|---|---|
| Provider | AI service and model settings | Vault secret |
| Transport | Provider connection settings | None |
| Modality | Executable AI capability | Provider, transport |
| Persona | Instructions and welcome message | None |
| Function | Tool definition and parameter schema | None |
| Adapter | SIP, HTTP, queue, or pipeline action | Vault secret or other adapter |
| Intent router | Maps an intent or tool call to an adapter | Adapters |
| Policy | Controls tools and call behavior | Functions, adapters, intent router |
| Profile | Defines one call experience | Modalities, persona, policy |
| SIP route | Sends a destination to a Bot and profile | Bot, profile |
Recommended workflow
- Create the Bot and any required Vault secrets.
- Create a provider and transport, assigning both to the Bot.
- Create a modality that uses that provider and transport.
- Create the persona and any functions, adapters, or intent router.
- Create a policy, then a profile.
- Create the SIP route that selects the Bot and profile.
Assignment integrity
Every referenced object must be assigned to every Bot that uses the parent object. For example, a modality, its provider, and its transport must share the same Bot assignment. The same rule applies through policies, profiles, and routes.