> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/product-reference/dialogue-studio/dialogue-studio-example-flows.md).

# Dialogue Studio example flows

Find the Dialogue Studio example scenario that matches your use case, with prerequisites, importable flows, and configuration steps.

Use this page to find a Dialogue Studio example that matches what you are trying to build, and to evaluate example flows as starter templates that you can adapt for your own service design.

The current product can include multiple bundled examples. Treat the named examples on this page as current starter templates, not as a fixed catalog for every release.

## Scenario gallery

Each scenario below is a standalone page with prerequisites, an importable flow where one exists, node-by-node configuration steps, and verification steps. Scenarios without a complete importable flow (SSML, the catch node, and Google Dialogflow) are documented as node-by-node build instructions instead, so the flow is not fabricated.

### Basic

* [Simple IVR](/product-reference/dialogue-studio/dialogue-studio-example-flows/simple-ivr.md) - a DTMF menu that routes callers to Sales or Support skills.
* [Simple chatbot](/product-reference/dialogue-studio/dialogue-studio-example-flows/simple-chatbot.md) - a multi-channel chatbot that greets customers and routes keyword-matched requests to an agent.
* [Simple voice bot (with Azure OpenAI)](/product-reference/dialogue-studio/dialogue-studio-example-flows/simple-voicebot-with-azure-openai.md) - a voicebot that transcribes a caller's question and answers it using Azure OpenAI.

### Advanced

* [Last agent routing](/product-reference/dialogue-studio/dialogue-studio-example-flows/last-agent-routing.md) - remembers each customer's last agent and skill, and offers to route them back on their next contact.

### Integrations

* [Connect to Azure OpenAI](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-azure-openai.md) - store Azure OpenAI credentials in global configuration and send a chat completion request.
* [Connect to Google Dialogflow](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-google-dialogflow.md) - connect a voicebot to a Google Dialogflow agent for intent detection.
* [Connect to Microsoft Dynamics 365 as an application user](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-dynamics-365-application-user.md) - authenticate as an application user and search for a Dynamics 365 contact.
* [Connect to Microsoft Graph as an application](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-microsoft-graph-application.md) - authenticate as an application and search Microsoft Graph for a user.
* [Connect to SharePoint sites and lists with Microsoft Graph](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-sharepoint-with-microsoft-graph.md) - use Sites.Selected application permissions to read, update, and create SharePoint list items.
* [Connect to ServiceNow](/product-reference/dialogue-studio/dialogue-studio-example-flows/connect-servicenow.md) - look up and create ServiceNow incidents for a self-service chat or voice bot.

### Tricks

* [Configure SSML](/product-reference/dialogue-studio/dialogue-studio-example-flows/configure-ssml.md) - generate SSML markup in a function node and play it with the Say node's SSML method.
* [Configure a catch node](/product-reference/dialogue-studio/dialogue-studio-example-flows/configure-catch-node.md) - catch an Enqueue node error and fall back to a working skill.

{% hint style="warning" %}
Every imported flow asset in this gallery contains blank placeholders for credentials (API keys, client secrets, service account keys, usernames and passwords). Enter real values using your organization's approved secret handling process, and never leave a real secret in a flow you export, share, or debug.
{% endhint %}

## Use examples as starting points

Treat example flows as reusable templates, not as finished production solutions.

Before you rely on an example:

1. Import the example into a controlled environment.
2. Review the prompts, routes, dependencies, and external connections it expects.
3. Replace the environment-specific values with the values for your own service.
4. Test the flow end to end before you expose it to production traffic.

{% hint style="warning" %}
Do not assume that an example flow is production-ready immediately after import. Imported examples still require environment-specific configuration, validation, and operational ownership.
{% endhint %}

## Built-in examples

The product can also include ready-made examples inside Dialogue Studio itself, separate from the scenario pages above.

### Evaluate the Call Park example

The Call Park example is useful when you want a starter design for parking a call and later retrieving the parked call.

When you adapt the example:

* bind it to the correct queue, route, or skill context
* confirm which prompts and retrieval paths apply to your environment
* replace any placeholder values with the values for the target service
* test both the park and retrieval paths before go-live

### Evaluate the Live Translation example

The Live Translation example is useful when you want a starter design for a flow that depends on transcription and an external translation path.

When you adapt the example:

* confirm the required transcription and translation dependencies first
* define the source and target language behavior for the target service
* test the supported language path with the same conversation model you plan to use in production
* confirm how the flow behaves when the translation path fails or returns no usable output

## Decide whether an example belongs in production

An example flow is a good starting point when it:

* demonstrates a pattern that matches your target use case
* reduces the amount of flow structure you need to build from scratch
* can be validated and owned by the administrators who support the service

An example flow is not enough on its own when it:

* depends on unverified legacy configuration assumptions
* hides important environment-specific dependencies
* needs substantial redesign before it matches the production service

## Verification

1. Confirm the example is available in the current environment before you plan around it.
2. Confirm all environment-specific values are replaced before you test the flow.
3. Test the main success path and at least one failure or fallback path.
4. Confirm the adapted example has a named owner who will maintain it after import.
5. Confirm the final production flow does not depend on undocumented example-specific assumptions.

## Related topics

Go to **Apply Dialogue Studio scenario patterns** for reusable design patterns that often sit behind imported examples.

{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/1aeml1BpvC79ocfNQlEt" %}
[Apply Dialogue Studio scenario patterns](/contact-center-configuration/building-your-callflow/via-dialogue-studio/apply-dialogue-studio-scenario-patterns.md)
{% endcontent-ref %}

Go to **Configure advanced Dialogue Studio features** for the AI-driven and settings-driven capabilities that some examples may depend on.

{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/tVbNw2DZ0Mb6w6i0kFlM" %}
[Configure advanced Dialogue Studio features](/contact-center-configuration/building-your-callflow/via-dialogue-studio/configure-advanced-dialogue-studio-features.md)
{% endcontent-ref %}


---

# 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://atlas.anywhere.now/product-reference/dialogue-studio/dialogue-studio-example-flows.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.