OUTBOUND Status Change data source

OUTBOUND Status Change Data Source

A record is written to the OUTBOUND Status Change data source whenever the value in the Row Status or Row Sub Status column of an OUTBOUND campaign's DATA MANAGEMENT table and view changes. Shown below are four status changes to a DATA MANAGEMENT table or view, causing four records to be written.

DATA MANAGEMENT table or view

Historical Data Export Report (OUTBOUND Status Change data source)

The following table describes the entire set of possible statuses and sub statuses:

Status	Status meaning	Sub Status	Sub Status meaning
Not Dialled	The storm OUTBOUND application selected the record for processing.	None	Not applicable
Active	The record was being processed and a result had yet to be returned to the DATA MANAGEMENT table. For example, the contact was in an outbound queue or an OUTBOUND call was in progress.	Not Dialled Active	The record was in the process of being dialled for the first time.
		Retry Active	The record was in the process of being retried using the same number.
		Failure Active	The record was in the process of being dialled using the contact’s next available number.
		Callback Active	The record was in the process of being dialled due to an agent-scheduled callback.
In Progress	The record was marked for redialling.	Scheduled Callback	The record was marked for an agent-scheduled callback.
		Retry and Failure Call Result	An agent selected a completion code that matched both a retry and a call failure completion code in the retry profile. The contact in this record was meant to be called again on the same number and, if required, on the next number according to the retry profile.
		Retry Call Result	An agent selected a completion code that matched a retry completion code but NOT a failure completion code in the retry profile. The contact in this record was meant to be called again on the same number according to the retry profile.
		Failure Call Result	An agent selected a completion code that matched a failure completion code but NOT a retry completion code in the retry profile. The contact in this record was meant to be called again on the next number according to the retry profile.
Complete	The record was dialled and was not scheduled for a retry or an agent-scheduled callback.	Maximum Calls Exceeded	The record was processed and was not meant to be called again because either the maximum number of retries (as configured in the retry profile) had been reached, or the retry profile was disabled.
		Call Result not in retry profile	The record was processed and was not meant to be called again because the selected completion code did not match any values in the retry profile.
		Retry criteria not met	The record was processed and was not meant to be called again because, while a match for the completion code was found in the retry profile, no match was found in the rules set up for that retry profile.
Expired	The record had reached its expiry date.	None	Not applicable
Excluded	The record had been excluded from further dialling.	None	Not applicable
Do not process	The record was not dialled because it had been included in a 'Do Not Process' list during the campaign run.	None	Not applicable

Explore Further

Section	Description
Data Export Fields in OUTBOUND Status Change	Provides a detailed description of each data export field in this data source and shows how the field is populated for the different parts on an interaction. There is a topic for each data export field. The information will help you to interpret and build data export report. Each topic in this section also indicates whether the data export report supports a filter, a dimension, or both. Knowing that a data export field supports a filter means that you can design metrics to include or exclude values reported the field. Knowing that a data export field supports a dimension means that you can break down metric values in a custom report on the basis of values reported in the field.
Metrics in OUTBOUND Status Change	Provides a detailed description of the standard metrics in this data source. You use metrics to create Custom Historical Reports.