From Bright Pattern Documentation
< 3.14:Outbound-quota-tutorial
Revision as of 23:56, 23 February 2017 by Tracy (talk | contribs) (Created new topic from branched topic Documentation:ServicePattern:outbound-quota-tutorial:Overview:3.13)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Contents

Overview

Outbound quotas are used in campaigns where it is sufficient to successfully process a subset of records from a calling list in order to fulfill the campaign purpose. Typical examples of such campaigns are opinion polls and surveys. In a quota-based campaign, records are selected for dialing from the associated calling list based on the conditions set in the quota configuration. The dialing stops once the specified number of such records have been completed with desired dispositions. ServicePattern supports the following types of quotas:

  • A list-wide quota is set for the entire list. With a quota of this type, records are selected for dialing from the entire list without any specific selection criteria. Dialing stops once the desired number of records have been completed with any dispositions of success type.
  • Disposition-based quotas can be used to set separate limits for specific dispositions of success type defined within the given campaign. Records are selected for dialing from the entire list without any specific selection criteria. Dialing stops once the desired number of records have been completed with each disposition for which a quota is set.
  • Field-based quotas are set with respect to a specific type of data within the calling list (i.e., a specific field). Multiple field values can be defined. Dialing stops once the desired number of records within each value have been completed with any disposition of success type. Field-based quotas can be set for text and numeric fields.
    • For text fields, the dialer will select records whose value in the given field matches a value specified in the quota (e.g., calling a number of people from each specified specified state or province).
    • For numeric fields, the dialer will select records whose value in the given field fits within a value range specified in the quota (e.g., calling a number of people from each specified age group).

Two field-based quotas can be used in combination to create more complex sampling conditions (e.g., calling a number of people from each specified age group within each specified state/province).

One field-based quota can also be used in combination with one disposition-based quota.


Each quota set within a campaign can be monitored separately via the real-time quota metrics view available to campaign operators via the Agent Desktop application.


Campaign results have a special field that marks all list records whose processing within campaign was not finished (or never started) because a quota was reached.



Next >
Next >