Campaign - Questions and Misc. Fields

This page is used to define the following type of information:

• An order's campaign can define questions to be posed to customers when an order is taken. For example, you could ask the customer "marketing survey" questions (e.g., please rate our service, how do you heat your home?, etc.).
• An order's campaign can also be setup to capture additional fields to be updated on the order's person / account / premise when the order is completed. For example, you could indicate that the account's override due date and automatic payment options should be captured when an order is taken.
• An order's campaign can also be setup to pose eligibility-oriented questions that qualify the customer for packages of goods and services. For example, you might have a campaign with packages that can only be selected if the customer commits to a year's worth of service.

Open this page using Sales & Marketing, Campaign and navigate to the Question & Misc Fields tab.

Description of Page

Campaign is the user-defined code that uniquely identifies the campaign. The campaign's description appears adjacent.

The Questions & Misc Fields scroll contains one row for each question / miscellaneous field captured on this campaign's orders. The following fields are used:

• Prompt on Order contains the prompt that is shown to the user when the order is taken. Refer to Determine The Properties Of Every Miscellaneous Field for examples.
• Brief Description is simply a brief description of the question / miscellaneous field.
• Sort Sequence controls the order in which the question appears on the order.
• Applicability controls whether the field is Optional , Required, or Only Applicable on Package.
  • A value of Required means the order taker must enter a valid value before packages are displayed for selection.
  • A value of Optional means the order taken can leave the field blank prior to package selection. You can make an Optional field Required on individual packages.
  • A value of Only Applicable on Package is used for fields that are only captured for specific packages. Fields of this type are suppressed prior to package selection. When you setup a package, you indicate if the field is applicable (if so, the user is only prompted for the field if the package is selected).
• Type of Response controls where the field is stored when the order is completed and how it is validated. You have two options: Characteristic or Column.
  • If a field is a Characteristic, you must define which entity the characteristic value is to be stored on when the order is completed ( Person, Account, Premise or Order ). You must also define the Characteristic Type as this controls the characteristic value entered by the user.
  • If a field's value resides in a Column (as opposed to a characteristic value), you must define the column reference. A field's Column Reference controls three things:
• How the field's value is retrieved. A field's value is retrieved when an existing person / account / premise is referenced on an order.
• How the field's value is validated. A field's value is validated before package eligibility is determined and before the order is completed.
• How the field's value is posted (i.e., updated on the database). A field's value is posted when an order is completed.

• If a field's value resides in a Column (as opposed to a characteristic value), you must also define whether the question / field is dependent on the order referencing an account or premise. You do this by populating Question Dependency with one of the following values:
• Select Must Have Account if this question / field should only appear if the order references an account (new OR existing).
• Select Must Have Premise if this question / field should only appear if the order references a premise (new OR existing).
• Select No Dependency if this question / field should always appear.

• Default Column Value / Default Char Value controls whether the order taker is supplied with a default value when an order is created. Note well: for Optional and Only Applicable on Package fields, you can specify a different default value on each package.