---
title: Every connection, considered.
subtitle: A clear caller path, from draft to route.
author: IVR Cloud
date: 13 October 2026
---

## Make the caller's next step clear

- Introduce the organization.
- Offer understandable choices.
- Name each outcome explicitly.

::: notes
This is an IVR Cloud design specimen. All example organizations and version numbers are fictional. It is not a customer story or production configuration.
:::

# From draft to phone route

## Publication and deployment have different effects

:::::: columns
::: column
### Publication

- Creates an immutable version.
- Preserves version history.
:::
::: column
### Deployment

- Names a phone route.
- Activates a published version.
:::
::::::

::: notes
Publishing alone does not establish that callers use the new version. The current application exposes deployment separately.
:::

## Keep the version context visible

| State | Version | Meaning |
|:---|:---|:---|
| Draft | v4 | Editable |
| Published | v3 | Immutable |
| Active route | v2 | Used by callers |

::: notes
Version numbers are fictional. A route can remain on an older version after a newer publication exists.
:::

## Keep the three operations distinct

![Illustrative IVR version lifecycle.](ivr-workflow.png)

::: notes
This diagram illustrates separate operations, not actual production state. Names and records in the sample are fictional.
:::

## Show the complete caller path

- Name the root step.
- Label menu and transfer outcomes.
- Explain unconnected steps.

## Make each route change explicit

- Name the number and endpoint.
- Select a published version.
- Verify activation state.

::: notes
Rollback requires an earlier ready deployment. Do not infer readiness from an older publication alone.
:::

## Complete the path before proposing activation

Review missing outcomes, then identify the intended phone route and published version.

::: notes
This slide states the example's next decision; it does not authorize any live change.
:::