Data Management Table
This data export field displays the name of the storm DATA MANAGEMENT table that was driving the OUTBOUND campaign, which triggered the outbound call or message.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
OUTBOUND |
|
Channels |
|
|
Size (bytes) |
1026 |
|
Filter |
Data Management Table |
|
Dimension |
Data Management Table |
Example
This data export report shows an OUTBOUND campaign where three outbound calls were made using information from the 'Monumental Contacts' DATA MANAGEMENT table.
|
Data Management Table |
||||
|
2018-10-12 12:10:11 |
O |
00156531972e |
Adam Carter |
|
|
2018-10-12 12:10:17 |
O |
7737188074 |
Monumental Contacts |
|
|
2018-10-12 12:12:21 |
O |
00156531972e |
Adam Carter |
|
|
2018-10-12 12:12:26 |
O |
7401809148 |
Monumental Contacts |
|
|
2018-10-12 12:14:37 |
O |
00156531972e |
Adam Carter |
|
|
2018-10-12 12:14:43 |
O |
7841289009 |
Monumental Contacts |
|
Detail
The data export field populates the outbound (O) legs in an OUTBOUND campaign as illustrated below. See also, Communication Legs.
Voice Interactions
|
|
External |
storm |
storm user |
|
|
Deskphone LOG IN and LOG OUT |
|
|
|
OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
|
|
Initial called party leg (2nd leg) |
|||
|
Not written for rejected preview calls |
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||
|
|
Text Interactions
Written to the outbound leg of a storm OUTBOUND SMS campaign.
Filter
Include or exclude one or more DATA MANAGEMENT table views in your organisation.