Shorten RingCX Historical Report Refresh Time Rate
Historical reporting may take up to an hour to populate, with an official timeframe of 15–60 minutes as specified by the product team. The customer has requested that the reports be available in near real-time.

-
Curt commented
Being able to download and listen to the calls within minutes is critical to training and coaching, as well as customer care functionality. We are experiencing delays in being able to access the call recordings of a minimum of 2 hours and up to 4 plus hours at times. This is a major concern for us.
-
Jeremy commented
needing an hour or two to compile on bulk for an exotic audio codex I can understand, but taking that long for something as simple as .mp3 or .wav shouldn't take that long, especially if it's possible to compile the recording as it's being made in real time, because of how long it is taking for our recordings to populate raises concerns about security and customer privacy, especially if recording the calls in .wav it would take that long to bulk compile and scan before upload, meaning that our customer data could potentially be stored on a RingCX server somewhere, literally anywhere as far as we know, for expediency, our policy, and potential privacy concerns, we need those times shortened and those recordings directly uploaded to us.
-
Brenda commented
Being able to download and listen to the calls within minutes is critical to training and coaching, as well as customer care functionality. We are experiencing delays in being able to access the call recordings of a minimum of 2 hours and up to 4 plus hours at times. This is a major concern for us.