|The name of this Vonage Call Summary record.|
The name given to the telephone number the caller has entered the VCC Admin Portal on.
|Vonage Telephone Number|
For inbound calls: the telephone number the caller entered the VCC Admin Portal on. May not always be number the caller dialed.
For outbound calls: the callback number
|CallGUID||Unique identifier for this call|
|Conversation GUID||Unique identifier for calls grouped in a conversation, such as the calls involved in a queued callback.|
|Task Exists||Box is checked when an activity record or task has been created for this interaction.|
|Task Link||Link to the Salesforce task record relating to this interaction, if available|
|Related To||The name of the related account if known from the account, case, opportunity or contact; otherwise the contact's or lead's name if known.|
|Related Contact||The contact this call relates to|
|Related Account||The account this call relates to|
|Categories||Categories matched by the Conversation Analyzer, if enabled for your account.|
|Data Source Values|
A comma-delimited list of mapped data sources in your account and their values in name:value pairs.
Data Source Mappings
For data source values to appear, the data sources must be mapped in the Data Source Mappings of the VCC Admin Portal. For information about Data Source Mappings, see Data Source Mappings.
Outbound Call: Interaction is an outbound call made by using either Click to dial, make call or Connect.
Inbound Call or Phone: Interaction is an inbound telephone call.
Case, email, web chat, and so on: Non-call interaction. Such interactions are displayed in a different page layout to calls.
|CallTime||Date and time stamp indicating the start of the call|
|Total Call Duration|
For inbound calls: The total time, in seconds, that the caller spends on the VCC Admin Portal for a particular call.
For outbound calls: The total talk time plus ringing an agent spends making a particular call.
|CallEndTime ||Date and time stamp indicating the end of the call|
|Queued Callback||Check box. Queued Callback check box is selected if the interaction is part of a queued callback conversation|
|Call Result||Copied from the Call Result field on the related Salesforce task record (if available). Often used for disposition code or next action by Salesforce users as well as the outcome of a Connect call.|
|Related Lead||The lead this call relates to.|
|Related Case||The case this call relates to.|
|Related Opportunity||The opportunity this call relates to.|
|Monitored||Check box. The Monitored check box is selected if the call was monitored.|
|Caller and Agent Related|
|Vonage AgentID||VCC Agent ID for the initial agent handling the call.|
|Agent||The name of the initial agent (as recorded in their Salesforce user record) handling the call.|
|Agent Phone Number||The telephone number Vonage Contact Center delivers the call to; also referred to as direct dial number, DID or DDI.|
|Agent2 ID||VCC AgentID for the agent the call was transferred to from the original agent.|
|Agent2||The name of the agent (as recorded in their Salesforce user record) who received the call following a transfer from the original agent.|
|External Transfer Phone||The external phone number the call was transferred to in case of an external transfer.|
|CLID||The number presented by the caller (caller ID). Alternatively a case ID for interactions routed through a UCD applet.|
Time zone this event occurred in—for example, Europe/London. The time zone is from the perspective of the last agent or the user who configured the channel if no agent details are available
|Queue Name||The name of the Queue where the interaction waited to be answered. Where a call spends time in different queues, Queue Name is Multiple and the individual queue names and durations are listed in Queue List. If the interaction visited just one named queue several times, the name of that queue is recorded.|
A comma-delimited list of queue periods for the interaction; comprises the name of the queue and the duration spent in it in order of queue episodes. The information appears in the following format:
QueueName-duration, QueueName-duration, ...
For example, if an interaction spent 30 seconds in Queue A and 15 seconds in Queue B, Queue List contains the following values:
Queue A-30,Queue B-15
Similar to Queue List, a comma-delimited list of agents that the interaction was routed to along with the duration of ringing for each agent. The information appears in the following format:
For example, if an interaction was routed to agent 123 and agent 123's phone rang for 30 seconds, and then the interaction was routed to agent 456 and agent 456's phone rang for 15 seconds, Ring List contains the following values:
|Last Agents Calls this Day||Link to Vonage Agent Summary record for the last agent to contribute an event to this call.|
Agent IDs for all agents involved in the call and the duration of time they spent handling the call. Multiple values are separated by commas. The information appears in the following format:
For example, where agent 110 spent 45 seconds handling the call, and agent 475 spent 103 seconds handling the call, Agent List contains the following values:
|Skills List||the skills which the interaction was tagged with when the interaction was placed in queue|
|Call Segments & Times|
|Automation||The amount of time a caller spent in an interaction plan—in menu applets, announcement applets, and so on—before entering a queue.|
|Number of Applets||Number of applets that the interaction was routed through: announcements, menus, digit collections, callouts to other systems, skill taggers, and so on.|
|Delivery Attempts||Count of the number of attempts to deliver an interaction to agents. Defaults to 1 for internal calls.|
|Total Ring Duration|
For inbound calls: The total time in seconds that Vonage Contact Center attempted to deliver the interaction to an agent from a queue. The value is sum of the durations of ringing for the agents to whom the interaction was offered.
For outbound calls: The total time, in seconds, that an agent spent ringing a third party before the call was answered or dropped.
|Last Ring Duration|
For inbound calls: The time in seconds of the last attempt to connect with an agent.
For outbound calls: The time that an agent spent ringing a third party before the call was answered.
|Agent Talk Time|
Add Agent Talk Time and Agent2 Transfer Time to include talk time for agent handling call when transferred.
|Hold Time||The total duration in seconds that the interaction spent on hold or parked. Hold Time includes the time that two parties—for example, two agents—consulted with each other prior to a transfer. Hold time is included in handle time for calls, but for non-calll interactions, on hold interactions are considered to be parked and therefore do not count as handle time for any agents.|
|Park Time||Total time in seconds that the interaction was parked and was therefore not being handled.|
|Interrupted Time||Total time in seconds that the interaction was interrupted by a higher priority interaction and was therefore not being handled.|
|Agent Consult Time||Time spent by agent or agents consulting other agents. Consult Time is included in handle time.|
|Number of Transfers||Number of times that an agent transferred the call to another agent or automated system such as the Mid-call Payment Transfer System or a queue.|
|Warm Transfer Time||Time spent by agent consulting with next agent before transferring the call to them. Warm Transfer Time is included in handle time because the second agent is working on the interaction for the consultation time.|
|Agent2 Transfer Time||Time spent by Agent2 handling a transferred call until another event, such as hold.|
|PCI Time||Total time, in seconds, that the caller spent interacting with PCI payment systems. PCI Time is included in handle time as the agent is placed on hold for the duration.|
|External Consult Time||Total time, in seconds, that the agent spent consulting on an external line.|
|External Transfer Time||Total time, in seconds, that the call was transferred to an external line.|
|After Call Work Time||Amount of time spent on post call activity. Post call activity includes manual and automatic wrap activities for the agent (or agents if the original agent transferred the call).|
|Post Call Automation Segment|
Time that the interaction spent in post-call applets—for example, a post-call survey—after the agent ended the call.
|Recording Duration||For inbound and outbound calls: The total duration in seconds of the call recording.|
|Number of Call Recording Interrupts||The number of times the call recording was paused or interrupted either automatically by VCC (during a PCI-compliant mid-call payment or during holds or consults) or manually by the agent.|
|Message Taken||Indicates whether a voice message was captured or left for this call.|
|Abandoned ||Indicates whether the interaction was abandoned before or after entering a queue, but before being connected to an agent.|
|Short Abandon ||Calls abandoned within 10 seconds.|
|Connected||Indicates that the interaction was connected. Selected if two or more parties were connected.|
|Number of Warm Transfers||Number of transfers directly from one agent to another rather than through a queue.|
|Number of Transfers to Applet|
Number of times the interaction was transferred by agents to further applets. An agent would usually transfer the interaction to queue but can also direct the caller to a menu or survey.
|Number of PCI Transfers||Number of times the call went into PCI payment phases.|
|End Applet||The last applet an interaction was routed through before being terminated by either party.|
Shows the party—Customer or Agent—who ended the call.
|Local Hour||Start hour from the perspective of the last agent's or the company's default time zone adjusted for DST if applicable.|
|Local Day of Week||Day of week in the time zone of the agent or the user who configured the channel if no agent details are available.|
|Local Date||Date from the perspective of the last agent's or the company's default time zone adjusted for DST if applicable.|
|Local ISO8601 Week||Week number in ISO8601 form of the start of the event in its local time zone.|
Text-sortable format—for example, YYYY/08/6-Saturday/00. Use this field to group and sort calls in reports
|Month of Year ||Month of year|
|UTC Hour ||UTC hour of the day|
|UTC Day of Week||Day of the week this call was received on in UTC|
|UTC Date||UTC Date of the Call|
|UTC ISO8601 Week||Week number in ISO8601 form of the start of the event in UTC|
|Week of Year||Simple Week count of the UTC Week number of the event start|
|Calendar Quarter||Calendar Quarter|
|Summary Record Processing|
|Server||The server or cloud this call data was retrieved from|
|Channel||Channel used to import this record|
|End Recorded||True if call end event was received from the API|
|Start Recorded||Indicates that the API received a call start event for the call. Selected for all calls for which the API has retrieved all data.|
Today's date and agent ID. Value appears in [YYYYMMDD][Agent Id] format.
Use Salesforce search to find a specific agent's summary record for a specific date..
|Last Queue Result|
The reason the call left a queue if the call continued. Values are:
|Version||Version of the Advanced Reporting and Statistics package that created the summary record.|
A comma-delimited list of the Virtual Queues or Agreements that the interaction matched.
For inbound interactions only.
|Call Rating||A comma-delimited list of call quality ratings given to a call.|
The record owner.
You can use Flags in the channel configuration to set the record owner to the last agent who handled the call.
|CR Start Immediate||Checked if Call Recording Applet which first turns on Call Recording starts the recording without waiting for the two parties to be connected. Use workflow(on create and update) to set this flag for calls which don't defer CR start based on the VCC service|
|Call Recording||URL to playback call recording|
|Created By||Standard Salesforce field containing the user who created the record. Can be the user who switched on Advanced Reporting and Statistics.|
|Last Modified By||Standard Salesforce field containing the user who last updated the record. Can be the user who switched on Advanced Reporting and Statistics.|
|Number of Segments|
Number of key events in this call. You can use this value as a measure of call complexity.
For example a call that goes to a menu applet, rings, and is connected to an agent would have 3 segments.
|Key Event String||Delimited encoded list of key interaction events (excludes all applets except those affecting call recording or voice messaging)|
|ChkStr||Delimited encoded list of all interaction events|
|Trace||Reserved for system use with Conversation Analyzer|
|Interaction JSON||Full JSON model of the interaction from the API|
The type of interaction. One of:
- Case (for non-live interactions)
- Inbound Call
- Outbound Call
- Internal Call