> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Channel behavior

> Prepare response length, formatting, and interaction-budget settings for different text conversation sources.

A short chat reply and a longer support exchange may need different response styles. Channel behavior settings describe those differences without changing the agent's core purpose or permissions.

<Note>
  This guide covers configuration authoring. A channel name in the schema does not establish an available SDK, connector, messaging channel, or live session path.
</Note>

## Define the response style

Per-channel settings live in `conversation_config.agent.text_behavior_overrides`. The map uses supported conversation-initiation source identifiers as keys. Each value can contain:

| Field | Accepted values |
| - | - |
| `verbosity` | `auto`, `concise`, `thorough` |
| `output_format` | `plain_text`, `markdown` |
| `interaction_budget` | `realtime`, `5_minutes`, `10_minutes`, `1_hour` |

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

<Steps>
  <Step title="Identify the actual integration">
    Start with the supported source identifier in the [agent schema](/api-reference/agents-platform/get-agent). Do not invent keys such as your app's display name. Check [deployment guidance](/agents-platform/deploy/web/overview) separately for integration availability.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Save and inspect the map">
    Preserve the current branch configuration, add only the intended overrides, and save a complete [server draft](/agents-platform/deploy/versioning). Read the draft back to check the exact source keys and enum values.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does adding a WhatsApp source connect WhatsApp?" id="faq-channel-connection">
    No. Behavior overrides do not provision or authenticate a channel. Review [WhatsApp availability](/agents-platform/deploy/whatsapp/overview) before planning that integration.
  </Accordion>

  <Accordion title="Do channel settings change access to tools?" id="faq-channel-access">
    No. Response style is separate from workspace permissions, tool attachments, and authorization in the service that owns an action.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.