Call Data

Shows basic call record data for the selection criteria specified. See Call Records for further information.

Options

Availability	Standard
Select By	Account or Service Number(s), then custom Date Period
Viewable in Portal	Yes
Download Options	CSV or Excel
Available to Schedule	Yes
Schedule Frequency	Daily
Graphs Available	No
Timeline Available	No

Output

Column Name	Description	Type
CallID	Unique ID allocated to the call	Integer
Call Start	Date and time when the call reached the call handling platform, in DD/MM/YYYY HH:MM:SS format. This is not necessarily the time the call is answered (and where call charges may be applied)	DateTime
Call End	Date and time when the call terminates, in DD/MM/YYYY HH:MM:SS format. This is not necessarily the time when the calling party terminates the call - for Service Plans with Post Call functionality, this may be the time the called party terminates the call	DateTime
Dialled Number	Also known as Service Number, and is the number dialled by the calling party	Telephone Number
Description	Optional description, defined in the portal via Home>Numbers, or Home>Service Manager>Manage>Numbers, or via a Web API call	String
Calling Number	The calling party's number	Telephone Number
Called Number	The destination party's (i.e. the called party's) number	Telephone Number
Withheld	The caller's CLI status - Yes=Withheld, No=Not Withheld	String
Duration	Call duration from the point the call is answered by the destination party or by the platform, depending on the Service Plan configuration. If the only Call Result (see below) encountered during a call is 'unanswered', the Duration will be blank	HH:MM:SS
Call Result *	†Answered, Unanswered, Engaged or Failed.​ ('Failed' is synonymous with 'Other')	String
Time To Answer​	TTA is 0 if the call was not answered, or a value (in seconds) of 1 or greater depending on the time the called party takes to answer the call. TTA is always 1 if the platform (rather than the called party) is first to answer the call. If the only Call Result (see above) encountered during a call is 'unanswered', the TTA will be blank	H

*Depending on the level of complexity in a Service Plan assigned to a Service Number, an individual call can encounter more than one call outcome, but only the final call outcome is reported. For example, an outbound call to a destination that returns busy tone may cause the service flow to attempt a new outdial to a different destination that does answer the call. This call attempt will be reflected in the report as "Answered" - but the busy tone that the initial outdial attempt encountered will not be reflected in the "Engaged" column - it is effectively lost as far as this Pulse report is concerned.

† An inbound call will be marked in the first instance as "Answered" in the following scenarios:

• If the first event encountered in the call is audio (passive audio or a menu prompt for example) - i.e. the platform has answered the call. (Note: the "Answered" status may be superseded by another status if for example the audio is then followed by an outdial attempt that does not result in an answered call.)

• If an outbound call has been answered by the destination. (Note: the "Answered" status may be superseded by another status if the successful outdial is then followed by other activity from a Post Call node, where a subsequent outdial is attempted that does not result in an answered call.)