Data usage in Connect

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.

Short lived custom objects

  • Pending Dial Entry
  • Active Dial Entry
  • Dial List Processing Time
  • Dial List Agent

Long lived custom objects

  • Dial List
  • Processed Dial Entry

Example storage usage scenario

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.

Custom Object
Quantity
Cost KB
Dial List12
Dial List Processing Time12
Dial List Agent50100

Pending Dial Entry

5001000
Active Dial Entry50100
Processed Dial Entry10,00020,000
Interaction Event5,00010,000
Interaction Event Note5,00010,000
Task5,00010,000
Totals25,60251,204
Short Lived6021,204
Long Lived25,00050,000

Support and documentation feedback

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.