Build and edit a voice sequence
Use the sequence editor to connect call steps and configure what callers hear. Start from a template, or open Sequences and select Create sequence > Start from scratch.
Editing requires Voice management write access.
Configure a call entry
- Name the draft and create it.
- Select its Voice call entry and give it a descriptive name.
- Define the entry's data fields if subsequent steps need values from your application.
- Connect the entry's output to the first call step.
A sequence can have several call entries. The caller starts at the entry selected by the API request or inbound number route. An inbound route supplies empty entry data, so that entry must accept {}. See sequence data.
Add and connect steps
- Select + on an outcome and choose the next step.
- Select the step on the canvas to edit its settings.
- Use Expand for the full configuration, available data, and step preview.
- Connect each intended outcome to a next step or an explicit ending.
Use Steps to navigate a larger flow. Moving a step changes its position; connections determine execution order. An output has one destination, and several paths can share a destination.
Review insertion into an existing connection carefully: a step with several outputs needs the correct continuation. Use a connection's action menu to repair its destination or remove it.
Design endings and repeat paths
An unconnected selected outcome can end the flow. Use Hang up to make the call ending explicit, or Finish with a result to record a status, reason, and result object.
Ordinary connections cannot form a cycle. To repeat a menu, use Transfer to a call entry. A transfer starts a fresh data scope and retains the call's execution limits; it does not create an unlimited loop. Follow dialing and transfers.
Disconnected nodes can block publication. Connect them to a call entry or remove them when they are no longer needed.
Save and recover edits
Finish open field edits, select Save draft, and check that the save succeeds. More editor actions contains undo, redo, and JSON editing. Keep JSON for settings that need it; field editors and JSON edit the same definition.
Browser recovery can restore unsaved work in the same browser. It does not save the draft to the server or make it available in another browser. If another editor has saved a newer revision, compare the changes before saving again.
Preview can use unsaved changes. A real draft test uses the saved revision, and production calls use a published version.
Next steps
- Choose sequence steps.
- Use sequence data.
- Preview and check a sequence.
- Publish and manage sequences.
संबंधित संसाधन
इस विषय के लिए डॉक्यूमेंटेशन, गाइड और उदाहरणों के साथ आगे बढ़ें। संसाधन अंग्रेज़ी में हैं।