☝️Note the currently known limitations for Transfer on User Exit:

🔎 (Additional) Transfers within the target service workflow: 

• Transfer to Service, Transfer to User, and Transfer to Customer Parameter are not supported.
• Transfer to External (PSTN phone number) is supported (required for DTMF input). Also refer to the PSTN limitations and reporting notes below.

🔎 Reporting Notes: 

• PSTN Removal on target service: When DTMF-Supported Transfer is enabled and the target service's PSTN number is removed, the transfer will fail and is reported as “Failed Service Transfer to External”.
• PSTN transfer mapping edge cases:  In most cases, PSTN-based Transfer on User Exit transfers are reported under the same Unified Session ID as the originating call. However, in certain edge cases, Nimbus cannot map the destination session to the original call, instead reporting a new incoming call with TransferOnUserExit = FALSE. 
  Such cases are: 
  • The caller gets anonymized (in any stage). Either the original call came from an anonymous number, the number was anonymized by Nimbus, or it was anonymized on the PSTN/caller side during transfer.
  • Multiple simultaneous calls from the same phone number arrive at the same service at the same time (e.g. a company routing all outgoing calls through a single number), making it impossible to match the source call to the correct original call.
• Nimbus Power BI Template coverage: The TransferOnUserExit flag is exposed in the OData Feed OData. Power BI dashboards consume these fields, but the standard Power BI template update follows in a later release