This guide covers configuration authoring. A channel name in the schema does not establish an available SDK, connector, messaging channel, or live session path.
Define the response style
Per-channel settings live inconversation_config.agent.text_behavior_overrides. The map uses supported conversation-initiation source identifiers as keys. Each value can contain:
These are requested response settings. An interaction budget is not a billing plan, guaranteed response time, or conversation-retention period.
Prepare a channel-specific draft
1
Identify the actual integration
Start with the supported source identifier in the agent schema. Do not invent keys such as your app’s display name. Check deployment guidance separately for integration availability.
2
Choose the smallest useful difference
Prefer concise plain text for a narrow message surface. Use Markdown only when your application can render it appropriately. Keep instructions about required information and permitted actions in the base prompt.
3
Save and inspect the map
Preserve the current branch configuration, add only the intended overrides, and save a complete server draft. Read the draft back to check the exact source keys and enum values.
4
Prepare comparable examples
Write the same example request for each intended channel. Record the desired length, formatting, and clarification behavior so later runtime testing has a clear expected result.
Frequently asked questions
Does adding a WhatsApp source connect WhatsApp?
Does adding a WhatsApp source connect WhatsApp?
No. Behavior overrides do not provision or authenticate a channel. Review WhatsApp availability before planning that integration.
Do channel settings change access to tools?
Do channel settings change access to tools?
No. Response style is separate from workspace permissions, tool attachments, and authorization in the service that owns an action.