...
| Excerpt |
|---|
Records representing Salesforce objects each use 2 kilobytes (KB) of data storage, that is, each of your standard Salesforce objects, Accounts, Contacts, Leads, and so on, use 2 KB of data. In addition to standard Salesforce records, Connect provides custom Salesforce objects, Dial Lists and Dial Entries. Dial List and Dial Entry records each use 2 KB of data storage. For example, one Dial List with ten Dial Entries uses 22 KB of data storage.
...
| title | Temporary records |
|---|
During a call, Connect creates temporary task records. These records are deleted after one to two hours but each use 2 KB of data while they exist.
...
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
Long lived custom objects
Example storage usage scenarioIn 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.
|