All Session Data (stored in fields and parameters) are treated equally in a large JSON object. In order to get a clearer grasp on its structure, it is therefore helpful to define:

• … the type of data for differentiation, … 
• … the purpose of each data object and what it consists of, and …
• … which actors accessing or updating the data during an ongoing session.

Type of Data	Consists of	Purpose	Actors
Call Data	Customer Identification Data	Basic Customer Identification (Name, PSTN, SIP, UPN).	Nimbus Power Automate
	Customer Custom Fields	Additional Context on a Customer.
System Data	Service, Customer, User data fields.	Identify Caller, Service, and Users to manage a session. Usually kept up-to-date automatically by Nimbus.	Nimbus
Custom Context Parameters	Custom Parameters (Defined in Nimbus UI and Workflows) Custom Context Parameters (Defined during Flow Actions)	Handling parameters that are critical for Task routing (e.g. Queue Time, IVR choices, Customer Priority). They are “custom” placeholders for any Service Team requirement which is not already covered by the other types of data.	Nimbus Power Automate
Address Book Fields	Address Book fields of internal or external contacts.	Used to extend the search capabilities for Nimbus UI, e.g. within Attendant Console.