Home Luware Nimbus Nimbus Resources Nimbus Concepts and Definitions

INC Caller Anonymization Scope

Type of Data in Scope	Field Names affected by Caller Anonymization (System Fields and Parameters)	Content DURING live session (My Sessions / Attendant Console / Assistant)	Content AFTER session in short-term storage (Sessions List / My Sessions)	Content in LONG-TERM storage (Nimbus Reporting)
Nimbus Call Data	`MicrosoftCallerId` `CallerTelNumber` `Phone number` `Caller + Tel Number` `Customer + Primary Tel Number` `Customer Primary Tel Number`	Shown (required to support operational handling (e.g. Power Automate)	Shown as “Not Available”	N/A - Not stored
	`CustomerFirstName` `CustomerLastName` `CustomerUPN` `CustomerAddress` `CustomerEmail` `CustomerCompany` `CustomerJobtitle` `CustomerState` `CustomerCity` `CustomerStreetAddress`	Shown as “Not Available” because Customer Identifier is “Anonymized on Request”	Shown as “Not Available”	N/A - Not stored
	`Display Name`	Shown as “Anonymized on Request”	Shown as “Anonymized on Request”	N/A - Not stored
	`CallerID` `CustomerDisplayName`	Shown as “Anonymized on Request”	Shown as “Anonymized on Request”	Shown as “Anonymized on Request”
Nimbus System Data	`Customer Identifier`	Shown as “Anonymized on Request”	Shown as “Anonymized on Request”	Shown as “Anonymized on Request”
Nimbus System Data	`IsAnonymous (Boolean)`	N/A	N/A	Is set to `true` when Caller Anonymization is enabled.
Nimbus (Custom Context) Parameters Nimbus Address Books	☝Custom Data and Address Books are NOT in scope of Caller Anonymization The following data might still be visible during a call and needs to be handled accordingly: Personal data stored in Parameters (e.g. a customer entering a PIN during a workflow or other personally identifiable information retrieved via Power Automate Connector). Data stored within Workflow Activities, e.g. workflow announcements which are directly addressing the customer by name or involving a customer input. AI driven interactions with the Virtual User. The AI will use the customer identifiers to log and parse data. This also involves AI-driven features such as Summarization and Transcription, as invovled participants will be identified by name. Caller data stored or retrieved via Power Automate Connector, which also includes Address Book data, such as the customer's home address. ✅Related action: Extension Service Settings UI exposure: If your anonymized service makes use of Parameters and/or related Power Automate retrieval Flow Actions to store customer data, make sure to review which data gets exposed to your Nimbus users via Extensions Service Settings (e.g. as Context, Session Details). Check Custom Context transfer / storage settings: Within Extensions Service Settings of your anonymized service, review the “Store Conversation Context Data” and “Keep Custom Context Parameters on transfer” toggles. When enabled, retrieved parameters would otherwise be kept and potentially revealed during service transfers and the historical Sessions List.

Table: Nimbus data affected with “Caller Anonymization" feature enabled

Table of Contents