Sign inGet Started

Preview and check a voice sequence

Use Checks to find definition problems and Preview to follow a path with sample data. Preview does not dial, play audio, record, or create a live run.

Review checks

  1. Open your sequence draft and select Checks.
  2. Follow each finding to its step or field.
  3. Correct missing settings, invalid connections, and unavailable data references.
  4. Check again after editing.
Errors can block publication. Warnings describe uncertainty that needs review, such as a value whose shape cannot be established in advance. Saving an unfinished draft can succeed while checks still report errors.

Preview a path

  1. Select Preview in the editor header.
  2. Choose Call entry and supply Entry data (JSON) matching its schema.
  3. Use Add a sample outcome for the media, pause, keypad, dial, or managed-transfer steps along the path.
  4. Select Preview workflow.
  5. Inspect the visited steps, selected outcomes, prepared inputs, and results.
For a keypad menu, sample a named match, timeout, or unmatched input. For Dial, sample completed, busy, no answer, or failed. These values represent hypothetical results; the preview does not perform the underlying operation.
Change the samples and preview again for each relevant path. A sample left over from a removed node or changed keypad route can invalidate the scenario even when that step is outside the selected path.

Inspect a single step

Select a step, expand its editor, and open Step preview. Select Preview selected step to inspect what that step would receive with the current scenario.
If an earlier action lacks a sample, the selected step may be unavailable. Supply that upstream outcome, then preview again. Expressions using call observations also need a matching execution sample.

Interpret the result

ResultMeaning and next action
CompletedThe sampled path reached an ending. Confirm it selected the intended result.
IncompleteA reached step needs a sample or call context. Inspect the stopping point and add the missing data.
FailedThe path reached a configured failed ending or an unhandled sampled failure. Review whether that is the intended behavior.
InvalidA definition, input, or execution-limit problem prevents the path from continuing. Correct the reported finding.
A failed result can be a valid test of a failure path. A completed result does not prove live audio quality, destination eligibility, or recording storage.
Preview samples are consumed as the path progresses. A transfer that revisits a step can stop at its next unsampled occurrence. Inspect the visited occurrences before assuming the menu can repeat indefinitely.

Save a useful scenario

Select Keep scenario in draft when you want to retain the current samples, then save the draft. Changing the definition or scenario makes the previous result stale; run preview again.
Saved samples are editing aids. Real calls take their data from the call request, caller input, and actual step outcomes.

Next steps

Recursos relacionados

Continúa con la documentación, guías y ejemplos sobre este tema. Los recursos están en inglés.