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 List	1	2
Dial List Processing Time	1	2
Dial List Agent	50	100
Pending Dial Entry	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