Refreshing a sandbox during the release preview window to ensure they have the upcoming release is a step that the team at UC should take to prepare for the new Salesforce release, as it allows them to test their application in an environment that matches the production environment after the upgrade. Running regression tests in an upgraded sandbox to detect any issues with the upgrade is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to verify that the existing functionality is not affected by the new features or changes introduced by the upgrade. Reviewing the release notes for automatically-enabled features and technical debt is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to understand the impact and benefits of the new features or changes, as well as to identify and resolve any technical debt that may cause issues or conflicts with the upgrade. Contacting Salesforce to schedule a time to upgrade the full sandbox is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not possible to request a specific time for the upgrade of the full sandbox, which is determined by Salesforce and depends on the release window and the pod assignment. Upgrading any SOAP integrations to the newest WSDL as early as possible is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not necessary to upgrade the SOAP integrations to the newest WSDL, unless they want to use the new features or fields introduced by the upgrade. The SOAP integrations will continue to work with the previous WSDL versions, as they are backward compatible.