Skip to main content

Overview

Select a question in the Outline on Setup → Questions and its settings open in the inspector on the right. This page covers what the question types have in common. Each type’s own page covers the settings only that type has. The inspector only shows settings that mean something for the selected type — change the Type and the form changes with it.

The top of the inspector

If you rename a key that rules use, the inspector warns ”… Renaming updates them too.” and the rules are updated when you save.

Question types

Other question types can arrive through an import (multiple choice, short text, email, date, matrix and so on). The voice interviewer can’t ask them: the inspector shows “Not supported for voice. The question can be read and deleted; its type cannot be changed here.” Delete them or rebuild them as a supported type.

Voice prompt

Voice prompt is the question as the interviewer says it — “What the agent reads out”. It’s required: the save button reads “Add a voice prompt to save.” until there is one. Write it the way you would say it on the phone. A few rules of thumb:
  • End a question with a question mark. When a Single choice, Rating or Long text prompt has no ?, the interviewer adds ” — what would you say?” so the respondent knows it’s their turn — unless Statement prompt is on (see below).
  • Don’t read the options in the prompt on a Single choice or Rating question. The interviewer reads them after the prompt, introduced by the Options lead-in.
  • Keep it to what a person can hold in their head. Long preambles belong in a section’s Intro line or a Display question.

Inserting earlier answers and variables (piping)

“Type / to insert an earlier answer, a variable or a contact field.” The picker offers: Only questions before this one in the survey are offered, and Display questions are never offered because they record nothing. A piped value is spoken as text. If the value is empty on the call — the earlier question was skipped, or the contact has no first name — the respondent hears the sentence with a gap. Readiness warns about piping that can come up empty. See Survey variables and piping.

Alternative phrasings

Alternative phrasings — other ways of asking the same question, one per line, up to 20. “One per line. The agent always asks the first time in the prompt above; when it has to ask again — after a question, or a re-read — it picks between the prompt and these, so it does not repeat itself word for word.” The first read is always the voice prompt exactly as written. Every later read — a re-ask after silence, the return after an FAQ or a “can you call me back?” detour, a clarify line or a nudge — picks at random from the prompt and these phrasings. Two or three good alternatives per question make the interviewer sound far less robotic. Not shown on Display. See Avoiding repetition.

The Voice panel

Click Voice to expand it. It holds how the interviewer listens and confirms.

Writing context

Write Context for the matcher as matching rules, not as a description of the question. For example:
“Every day” is Daily; anything from a few times a week down to rarely is Less often. “Not sure” is the separate Don’t know answer. Refusing is a recorded answer, not a screen-out.
If you leave it empty, any help text or interviewer instruction that came in with an import is used instead.

Keyterms versus “Often heard as”

  • Keyterms pull the recogniser towards a spelling. Use them for real words it might not know — a council, a street, a product.
  • Often heard as lists what the recogniser writes when it gets a word wrong — for example “can send” for concerned.
Never enter a mishearing as a keyterm. A keyterm makes the recogniser more likely to produce that exact text, so a misspelling added as a keyterm makes the mistake more common, not less.
The survey-wide Keyterms in the Agent section apply to the whole call; a question’s keyterms apply while that question is being asked.

The Behaviour panel

Click Behaviour to expand it. Display questions show only the step levels. Each cap and level is explained, with guidance, in Attempts and step levels. If Required is on and Decline is 0, the inspector warns: “Required questions nudge a refusal at least once, but decline nudges is 0 in Behaviour. Raise it to 1 or turn Required off.”

Saving

  • Add question (a new question) or Save changes — reads Saving… while it saves. Toasts: “Question added”, “Question saved”.
  • Cancel discards a new question; Delete removes an existing one (toast “Question deleted”). A question in use by rules or variables, or with recorded answers, can’t be deleted — see Questions tab.
On a read-only version, the inspector shows the stored values instead: “This version is read-only. Create a Voxworks copy to edit it.”

What happens when the interviewer asks

Every answerable type follows the same pattern, with the details varying by type: When a question is skipped the interviewer moves on gracefully — “That’s okay, let’s move on.” If the question’s own setup can’t run on the call, the respondent hears a brief apology and the survey continues (or screens them out, if Screen out if the question cannot be run is on). How the interviewer tells an answer apart from an FAQ or a detour is covered in Answers given early and interruptions.

What every question records

Each question writes these custom variables on the call. <key> is the question key in lower case, with spaces and punctuation turned into underscores — so a question keyed Q3 records survey.q3.result. Later prompts can speak {{survey.<key>.result}}, and routing rules read the answer directly. After the call, answers are stored against the survey session and appear in Results and in the CSV export’s answer column. See Survey variables and piping and Responses and export.

Next Steps