# Dial and transfer calls in a sequence

Use **Dial** to call another phone number during a sequence. Use **Transfer** to continue at another call entry or a managed service, such as voicemail.

Dialing places a real additional call and remains subject to calling permissions, destination controls, and charges.

## Connect a caller to a destination

1. Add **Dial** after the menu choice or prompt that leads to your team.
2. Enter a destination with its country code, or map it from eligible earlier data.
3. Set the ringing timeout.
4. Connect the outcomes to the appropriate continuation.

| Outcome   | Meaning and next action                                                                             |
| --------- | --------------------------------------------------------------------------------------------------- |
| Completed | The connected conversation ended and the sequence can continue. Choose a closing message or hangup. |
| Busy      | The destination was busy. Offer another route or voicemail.                                         |
| No answer | The destination did not answer within the attempt. Offer a fallback.                                |
| Failed    | The dial failed and the caller can safely continue. Use a recovery path.                            |

An interruption or uncertain call cleanup can end the run without taking a normal outcome. A connected failure path does not guarantee recovery from every telephone failure. Inspect the run and call records when the caller does not reach the expected fallback.

## Repeat a menu or enter another flow

1. Add **Transfer** on the path that should change entry.
2. Select the destination under **This sequence**.
3. Supply data matching the destination entry's schema.
4. Preview the path through the new entry.

The transfer continues within the same call. It replaces entry data and clears earlier step outputs, so explicitly pass values needed after the transfer. Recording state and call limits continue. Use Transfer for a menu repeat; ordinary connections back to earlier steps are rejected as cycles.

## Use a managed service

Managed destinations that record audio, including voicemail, remain in preview. The runtime checks recording availability when the call runs.

Select an available managed destination in **Transfer** and complete its required fields. The service takes control as a terminal operation. It does not return through an ordinary next-step connection.

For preview, supply the managed transfer's **Completed** sample. That sample does not run the service or create a recording. Use a real test call to verify its audible behavior and artifacts.

## Test the fallback paths

The **Support routing and voicemail** template includes completed, direct-voicemail, and no-answer scenarios. Replace its support number before real testing. Confirm the destination country is enabled under [**Destinations**](https://bird.com/dashboard/w/voice/destinations).

Preview the intended paths, then test with numbers you control. Check both the sequence's selected output and the telephone result in the [call log](/docs/guides/voice/call-log).

## Next steps

- [Use sequence data](/docs/guides/voice/sequences/data).
- [Preview and check a sequence](/docs/guides/voice/sequences/preview).
- [Test with real calls](/docs/guides/voice/sequences/testing).
- [Inspect sequence runs](/docs/guides/voice/sequences/runs).

## Related resources

- [Voice sequences](/docs/guides/voice/sequence-builder) (docs)