Understanding Best Practices for Scripts

The following are best practices for using the Script Manager and some important notes on parts not to use.


  • We highly recommend configuring your script so that questions appear one at a time using visible if statements to avoid having to scroll up to the beginning, to avoid skipping questions, and to prevent any confusion for the caller.
  • Always use radiogroups as the standard question type unless other types are needed.
  • Name each question something related to the question instead of leaving it as the default (question1, question2, etc). The question name will show in your script results file as column headers.
  • In the answer section of the question, you'll want to make sure that the "Value" is something you can read instead of the default (item1, item2, etc). That value is shown in your script results file in the column for the question.
  • Each contact widget needs to start with the question name contact_email and contact_text for the two options.


  • Don't use the "Other" option in the answer section. Any text entered into the other field on any question types won't capture what the people type into that other field and will only display the answer name "Other" in reporting. Instead, add an answer option for "other" that leads to a single input question type and then branches to the next question in your script. Notes should only be collected if your program can read every note. 
    • Example DO NOT USE:

  • Don't use the "is required" check. This only adds an * to your script. Only the visible if section makes each question required as your caller clicks answers to move through the script. If multiple questions are showing on the screen, your caller can skip a question regardless if the "is required" is check. 
    • Example DO NOT USE: