A particular process is followed to determine which campaign (and therefore Workflow & data combination) should be popped by a particular pop request. This section will provide a brief explanation of this process.

 

The diagram below provides a top-level overview of identifiers, campaigns, Workflows, and versions, and how these interact with each other.

 

 

Identifiers can be telephone numbers, email addresses, or some other unique identifier such as a sequence of letters and/or numbers. This will be used to identify which campaign to pop, as described in the Popping Mechanism Hierarchy below; it will be matched to an Alias, Pop Name, or Campaign Name. It should be noted that Diallers are unable to make use of Campaign Aliases.

 

Once a specific campaign has been identified, it specifies which Workflow is to be popped, and what (if any) information is to be passed. Note that each campaign can only link to a single Workflow, but multiple campaigns can link to the same Workflow.

 

The Workflow itself is where potential data linkages are specified, and contains all the Workflow Versions.

 

If a version of the Workflow has been published, this version will then be popped; otherwise, the most recent version will be popped. Pop data can be linked to the Workflow fields and variables within each version independently.

 

 

The flow diagram below provides an overview of the process linking a provided identifier and Workflow to be popped. It should be noted that Diallers are unable to make use of Campaign Aliases.