> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions.md).

# Design voice interactions

Design how users experience a Voice Gateway conversation: what they hear, how they respond, how long Voice Gateway waits, and what happens next.

A voice interaction can combine four types of behavior:

| Interaction layer  | What you configure                                       |
| ------------------ | -------------------------------------------------------- |
| Output             | Audio, Text-to-Speech, and playback behavior             |
| Input              | DTMF, speech, or both                                    |
| Pacing and waiting | Silence, processing feedback, and external-service waits |
| Call action        | Continue, transfer, recall, or end the call              |

{% hint style="info" %}
Configure shared behavior at the Voice Gateway level. Use Technical text when an individual Answer needs different behavior.
{% endhint %}

## Default menu behavior

If an Answer does not define a supported interaction property, Voice Gateway uses the configured default `DTMF_VOICE` behavior.

Explicit interaction behavior can include:

* [**DTMF input**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/choose-how-users-respond.md#dtmf-properties)
* [**Voice input**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/voice-input.md#voice-menu-properties)
* [**Combined DTMF and Voice input**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/voice-input.md#combined-input)
* [**Play Silence**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/control-pacing-and-waiting.md#play-silence)
* [**Transfer**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/control-what-happens-next.md#transfer)
* [**Hangup**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/control-what-happens-next.md#hangup)
* [**Recall**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/control-what-happens-next.md#recall)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
