Campaign calls seldom reach the desired number of contacts after a single pass through a list. Therefore, campaign lists are recycled using disposition codes from earlier cycles to alter selection and sort strategies to create new campaigns. The transaction codes, which indicate call outcomes, can be used to determine how a campaign call needs to be processed further. You can map transaction codes to automated disposition actions for better processing of campaign calls.
Every attempted campaign call may be labeled with a disposition action for follow-up. The supported disposition actions are Try Again, Schedule Call Back, and Do not Call.
The following table summarizes the resulting disposition actions with examples:
|Disposition Action||Resulting Action|
|Schedule Call back||
|Do not Call||allows marking records, and updating a CRM field with Do not Call disposition information.
For example, the Lead object in Salesforce CRM has a standard Do not Call field. During a campaign call, you can update this field automatically by mapping a transaction code with Do not Call disposition action.
The disposition actions get recorded in the Campaign Transaction Details report. A supervisor can monitor this report, and follow up with suitable actions.
To access the Disposition Action tab:
Note: Disposition actions apply to transaction code lists assigned to queues only. You cannot map code lists assigned to agent groups.
Open topic with navigation