What is the correct response if a customer wants to integrate a product that Cortex XSOAR currently does not support during a 30-day proof of concept?

The correct response hinges on the established scope of the proof of concept (POC) engagement. When a customer expresses a desire to integrate a product that is unsupported by Cortex XSOAR during the trial period, it is important to clarify the standard terms of the POC. The practice typically involves showcasing the capabilities of existing integrations and not extending the scope to cover custom integrations unless specifically outlined in the initial agreement.

By indicating that custom integrations are not included in the POC, you are reinforcing the structured nature of the evaluation period. This keeps the focus on the current capabilities of Cortex XSOAR and ensures that both the customer and the provider have clear expectations regarding what can be delivered within the given timeframe. This clarity helps manage customer expectations effectively and prevents potential misunderstandings about the extent of services available during the POC period.

Suggesting an extension of the POC window for custom integration may not be feasible or practical depending on resources and timelines. Indicating that Professional Services could build the integration at an additional cost introduces complexity that may not have been agreed upon initially in the POC arrangement. Finally, agreeing to build the integration as part of the POC borders on a commitment that goes beyond the typical framework of such trials, potentially complicating the evalu