🔎BY DESIGN: CALLER ANONYMIZATION

💡The following design notes are not considered issues: 

• In any transfer scenario, the first service settings apply - including Caller Anonymization. Transfer to other services will inherit this setting from the original service session. This also works in the inverse case, meaning that transfers received from a service with anonymization disabled will NOT appear anonymized on a service that has the feature enabled.
• Power Automate Connector: Any externally retrieved Parameters and other Customer-identifying context are not included in Caller Anonymization.
  → Nimbus cannot identify which parameters count as sensitive. If you need to anonymize this information, adjust your Power Automate flows accordingly.
• Extensions Service Settings: While having “Store Conversation Context Data” toggle enabled, Custom Context Parameters may persist through anonymization. → We recommend to have this toggle disabled to ensure that sensitive parameters are not stored after a session.
• Scheduling a Callback (see Use Case - Schedule Automatic Callbacks from a Nimbus Queue) will not work on anonymized services, as the Workflow Activity “Save to Parameter” will not have a Parameter with a usable customer PSTN to operate with.
• The “Callback” Workflow Activity will not work on anonymized services.
• The caller PSTN (phone number) will still be shown in Microsoft Teams UI, as Nimbus cannot control this part.