Guide

    Create a standard test

    Script a call step by step and check the IVR answers correctly

    Steps

    1. Start on the Dashboard

      There is a shortcut: the New Test quick action on this page goes straight to the create wizard. The sidebar route below is worth knowing anyway, because it is how you reach everything else in Testing.

    2. Expand Testing, then choose Create Test

      The same group holds Test Config, Mission Test Config, Batches, Sweeps and the two results pages. Compliance audits have their own section below.

    3. Pick the Standard test type

      Parameterised is the same idea with variable placeholders instead of fixed data, which is what a sweep needs. Mission hands an AI caller a goal instead of a script. You can change the type later.

    4. Fill in the basics

      The description is optional but worth writing — it is what tells a colleague, or you in six months, what a failure actually means.

    5. Leave call setup on its defaults

      Maximum call length ends the call once it is reached. Flows that collect a lot of detail — a booking needing a name, date of birth and address — rarely finish in three minutes, so raise it for those.

    6. Write the first step

      Match threshold is the minimum similarity required to pass, and timeout is how long the step waits. The defaults, ninety percent and thirty seconds, are a reasonable starting point.

    7. See the four step types

    8. Add a DTMF step to press 1

      This trips people up: a DTMF step will not save with an empty transcript. Give it the prompt the digit is answering. The optional delay sends the digit anyway if the threshold is never met.

    9. Skip or set automation

    10. Check the review page

    11. Create the test

      Creating a test never places a call. Nothing is dialled until you run it.