Skip to main content

What is Readiness?

Readiness is the third tab in Setup mode of the survey workspace. Its panel is titled Voice readiness: “Validate the selected version before publishing it for voice execution.” Readiness checks the selected version against one set of rules and sorts what it finds into two kinds:
  • Blockers stop the version from compiling and publishing. Fix every one first.
  • Warnings never block. They point at things worth checking before you publish.
The same checks run when you press Validate or Publish in the workspace header, so what you see here is exactly what those buttons act on. When a version has blockers, the header shows “(n) blocker(s) prevent this version from compiling for voice.” with a Review in Readiness button. In the text below, (key) stands for a question key, (rule) for a rule key and (code) for an outcome code — the app shows the real ones.

The tab

While blockers exist, the Compile card shows “Clear the blockers first — a compile of blocked content would only repeat them.”

Blockers

When you press Validate with blockers, the toast reads “1 blocker — fix it before compiling.” or “(n) blockers — fix them before compiling.” When you press Publish, it reads “Publishing is blocked:” followed by the first blocker.

Warnings

Questions

Piped tokens

These name the question and where the token is — its prompt, alternative phrasing (n) or item “(key)” longer form (n) — followed by:
  • “pipes {{…}}, and “x” is not a variable of this survey — the token speaks as an empty string.”
  • “pipes {{…}}, and no rule anchored on an earlier question sets “x” — the token speaks as an empty string.”
  • “pipes {{…}}, but every rule that sets “x” is anchored on a question that can be skipped — the token speaks as an empty string on a call that never asked it.”
  • “pipes {{…}}, which is none of {{survey.<question>.result}}, {{survey.var.<variable>}} or {{contact.<field>}} — nothing substitutes it, so the raw token is spoken.”
  • “pipes {{…}}, and “x” is not a question of this survey — the token speaks as an empty string.”
  • “pipes {{…}}, which is this question itself — the token speaks as an empty string.” / “pipes {{…}}, which is asked later — the token speaks as an empty string.”
  • “pipes {{…}}, but “x” can be skipped — the token speaks as an empty string on a call that never asked it.”
How to fix each is in Survey variables and piping.

Gatekeeper

Voice

The voice warning does not stop a compile or a publish. Always check that a voice is chosen before you run a survey.

Compile errors

Some problems can only be found by building the survey — for example a survey that is very large or very heavily routed. These appear after a compile, on the Compile card as (code) · (question key) — (message), not in Findings. See Validate, compile and publish.