Explicitly pause copilot response for paths/queries

Hello, 

Is there an option to have more control of when the copilot will respond to user triggers? It would be useful if we could turn off copilot response when certain user statements trigger a path.

We noticed issues where the copilot will take precedence over our paths/queries that we triggered and try to summarize a response. We would like to turn off the copilot in the scenario so the user is only displayed the path/query that we have created for this trigger. 

For example, in the following scenario, we have created a troubleshooting path for headset issues. The copilot response takes precedence over the explicit path, which is not desired.The path is only displayed to the user after the copilot response.