Call End Date/Time
This data export field displays the date and time at which the communication leg ended.
See also, Interaction Duration Charts.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
Basic |
|
Channels |
|
|
Size (bytes) |
8 |
|
Filter |
None |
|
Dimension |
None |
Format
You can display the date and time in a choice of formats. You can also change the time zone in which the time is displayed.
These settings are available via the field's Settings 
button.
Example
This data export report shows an email and a voice interaction.
Row 1: An incoming email.
Rows 2 to 4: An incoming voice call that was answered by an agent (rows 2 and 3) and then transferred (row 4). The call started at 17:15:25 and ended at 17:30:20.
|
Call End Date/Time |
|||||
|
2018-02-13 10:33:40 |
I |
j65.burt@teleworm.com |
monumental@gmail.com |
|
2018-02-13 10:33:40 |
|
2018-07-30 17:15:18 |
I |
07700900432 |
01614960654 |
15:00 |
2018-07-30 17:30:20 |
|
2018-07-30 17:15:25 |
O |
07700900432 |
iPath_129_cmilliband |
6:53 |
2018-07-30 17:22:21 |
|
2018-07-30 17:18:11 |
O |
07700900432 (2006) |
00156527D65C |
12:04 |
2018-07-30 17:30:17 |
Note: due to the instantaneous nature of text messages, emails, and social media messages, their end times match their start times.
Detail
The field value is written to every communication leg generated in an interaction.
Voice Interactions
The inbound leg of a call reports the date and time at which the call ended (after any transfers, where applicable). Outbound legs report the date and time at which those legs ended.
Text Interactions
The data export field populates the inbound (I) and outbound (O) legs in interaction scenarios as illustrated below. See also, Communication Legs.
|
|
|
|
|
|
External |
storm |
storm user |
|
|
|
Sent date and time |
INCOMING SMS TEXT |
|
|
Sent date and time |
OUTGOING SMS TEXT Agent-initiated or reply |
|
|
|
|
|
||
|
|
Sent date and time |
INCOMING EMAIL |
|||
|
Initiate or Action date and time |
Initiate Reply Forward Followed Up |
OUTGOING EMAIL or ACTION on INCOMING EMAIL |
Ignore Delete Requeue Complete Follow Up Followed Up |
Action date and time |
|
|
|
|
|
|
|
|
Web chat session end date and time |
WEB CHAT |
|
|
|
|
|
|
|
Sent date and time |
INCOMING SOCIAL MEDIA MESSAGE |
|
|
Sent date and time |
SOCIAL MEDIA MESSAGE REPLY |
Interaction over a Daylight Saving Time (DST) boundary
For records that are written over a Daylight Saving Time (DST) boundary where clocks have moved forward, there will be an apparent gap in the recorded date and times. If clocks have moved back, you may see several different records for the same date and time.
You can use the Call End Date UTC Offset field to resolve any time gaps or apparently conflicting times around a DST boundary.