From Bright Pattern Documentation
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Contents

Lists Tab

Associations between an outbound campaign and its calling lists are configured in the Lists Tab. The upper part of this tab displays the calling lists associated with the selected campaign. To associate a new list with the given campaign, click the button with the “+” sign in the right pane and select the list from the dialog box that appears. The lower part of this tab contains the settings that define how the list will be used within this campaign.

By default, lists assigned to a campaign will appear in the campaign with the same priority and without any filters applied. I.e., if you decided to run a campaign after such initial assignment, all records from assigned lists would be dialed in a round-robin fashion in the order in which they appear in the originally imported list.

ServicePattern allows you to configure list order, apply filters, and define sorting rules. These settings are configured in the List tab of the Services and Campaigns menu option. Assigned lists appear in the upper portion of this screen. Properties that define use of the currently selected list within the given campaign appear in the lower screen portion and are described in the following table:


Properties tab
List Name of the selected list. Read-only.
Enabled Indicates whether the records from this list can currently be used within this campaign. Select the checkbox to use the records from this list.

Note that lists can also be enabled and disabled via the Agent Desktop application by a user designated as an operator for this campaign.

Order Defines the order (form low to high) in which lists will be used within the service. If you want records from different lists to be dialed in a round-robin fashion, assign the same priority to all such lists. See property Dialing ratio below for more information.
Dialing ratio For lists with the same order, defines the ratio at which records from these lists will be used. For example, if you have two lists with order 1, the first list has dialing ratio set to 2 and the second list has dialing ratio set to 3, two records from the first list will be used, then three records from the second list, then again two records from the first list, and so on.
Instance name The same list can be assigned to a campaign multiple times with different filters (see the Filters tab below). This property allows you to assign a different name for each instance of the same list within the same campaign. Note that the system does not verify uniqueness of such names.
Filters tab
Filter Specifies which records from this list will be used in the given campaign. Click add filter field to define a new filter and select the entity that will be used as a filter from the Filter records by drop-down menu. You can define multiple filters for the same list instance.
Note: Applying a filter to list data requires internal re-processing of the entire list. Thus, if a filter is applied to a list within a running campaign, use of this list within the given campaign will be suspended until re-processing is complete. The suspension time will depend on the list size and, for long lists, may amount to tens of minutes. Other lists associated with the same campaign will not be affected.
list field values Allows you to select records with specific values of certain fields.
  • From the Field drop-down menu, select the desired list field.
  • Select specific values if the field values in this list must (or must not) match one or more specific values. Specify the values in the field below. Note that each value must be specified on a new line. Indicate whether the records with the matching field values must or must not be dialed.
  • Select value range if the field value must (or must not) fit within a specified range. This option is supported for numerical values only. Specify the numerical range in the fields below. Indicate whether the records with the field values within the range must or must not be dialed.
dispositions from campaign Allows you to select records that were used in a previous campaign and whose processing ended with a specific disposition. For example, if you previously ran a sales campaign, and now would like to run a customer satisfaction survey campaign for the products sold during that campaign, you may use this filter to only reach the customers who actually purchased the product (as may be indicated by dispositions in the results of the original campaign).
  • From the Campaign drop-down menu, select the desired previous campaign. (Only the campaigns where this list was previously used and whose results are still stored in the system will be available for selection.)
  • From the Dispositions drop-down menu, select the dispositions indicating that the corresponding records must (or must not) be dialed during the given campaign.
  • Indicate whether the records with the selected disposition must or must not be dialed.
Note: Note that subsequent changes made to the association of the given list with the campaign you select above will potentially affect the filter you create here and may require re-processing of the list that this filter is applied to. During such re-processing, use of this list within the a running campaign will be suspended until re-processing is complete. The suspension time will depend on the list size and, for long lists, may amount to tens of minutes. Other lists associated with the same campaign will not be affected.
only never attempted records Allows you to select records whose dialing was never attempted during a previous campaign to which this list was assigned. For example, the campaign was terminated before all records on the list had been attempted.

From the Campaign drop-down menu, select the desired previous campaign. (Only the campaigns where this list was previously used and whose results are still stored in the system will be available for selection.)

all unfinished records Allows you to select all records whose processing was not finished during a previous campaign. This includes the never attempted records (see above) as well as the records that were attempted without a final result. For example, a dialing attempt was rescheduled due to no-answer event, but the campaign was terminated before the rescheduled time.

From the Campaign drop-down menu, select the desired previous campaign. (Only the campaigns where this list was previously used and whose results are still stored in the system will be available for selection.)

Sorting tab
Sorting order Allows you to choose the order in which the records of this list will be selected for dialing.
  • Select natural if the records are to be dialed in the same order they appear in the list.
  • Select random if the records are to be attempted randomly.
  • Select custom if the records are to be sorted by the values of a specific list filed. Click add to select the field to be used for sorting and specify the desired sorting direction (ascending or descending). Note that you can sort by multiple fields.


Note the following:

  • Changing the sorting order requires internal re-processing of the entire list. Thus, if you change the sorting order for a list within a running campaign, use of this list within the given campaign will be suspended until re-processing is complete. The suspension time will depend on the list size and, for long lists, may amount to tens of minutes. Other lists associated with the same campaign will not be affected.
  • Previously dialed and rescheduled records take precedence over never dialed records. Thus, when you add records to a list within a running campaign, such rescheduled records may be dialed before the new ones even if the specified sorting order indicates that the new records should be dialed first. You can use a list field of the Priority type to force immediate dialing of the new records.
  • For optimized performance, the dialer selects and caches up to 1200 records at a time. Thus, when you add records to a list within a running campaign, the dialer will finish previously cached records even if the specified sorting order indicates that the new records should be dialed first. You can use a list field of the Priority type to force immediate dialing of the new records.
< Previous | Next >