Data usage in Connect
- Helen Griffith
Connect uses several custom objects to manage calls. Each custom object record costs 2 KB against your data storage limit. Many of the custom object records created by Connect are short lived and have a limited impact on your data storage limits; others, such as Dial List and Processed Dial Entry, live as long as you require them for reporting purposes and are not removed until you delete them. In this scenario, a supervisor has created a single dynamic Dial List and assigned 50 agents. All 50 agents are actively working on the dial list and have, so far, completed 5000 calls and skipped 5000 calls. The dynamic Dial List cache size for the org is 500 and the dial list has just been refreshed filling the cache so that there are as many pending calls as possible. All agents take notes on the call and no call transfers occur. Pending Dial EntryShort lived custom objects
Long lived custom objects
Example storage usage scenario
Dial List 1 2 Dial List Processing Time 1 2 Dial List Agent 50 100 500 1000 Active Dial Entry 50 100 Processed Dial Entry 10,000 20,000 Interaction Event 5,000 10,000 Interaction Event Note 5,000 10,000 Task 5,000 10,000 Totals 25,602 51,204 Short Lived 602 1,204 Long Lived 25,000 50,000
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.