Contact us
Recommended
Save time by chatting, available online 24/7.
Submit a case
The most direct way to match you to the right expert on your issue. Responses within 48 hours.
Contact us
FOR SALES
1 (888) 898-4591
FOR SUPPORT
1 (888) 898-4591
Submit a case
Contact us
FOR SALES
FOR SUPPORT
Welcome to MyRingCentral
Hi, ${extension.contact.firstName}!
Welcome to MyRingCentral
Hi, ${extension.contact.firstName}!
Analyzing call termination in Prebuilt Reports
Last updated on August 22, 2023
Notice
- On October 22, 2021, access to Prebuilt Reports in RingCentral Engage Analytics (now known as RingCX Analytics) was discontinued for new customers. Legacy customers were still able to use this feature.
- On July 1, 2023, access to Prebuilt Reports in RingCentral Engage Analytics (now known as RingCX Analytics) was discontinued for existing and new users. Customers should migrate to RingCX Analytics Historical Reporting.
- On July 1, 2023, access to Direct Data Access (DDA) to AWS Redshift was discontinued for all customers. Customers should migrate to RingCX Analytics Historical Reporting and use the Consolidated Reports Scheduling and Delivery feature.
- RingCX Analytics Historical Reporting is the new location for all reporting features. Read Intro to Historical reports to learn more.
A number of historical or real-time reports provide information about the details of how a call terminated. This information includes the call termination party (which party ended the call) and the termination reason (such as the call ended, the call was dropped, or the caller hung up).
The reports that provide this information for one or more call legs include:
- Global Call Transfer Detail
- Inbound Call Detail Download
- Dialer Result Download
- Global Call Type Detail
- Inbound Agent Segment Metadata Report
- Outbound Segment Metadata Report
To learn more about the individual metrics in these reports, read Reports reference.
In general, there are three different ways that a call will end between an agent and the far end caller/callee. The following examples look at metrics from the Inbound Call Detail Download available in Inbound reports.
Case 1: Far end hangs up
In this case, you will see the ‘Inbound_term_party’ as Caller and the ‘Inbound_term_reason’ as Hang-up for the caller’s leg of the call. As the call is now over, the system will end the agent's leg of the call resulting in an ‘Agent_term_party’ of System, and an ‘Agent_term_reason’ of EOC (End of Call).
Case 2: Agent hangs up via system
In this case, the agent leg will look the same as in Case 1 as it is still the System that tears down the agent leg of the call. You will still see an ‘Agent_term_party’ of System, and an ‘Agent_term_reason’ as EOC.
The key difference is what gets displayed on the caller’s leg, which will show the ‘Inbound_term_party’ as System with an ‘Inbound_term_reason’ of Drop. This indicates that the ending of this side of the call was via the System, and that due to the agent ending the call, the far end is being dropped off of the call session.
Note: The ‘Inbound_term_reason’ of Drop can be misleading here. Drop does not indicate a dropped call as we commonly refer to it, rather that as a result of the agent side ending the call, the system is dropping the far end from the session with the platform where it will be up to their local carrier to tear down their side of the call.
Case 3: Agent hangs up via softphone or hard phone
In this case, the agent has hung up via their phone rather than using the system call controls available to them in the Agent UI. As such, the call detail shows the ‘Agent_term_party’ as Caller for the agent leg and the ‘Agent_term_reason’ as Hang-up for the agent leg.
