# developer Agentforce Partner Onboarding Guide (agentforce-partners) - Full Documentation # Agentforce Partners Release Notes This section describes recent changes that have been made to this guide. To learn more about new Agentforce features, visit [Agentforce release notes](https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein.htm). ## September 2026 - Added Five9 to the [Agentforce Voice with SIP Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-sip-partner-regional-availability.md). - Added Custom SIP X-headers and SIP REFER information to [Support Agentforce Voice with SIP](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-sip-setup.md). ## July 2026 - Added AMC Technology to the [Agentforce Voice with SIP Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-sip-partner-regional-availability.md). ## May 2026 - Updated the sample SIP INVITE message in [Support Agentforce Voice with SIP](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-sip-setup.md). ## April 2026 - Created this release notes changelog for partner reference. - Added Vonage to the [Agentforce Voice with SIP Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-sip-partner-regional-availability.md). - Added [TLS Certificate Management Requirements](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice/agentforce-voice-tls-certificate-management.md). # Agentforce Voice with SIP Regional Availability Chart This document displays regional availability details for CCaaS partners that support Agentforce Voice with SIP. ## Genesys The Genesys regional availability chart displays the regional availability details for integrating Agentforce Voice with SIP with the Genesys partner CCaaS system. Refer to the Genesys [BYOC Cloud public SIP IP addresses](https://help.genesys.cloud/articles/byoc-cloud-public-sip-ip-addresses/) site for a list of the public IP addresses currently used by Genesys services across different regions. | Genesys Mapped Location | Agentforce Voice Region | Preferred Customer CCaaS Locations | SBC FQDN | | :------------------------------------------------------- | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------- | | US West (Oregon) / usw2 | US-WEST | USA West | gateway.afvsip.thb01.uengage1.sfdc-lywfpd.salesforce-ccaas.com | | US East (Northern Virginia) / use1 | N.VIRGINIA, US-EAST | USA East | gateway.afvsip.thb01.uengage1.sfdc-yfeipo.salesforce-ccaas.com | | Asia Pacific (Singapore) / apse1 | SINGAPORE | Singapore | gateway.afvsip.thb01.uengage1.sfdc-hvhps.salesforce-ccaas.com | | Europe (London) / euw2 | LONDON,UK | UK | gateway.afvsip.thb01.uengage1.sfdc-5pakla.salesforce-ccaas.com | | Asia Pacific (Mumbai) / aps1 | MUMBAI, INDIA | India | gateway.afvsip.thb01.uengage1.sfdc-y37hzm.salesforce-ccaas.com | | Asia Pacific (Tokyo) / apne1 | TOKYO, JAPAN | Japan | gateway.afvsip.thb01.uengage1.sfdc-mchho0.salesforce-ccaas.com | | Asia Pacific (Sydney) / apse2 | SYDNEY, AUS | Australia, NZ | gateway.afvsip.thb01.uengage1.sfdc-vwfla6.salesforce-ccaas.com | | Canada (Central) / cac1 | CANADA | Canada | gateway.afvsip.thb01.uengage1.sfdc-58ktaz.salesforce-ccaas.com | | South America (São Paulo) / sae1 | SÃO PAULO, BRAZIL | Brazil | gateway.afvsip.thb01.uengage1.sfdc-xwy4ub.salesforce-ccaas.com | | Europe (Frankfurt) / euc1 Europe (Zurich) / euw1 Ireland | FRANKFURT, GERMANY | Belgium, Croatia, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Luxembourg, Norway, Poland, Portugal, Spain, Sweden, Switzerland, Turkey | gateway.afvsip.thb01.uengage1.sfdc-yzvdd4.salesforce-ccaas.com | ## Vonage The Vonage regional availability chart displays the regional availability details for integrating Agentforce Voice with SIP with the Vonage partner CCaaS system. | Vonage Mapped Location | Agentforce Voice Region | Preferred Customer CCaaS Locations | SBC FQDN | | ------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | North America (NAM) / US West | US-WEST | USA West | gateway.afvsip.thb01.uengage1.sfdc-lywfpd.salesforce-ccaas.com | | North America (NAM) / US East | N.VIRGINIA, US-EAST | USA East | gateway.afvsip.thb01.uengage1.sfdc-yfeipo.salesforce-ccaas.com | | Asia Pacific (APAC) / Singapore | SINGAPORE | Singapore | gateway.afvsip.thb01.uengage1.sfdc-hvhps.salesforce-ccaas.com | | Europe (EMEA) / London | LONDON,UK | UK, Ireland | gateway.afvsip.thb01.uengage1.sfdc-5pakla.salesforce-ccaas.com | | Asia Pacific (APAC) / Sydney | SYDNEY, AUS | Australia, NZ | gateway.afvsip.thb01.uengage1.sfdc-vwfla6.salesforce-ccaas.com | | Europe (EMEA) / Frankfurt | FRANKFURT, GERMANY | Belgium, Croatia, Denmark, Finland, France, Germany, Greece, Hungary, Italy, Luxembourg, Norway, Poland, Portugal, Spain, Sweden, Switzerland, Turkey | gateway.afvsip.thb01.uengage1.sfdc-yzvdd4.salesforce-ccaas.com | ## AMC Technology The AMC Technology regional availability chart displays the regional availability details for integrating Agentforce Voice with SIP with the AMC Technology system. For more details, see [DaVinci Voice Gateway for Agentforce Voice](https://www.amctechnology.com/davinci-voice-toolkit-for-salesforce/davinci-voice-gateway-for-agentforce-voice?utm_source=referral&utm_medium=backlink&utm_campaign=dvg-sf-sip-regional). | AMC Technology Mapped Location | Agentforce Voice Region | Preferred Customer CCaaS Locations | SBC FQDN | | ------------------------------ | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | US West | US-WEST | USA West | gateway.afvsip.thb01.uengage1.sfdc-lywfpd.salesforce-ccaas.com | | US East | N.VIRGINIA, US-EAST | USA East | gateway.afvsip.thb01.uengage1.sfdc-yfeipo.salesforce-ccaas.com | | Singapore | SINGAPORE | Singapore | gateway.afvsip.thb01.uengage1.sfdc-hvhps.salesforce-ccaas.com | | UK-London | LONDON, UK | UK | gateway.afvsip.thb01.uengage1.sfdc-5pakla.salesforce-ccaas.com | | India | MUMBAI, INDIA | India | gateway.afvsip.thb01.uengage1.sfdc-y37hzm.salesforce-ccaas.com | | Japan | TOKYO, JAPAN | Japan | gateway.afvsip.thb01.uengage1.sfdc-mchho0.salesforce-ccaas.com | | Australia | SYDNEY, AUS | Australia, NZ | gateway.afvsip.thb01.uengage1.sfdc-vwfla6.salesforce-ccaas.com | | Frankfurt / Ireland | FRANKFURT, GERMANY | Belgium, Croatia, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Luxembourg, Norway, Poland, Portugal, Spain, Sweden, Switzerland, Turkey | gateway.afvsip.thb01.uengage1.sfdc-yzvdd4.salesforce-ccaas.com | ## Five9 The Five9 regional availability chart displays the regional availability details for integrating Agentforce Voice with SIP with the Five9 partner CCaaS system. | Five9 Mapped Location | Agentforce Voice Region | Preferred Customer CCaaS Locations | SBC FQDN | | --------------------- | ----------------------- | ---------------------------------- | -------------------------------------------------------------- | | US West | US-WEST | USA West | gateway.afvsip.thb01.uengage1.sfdc-lywfpd.salesforce-ccaas.com | | US East | N.VIRGINIA, US-EAST | USA East | gateway.afvsip.thb01.uengage1.sfdc-yfeipo.salesforce-ccaas.com | ## See Also - [Support Agentforce Voice with SIP](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-setup.html) - [SIP Signaling Configuration Form](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-signaling-config.html) # Agentforce Voice with SIP Signaling Configuration Form This document lists the Session Initiation Protocol (SIP) configuration parameters essential for managing real-time communication. Proper configuration ensures reliable call setup, teardown, and feature negotiation across various geographical regions. ## Before You Begin Use this form to collect the information Salesforce needs to start the SIP integration process. Complete this form as part of the Agentforce Voice with SIP onboarding process for CCaaS partners. Refer to the [Support Agentforce Voice with SIP](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-setup.html) page for details. **Copy and paste the following content into a separate document, fill in all configuration details, and then send the completed document to your Salesforce team.** ## SIP Trunk Complete the following SIP trunk details. Note: The first line represents an example of the information to provide. | Partner CCaaS Region | Partner IPv4 Subnet for Signaling | Ports | Partner CCaaS Provider Name | | :------------------- | :-------------------------------- | :----- | :-------------------------- | | _US-WEST-2_ | _x.x.x.x_ | _5061_ | _Genesys_ | | | | | | | | | | | **Descriptions:** - **Partner CCaaS Region:** The geographical location of the SIP signaling server. Selecting the closest region to your user base minimizes latency and improves call quality. - **Partner IPv4 Subnet for Signaling:** The IP address range allocated for SIP signaling traffic within a given region. This address range is critical for network routing and firewall configurations. - **Ports:** The specific network ports used for SIP signaling. **TCP/TLS port 5061 (for encrypted SIP).** ## Media Traffic This section details the configuration parameters for media traffic, which encompasses the actual audio and video streams exchanged during a communication session. Optimized media configuration is paramount for high-quality, real-time communication. Complete the following chart only if signaling and media IP are different. | Partner CCaaS Region | Partner IPv4 Subnet for Media | Ports | | :------------------- | :---------------------------- | :---- | |   | | | |   | | | |   | | | **Descriptions:** - **Partner CCaaS Region:** The geographical location of the media server. Proximity to end users is crucial for minimizing media latency and ensuring a smooth user experience. - **Partner IPv4 Subnet for Media:** The IP address range dedicated to media traffic. This distinct subnet allows for separate network policies, QoS (Quality of Service) configurations, and security measures for media streams. - **Ports:** The network ports used for media traffic. Real-time Transport Protocol (RTP) typically uses a range of UDP ports (e.g., 1024 \- 65534) for audio and video streams. Secure RTP (SRTP) uses the same port range but with encryption. ## Certificates Provide your partner certificate details. Salesforce installs these certificates on Edge devices to ensure a secure, trusted connection between the CCaaS partner and the SFDC SBC. To learn about certifcate update communication requirements between partners and our Operations team, see [TLS Certificate Management Requirements](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-tls-certificate-management.md). | Transport Protocol | TLS | | :------------------- | :-------- | | **Codec Supported** | G711U | | **CA Certificate** | | | **SRTP Requirement** | Mandatory | ## Regional Connectivity This section provides general recommendations for connecting various countries to specific regional infrastructure for optimal performance and reliability. | Countries | Region Recommendation and Region Info | | :----------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------ | | UK | London | | Germany, France, Italy, Switzerland, Sweden, Finland, Denmark, Spain, Belgium, Greece, Poland, Portugal, Hungary, Luxembourg, Norway, Turkey, Croatia. | Frankfurt | | India | Mumbai | | Canada | Canada | | USA | US East or US West | | Japan | Tokyo, Japan | | Australia | Sydney | | Brazil | Sao Paulo | | Singapore | Singapore | **Descriptions:** - **Countries:** The countries or geographical areas for which the recommendation applies. - **Region Recommendation:** The most suitable region to establish connectivity for users within the specified countries. This recommendation considers factors such as network latency, data sovereignty, regulatory requirements, and the location of the primary user base. Adhering to these recommendations helps ensure a robust and efficient communication infrastructure. **note:** For the latest list of Agentforce Voice with SIP partners and regions, refer to the [SIP Partner Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-partner-regional-availability.html) page. ## See Also - [Support Agentforce Voice with SIP](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-setup.html) - [SIP Partner Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-partner-regional-availability.html) # Get Started with Agentforce for Partners Agentforce is the agent-driven layer of the Salesforce Platform, and it helps you deploy AI agents that work side-by-side with your employees to extend your workforce and serve customers 24/7. The Trust Layer securely connects your data with the power of large language models (LLMs). This guide is for Salesforce partners who help their Salesforce customers implement Agentforce features, including Agentforce Voice. If you're a customer and you want to set up Agentforce, begin your journey at [Agentforce and Einstein Generative AI](https://help.salesforce.com/s/articleView?id=ai.generative_ai.htm). To dive deeper and develop with Agentforce and generative AI, go to the [Agentforce Developer Guide](https://developer.salesforce.com/docs/ai/agentforce/overview). **See Also** - [Agentforce Developer Guide](https://developer.salesforce.com/docs/ai/agentforce/overview) - _Salesforce Help_: [Agentforce and Generative AI](https://help.salesforce.com/s/articleView?id=ai.generative_ai.htm) - _Salesforce Help_: [Agentforce Agents](https://help.salesforce.com/s/articleView?id=ai.copilot_intro.htm) - _Salesforce Help_: [Agentforce and Einstein Generative AI](https://help.salesforce.com/s/articleView?id=ai.generative_ai.htm) # Get Started with Agentforce Voice for Partners Agentforce Voice transforms customer service by replacing traditional interactive voice response (IVR) menus with AI-powered voice agents that deliver natural, conversational experiences built directly on the Salesforce platform. These intelligent voice agents operate 24/7, leveraging the existing Salesforce data and workflows to understand customer intent, provide accurate answers, and handle requests autonomously while seamlessly escalating to human reps when needed. As a Salesforce CCaaS partner, the topics in this section help ensure you provide your Salesforce customers with the best possible Agentforce Voice setup experience. **See Also** - _Salesforce Help_: [Agentforce Voice](https://help.salesforce.com/s/articleView?id=ai.agentforce_voice.htm) - _Salesforce Help_: [Connect a Service Agent to Partner Telephony](https://help.salesforce.com/s/articleView?id=ai.agent_connect_telephony_parent.htm) - [Agentforce Developer Guide](https://developer.salesforce.com/docs/ai/agentforce/overview) # Support Agentforce Voice with SIP When transmitting voice calls to Agentforce agents, customers can select from multiple types of communication protocols: Public Switched Telephone Network (PSTN), Session Initiation Protocol (SIP), or Dynamic Voice Routing. To fully support customers who want to implement and use Agentforce Voice with SIP protocol, you must become a verified Agentforce Voice with SIP partner. If you’re a verified Agentforce Voice with SIP partner, to get started, your customers can start setting up Agentforce Voice with SIP by referring to the [Create a Voice-Enabled Service Agent](https://help.salesforce.com/s/articleView?id=ai.service_agent_voice.htm) Help page. If you’re not an Agentforce Voice with SIP partner, perform the steps in this document to obtain verification. ## Becoming a Verified Agentforce Voice with SIP Partner The flowchart represents a high-level flow of the Agentforce Voice with SIP setup process for the Contact Center as a Service (CCaaS) partner. The process starts when you contact your Salesforce team with a request to support Agentforce Voice with SIP and ends when the Salesforce team endorses you as a verified Agentforce Voice with SIP partner. ![Flowchart representing the steps that CCaaS partners perform to become Agentforce Voice with SIP partners.](https://developer.salesforce.com/media/agentforce-voice/agentforce-voice-partner-flow.png '{"class": "image-lg"}') ### Step 1: Perform Initial Assessment Review and complete the SIP support and header requirements before you begin the Agentforce Voice with SIP partner-verification process. #### SIP Support Requirements To ensure a successful SIP integration, verify that you meet the support requirements. Understand the connectivity standards required to establish a SIP trunk. - SIP over TLS (mTLS isn’t supported) - Media over SRTP - Static signaling and media IP addresses - Codecs Supported: G.711 PCMU and PCMA - SIP INVITE header fields Perform the verification steps to ensure your environment is prepared. - Verify that real-time communication systems are set up to support the SIP standard. - Verify that user-to-user information (UUI) headers with Hex encoding are supported. - Verify that you have the full public address range by regions for allowlisting. Provide your partner name and the customer's data center location. - Partner name, such as Genesys - Customer data center location, such as London #### UUI and SIP Standard Header Fields and Values Gather the values for the UUI and SIP header fields. To transfer an incoming call to an Agentforce agent using SIP, Salesforce uses UUI headers to pass call context and authentication data over SIP trunks. The UUI header carries key parameters that Salesforce uses to route the call. Alternatively, if custom SIP headers are enabled, Salesforce can use X-headers for those key parameters instead. During this setup process, you’ll use the header fields to perform basic SIP connectivity and end-to-end verification tests. For a list of UUI and SIP header fields, refer to [Configure Inbound Call Transfers When Using SIP](https://help.salesforce.com/s/articleView?id=ai.telephony_configure_inbound_call_transfers_sip.htm). #### Custom SIP Headers and SIP REFER Determine whether you plan to support X-headers in SIP invite requests and the SIP REFER protocol. Custom headers are used to send contextual data such as customer intent, language preference, or authentication information to an Agentforce agent. They are also used to support SIP REFER to handle disconnects, if this is a requirement for your customers. For more information, refer to [Include Custom SIP Headers and REFER Support](https://help.salesforce.com/s/articleView?id=ai.agent_sip_headers.htm). For a list of alternative X-headers to pass key parameters instead of using the UUI header, refer to [Configure Inbound Call Transfers When Using SIP](https://help.salesforce.com/s/articleView?id=ai.telephony_configure_inbound_call_transfers_sip.htm). ### Step 2: Gather SIP Configuration Details To collect the information that Salesforce requires to start the SIP integration process, complete the SIP Signaling Configuration Form. 1. Make a copy of the [SIP Signaling Configuration Form](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-signaling-config.html) and complete it. 2. Send the completed document to your Salesforce team, who then submits a request to the development team to integrate you as an Agentforce Voice with SIP partner. 3. Wait for your Salesforce team to confirm that the integration has completed so that you can move on to the next step. ### Step 3: Perform Basic SIP Connectivity and End-To-End Verification Tests After your Salesforce team confirms that the integration has completed, perform basic SIP connectivity and end-to-end verification tests. #### Connectivity Test 1. Use the UUI header (in Hex code) to initiate a test call to the Salesforce Session Border Controller (SBC). ```json {"orgId":"echo-test-org","scrt2Domain":"afv-wss-echo:7442"} ``` 2. To confirm that connectivity is successful, after you initiate the call, listen for the ECHO. 3. To verify that signaling works as expected, perform basic call tests and verify the SIP traces at both ends. The sample SIP INVITE message is used to initiate a user-to-user call. ```json INVITE sip:+11060321122@10.10.1.148:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.41.152.80:5060;branch=z9hG4bK10Bf15a9a98700aeb9c From: ;tag=gK103154c4 To: ;transport=TLS Call-ID: 608213684_125667659@10.41.152.80 CSeq: 850640 INVITE Max-Forwards: 68 Allow: INVITE, ACK, CANCEL, BYE, REGISTER, REFER, INFO, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS, MESSAGE, PUBLISH Contact: User-to-User: 7B226F72674964223A226563686F2D746573742D6F7267222C227363727432446F6D61696E223A226166762D7773732D6563686F3A37343432227D;encoding=hex User-Agent: VineProx-v2.3 Supported: timer, 100rel, precondition, replaces Session-Expires: 1800 Min-SE: 90 Content-Length: 235 Content-Disposition: session; handling=required Content-Type: application/sdp , msgLen = 1504. 324 12092025 042639.296880:1.01.00.22619.Info .SIPCM: SipFeSocketSendMsg - msg = v=0 o=Sonus_UAC 520733 642062 IN IP4 10.22.88.80 s=SIP Media Capabilities c=IN IP4 10.22.88.80 t=0 0 m=audio 1072 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 , msgLen = 224. ``` 4. Repeat the steps for each mapped region that you support. #### End-To-End Testing 1. Configure a Salesforce org with partner telephony fully set up. 2. Set up Agentforce Voice with SIP. For the steps, see the [Create a Voice-Enabled Service Agent](https://help.salesforce.com/s/articleView?id=ai.service_agent_voice.htm) Help page and then the [Connect a Service Agent to Partner Telephony](https://help.salesforce.com/s/articleView?id=ai.agent_connect_telephony_parent.htm) Help page. 3. Perform an inbound call that enters your partner telephony system. 4. Transfer the call to Salesforce via SIP. 5. After the call connects to the Agentforce Voice agent, escalate the call to a service rep. 6. Return the call back to your partner telephony system and route the call to the service rep inside Salesforce via Salesforce Voice. Verify that the Agentforce Voice Call record is linked to the Voice Call routed to the service rep. ### Step 4: Final Review with Salesforce Schedule a call with Salesforce to review your end-to-end setup. To facilitate this review, share documentation of your setup, such as a recording. The documentation should explain: - Your telephony provider configuration for Agentforce Voice with SIP - The flow used to transfer the call to an agent and escalate the call to a rep - How you link related calls to pass call context ### Step 5: Publish Supported Agentforce Voice Regions After you’ve thoroughly tested the connection, wait for Salesforce to notify you that you’re endorsed as a supported Agentforce Voice with SIP partner. Congratulations. As a verified Agentforce Voice with SIP partner, you can work with your customers to implement Agentforce Voice with SIP in their orgs. Your customers can refer to the [Create a Voice-Enabled Service Agent](https://help.salesforce.com/s/articleView?id=ai.service_agent_voice.htm) Help page to get started with Agentforce Voice. ## See Also - [SIP Partner Regional Availability Chart](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-partner-regional-availability.md) - [SIP Signaling Configuration Form](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-sip-signaling-config.md) - [TLS Certificate Management Requirements](https://developer.salesforce.com/docs/ai/agentforce-partner/guide/agentforce-voice-tls-certificate-management.md) - _Salesforce Help:_ [Create a Voice-Enabled Service Agent](https://help.salesforce.com/s/articleView?id=ai.service_agent_voice.htm) - _Salesforce Help:_ [Configure Telephony Vendor Settings When Using SIP](https://help.salesforce.com/s/articleView?id=ai.telephony_vendor_settings_sip.htm) # TLS Certificate Management Requirements for Agentforce Voice Platform To ensure uninterrupted service for the Agentforce Voice platform, SIP partners must coordinate all TLS certificate updates with our Voice Operations team. Our security architecture requires multi-layered approvals, and unannounced certificate rotations will cause immediate service disruption. ## Notification Requirements - **Standard Updates:** Require a minimum of 14 days advance notice to provide enough time to perform mandatory testing. - **Emergency/Risk-Based Updates:** If an immediate rotation is required due to a compromise or expiration, a detailed justification is mandatory. While we will prioritize these requests through our escalation path, we can’t guarantee completion within a few hours due to the required security process and proper validation. ## Notification Process [Email our Voice Operations team](mailto:thb-voiceops@salesforce.com), and include this information: - **Partner Name:** Your organization's identifying information. - **Type of Update:** Specify whether you are completing a standard scheduled rotation or an emergency rotation. For an emergeny rotation, include detailed justification. - **Target Date:** When you intend to perform the TLS certificate change on your side. - **Technical Contact:** Best point of contact for your engineering team during the update window and their contact information.