Once the vendor application is published or authorized in development, the integration must be made active inside the customer's specific operational tenant.
In this step, we will have to navigate to the administrative portal, bind the newly generated connections to the correct organizational segments, and extract the system-generated backend telephony configurations.
Locate and Verify the Connection Assets
First, we will have to confirm that the application instance has correctly registered inside the Zoom Contact Center framework.
- Log into the Zoom Admin Portal using an account with Contact Center administrative privileges.
- In the left navigation menu, expand Contact Center Management, navigate to Integrations, and select Connectors.
- Review the active workspace grid to confirm that your newly added app connection entry appears dynamically in the list.
Map Connectors to Operational Divisions
Next, we will have to manage operational environments using divisions. Zoom Contact Center uses divisions to organize and isolate distinct teams, data rules, or business units.
- Locate your specific target connector from the data matrix.
- Click the Assign Division option associated with that connector.
- Select your operational target division (e.g.,
Main Division) from the menu selection prompt.
Note: If your organization does not leverage complex divisional profiles, you can bind the connector structure to the default root account settings to ensure standard cross-system availability.
Extract the Instance Endpoint Configurations
Next, we will have to extract the instance-specific data routing URLs required by the third-party voice agent platform.
- Locate the
...(ellipsis) options icon context menu positioned next to your assigned connector profile. - Select View Connector Settings from the prompt selection layout.
- Choose the appropriate operational Region matching your telephony network architecture deployment.
- Locate the data window displaying the Static URL. Click copy and securely store this value.
Architecture Note: This represents the unique webhook API gateway endpoint that the third-party voice agent must target to pass real-time interaction context back into Zoom. If you provision multiple individual connectors pointing to the same vendor voice agent, each unique connection profile will render its own isolated Static URL string.
Commit Configurations and Generate the Telephony Target Identification
Finally, we will have to commit these configurations to the active environment to generate the foundational telephone routing endpoints.
- Click Save at the base of the connector configuration screen.
- Saving changes prompts the Zoom core architecture to dynamically generate and allocate a unique 15-digit termination number string starting with the digits 999....
- Record this number cleanly; this string serves as the explicit SIP destination dial target (
INVITEheader string destination) required by external telephony layouts to push incoming calls into this specific connector path. - Repeat this administrative loop sequence for each unique connector connection instance deployed across the environment.