Design a call sequence
Warning: Voice sequences are in preview. Steps, entry data, and the sequence definition format can change in ways that break existing sequences and API requests.
Define the prompts, keypad choices, recording, and ending of a call before configuring its workflow. Use the Voice sequence builder for a saved Bird call flow. If your own application handles the flow, connect it through a SIP trunk.
Define the caller’s outcome
Choose a small, observable result. A service-information menu can offer opening hours on one key and directions on another. Write the response for silence and an unmatched key as well as the main choices.
Keep external business actions in the application or conversational runtime that owns them. A spoken confirmation does not establish that another system booked an appointment or changed an order. Use the AI voice integration guide when the conversation depends on live tools and dialogue.
Map the steps and dependencies
- Name the entry point and each destination. List the phone numbers and external applications that depend on them.
- Write the prompts and prepare the audio. Specify whether a key press should interrupt a prompt or wait until it finishes.
- Define branches for complete keypad choices, silence and unmatched input. Give each branch a destination or an explicit end to the call.
- If the application records a response, specify when capture starts and stops, which audio it captures and whether it needs transcription. Keep sensitive input outside the capture window.
- Check that the selected sequence steps or connected application support the required behavior. Verify input handling, recording, and transfer operations before configuring the workflow.
Keep recording, transcript processing and the telephone outcome separate. The recordings guide covers consent, access and review of the resulting artifacts.
Connect the application
For a Bird sequence, create and save a draft, test its paths, and publish a version. The builder guide covers call entries, simulation, real test calls, and number binding. Editing a draft leaves the active publication unchanged; publishing a paused sequence leaves it paused.
For an external SIP application, configure the connection as follows.
Create a trunk and enable the required calling direction. For incoming calls, enable inbound calling, configure a delivery gateway and point an eligible number at the trunk. The receiving-calls guide covers number routing.
For outgoing calls, enable outbound calling and configure authentication, caller identity and destination access. Use the SIP calling guide to prepare the connection.
Configure prompts and menu behavior in the system that owns the flow. Check the published API, CLI, or MCP reference before using an operation. Call-record reads, sequence authoring, simulation, and real call creation have different effects and permissions. To start a Bird sequence over HTTP, follow Create a voice call.
Test before changing the production route
Use a number you control and an isolated draft or application configuration. The first-call guide covers connection preparation. A sequence simulation places no call; a real draft test does place a call and incurs normal calling charges.
Test recognized input, silence, an unmatched key, interrupted prompts and clean hangup. Verify that each branch reaches its intended response. Check recording and transcript state separately when the workflow uses them.
Coordinate edits during the test and record the configuration tested. Keep the previous application configuration and number route available so you can restore them if the new workflow fails. Restoring routing does not undo a business action already performed.
Verify the calling result
Use the leg log to inspect the telephone outcome. An answered call, a completed menu and a completed business task are separate results. Reconcile Voice events against the leg record when updates are missing or arrive out of order.
Next steps
Related resources
Continue with the documentation, guides and examples for this topic.