Skip to main content
Surveys is in beta and available to accounts enabled by the Voxworks team. Speak to the Voxworks team if you would like access.

What is Surveys?

Surveys is where you “Upload, author and publish surveys your AI voice agents run.” You write a questionnaire — sections, questions, answer options, routing rules and outcomes — and Voxworks turns it into an AI interviewer that asks it over the phone, the way a CATI (computer-assisted telephone interviewing) interviewer would. You’ll find it in the sidebar under Outbound Calls → Surveys, between Batch Scheduler and Automations. The entry only appears for accounts that have Surveys enabled. A survey is made of two parts:
  • Your questionnaire — the authored sections and the questions inside them, plus the routing rules, survey variables and outcome codes that decide who is asked what and how the interview ends.
  • A fixed shell — the parts every survey has and that you fill in rather than build: the Agent (who is calling, the voice and the survey-wide defaults), the FAQs, the Behaviours (busy and stop), the Gatekeeper (how the call opens and asks for consent) and the Closing (the farewell and the closing line for each outcome).
You don’t design call flows by hand. When you compile, Voxworks builds an ordinary call script and its flows from the survey. That script is what places or answers the calls, and every answer the respondent gives is recorded back against the survey so you can read it in Results.

How a survey gets from draft to results

A survey has no default voice. Choose one under Voice in the Agent section before you compile — a script compiled without a voice cannot place a call. See Agent section.
Every survey created in the app runs on the voice channel in English. Both are shown read-only on the Readiness tab as Channel and Language. A Voxworks survey runs in both directions — the same compiled script handles outbound calls and respondents who call back.

What a respondent experiences

On every call, the Gatekeeper runs first. It works out who has picked up — a live person, a receptionist or call-screening service, or an answering machine — and asks for consent with your greeting. A “yes” starts the questionnaire; a “no”, a “call me later”, a wrong number or a voicemail ends the call with the matching outcome. Inside the questionnaire the interviewer asks each question in order, following your routing rules. Along the way it:
  • re-reads a question in different words when asked, or when it hears nothing (Avoiding repetition);
  • nudges once on a “don’t know” or a refusal before recording the question as skipped (Attempts and step levels);
  • checks a possible mishearing with a short “did you say…?” (Answer confirmation);
  • answers questions about the call from your FAQs, then returns to the question it was asking;
  • ends the call politely when the respondent is busy or wants to stop (Behaviours).
The interview ends with an outcome code, the closing line you wrote for that outcome, and your farewell (Closing and outcomes).

Question types

Settings every question shares are covered in Question settings.

Permissions

Surveys uses its own permissions. The Owner role has all of them; the Member role has the first three. The team’s primary owner always passes every check. See Roles & Permissions for how roles work.

Next Steps