Guide

    Create a mission test

    Give an AI caller a goal and let it find its own way there

    Steps

    1. Start on the Dashboard

      The New Test quick action on this page goes straight to the same wizard. The sidebar route is worth knowing anyway, because Mission Test Config lives there too, and that is where the saved test ends up.

    2. Expand Testing, then choose Create Test

      Note the two config pages in this group. Standard and parameterised tests are listed under Test Config; mission tests get their own page, Mission Test Config.

    3. Pick the Mission type

      Choose mission when there is no fixed script to write against: open-ended voice agents, or a flow where the wording changes but the outcome shouldn't. If you already know the exact answers you expect, standard is the stricter and cheaper choice.

    4. Fill in the basics

      The description is optional but worth writing. With a mission test the verdict is a judgement about a conversation, so the note explaining what you were checking is what makes a result readable six months later.

    5. Understand the two halves of a mission

      Sector and mission are free text with a suggestion list behind them — Banking, Insurance, Telco, Utilities and Retail for the sector, and around seventeen common goals for the mission. Start typing and the browser offers them. Type your own whenever the list doesn't fit; nothing is validated against it.

    6. Write a criterion you could grade by hand

      A vague criterion like "the caller is helped" gives the evaluator nothing to hold on to and produces different verdicts run to run. Write the sentence you would use to mark the transcript yourself.

    7. Meet the required field

      Without a profile the agent has no name, no account number and no date of birth to offer, so any flow that asks the caller to identify themselves stalls. Profiles are managed under Data Management, on the profiles page.

    8. Choose a data profile

      The profile is a set of caller facts, not a personality. Voice, above it, is what the caller sounds like; the profile is who they claim to be.

    9. Leave advanced call behaviour alone at first

      Reach for these when a system pauses mid-sentence and your tester talks over it — raise the silence wait — or when it hesitates too long before answering, which is reply eagerness. Changing them changes nothing about whether the mission passes, only how the conversation flows.

    10. Tag it if you'll want to find it later

    11. Read the review page carefully before clicking

      There is no confirmation in front of Save and run. If you only meant to save the setup, use the left-hand button.

    12. Find it under Mission Test Config

      Mission tests are not versioned the way standard ones are, so there is no v1 badge to look for. Find yours by name, or by the tag you just gave it.