So you're a manager and want to gamify and coach your reps who use RingCentral as their main dialer. You want an appropriate breakdown of call analytics and export/sync/integrate that data with a sales coaching and gamification platform (external to Ring Central). You currently have 2 options. You can use the Call aggregation data (Line Of Business Analytics) endpoint OR the List Company Call Records (Call log) endpoint. In ring central you have multiple ways of looking at call data. You can view call log reports, performance reports, and business analytics. The problem that arises is when wanting to integrate your call data with an external platform. You want to export the records so you can aggregate data yourself or export the user analytics all while having a source of truth in Ringcentral to go back and check against. Currently if you set up an integration with the call log API you get lots of discrepancies bc the call record is handled differently in the API and in app when looking at performance reporting. This idea is to bridge this gap. We either need a new endpoint that correctly matches user performance analytics as an endpoint that matches the same algorithms used in that reporting to aggregate and summarize user's call data OR we need the call log API to be updated to always include the user in the org that will be attributed for handling the call. For simple calls, the call log API endpoint is enough. Joe makes an outbound call to prospect A, and we see the length of the call and Joe's extension which we can look up against the directory and enrich the data with Joe's email, extensionID, etc etc For complicated calls that include queues, forwarding, transfers, department #s, IVR menus etc It's currently impossible to tell from the call log API WHO gets credit for the call. Even in the detailed view of the call log record, we can see all the legs but it seems that even RC's support team is unsure if they're in chronological order and HOW we'd get from point A to point B. WHO made the call or WHO picked up the phone and will ultimately get credit for it in the analytics dashboard is impossible to tell from the call log api endpoint. Here's a few response snippets from support tickets submitted inquiring about how to use the call log API (detailed views) to appropriately know who should get credit for a call. "From my understanding Performance reports analytics dashboard and the Call log APIs cannot be compared as they are from different systems and have different data source and implementations. Call log APIs can be compared with Call log reports available in your service web portal (https://service.ringcentral.com/).""Performance reports does not have an API yet to compare the Performance reports analytics dashboard with. If you are looking for call answered data through the Call log APIs, the detailed call log will have legs involved in the call. The legs are ideally in order and show the flow of the actual call. If you are looking for the extension that answered the call, you might want to look for “result”:“Call connected” and “reason”:“Accepted” in the Call log API response. If you have multiple transfers involved in the call and the call was answered by different users, then you will have multiple “result”:“Call connected” parameters in the API response."This is currently affecting managers' abilities to coach and gamify their reps in their ORG as some users may answer department calls and never receive credit for this externally due to lack of details in the call log API record or lack of a performance reports API endpoint. If there is a way to decipher call legs to know who should be getting credit for the call record, that would also be a great solution!