Genesys Cloud - Developer Community!

Hi,

We have a customer who has recently integrated Genesys Cloud with Dynamics 365 using a third-party connector. They are experiencing an issue where Agent Co-Pilot does not automatically load/pop up when an interaction begins.

Currently, agents must manually open the Co-Pilot script from the embedded client, which isn't ideal as the customer conversation is often already underway by the time the script is opened.

• Is this expected behaviour with the current embedded framework?

• Is this something that is expected to be addressed in the upcoming embedded framework UI updates?

• Are there any recommended interim workarounds or best practices (e.g. pop-out windows, embedding options, or agent workflows) to ensure Co-Pilot is available from the start of the interaction?

Any insights or experiences from similar implementations would be greatly appreciated.

Regards,

Rohit

Hi Rohit

On the Embeddable Framework it doesnt open copilot automatically, you will need to either click on the scripts button to open the Interaction Window or you have the option to pop and show that interaction window whenever you like. Even keep it open and loaded constantly.

Since you are using a third-party connector, it is the responsibility of that third-party connector provider to build this experience. In theory they could pop automatically or be present always.

In the future, we are planning to make Copilot available as a standalone component that can be placed on your UI. This is part of the Composable Desktop SDK initiative that will be available to all customers later this year.

Thanks

Thomas

Hi,

We have a customer who has recently integrated Genesys Cloud with Dynamics 365 using a third-party connector. They are experiencing an issue where Agent Co-Pilot does not automatically load/pop up when an interaction begins.

Currently, agents must manually open the Co-Pilot script from the embedded client, which isn't ideal as the customer conversation is often already underway by the time the script is opened.

• Is this expected behaviour with the current embedded framework?

• Is this something that is expected to be addressed in the upcoming embedded framework UI updates?

• Are there any recommended interim workarounds or best practices (e.g. pop-out windows, embedding options, or agent workflows) to ensure Co-Pilot is available from the start of the interaction?

Any insights or experiences from similar implementations would be greatly appreciated.

Regards,

Rohit

Hi Rohit

On the Embeddable Framework it doesnt open copilot automatically, you will need to either click on the scripts button to open the Interaction Window or you have the option to pop and show that interaction window whenever you like. Even keep it open and loaded constantly.

Since you are using a third-party connector, it is the responsibility of that third-party connector provider to build this experience. In theory they could pop automatically or be present always.

In the future, we are planning to make Copilot available as a standalone component that can be placed on your UI. This is part of the Composable Desktop SDK initiative that will be available to all customers later this year.

Thanks

Thomas

Hi,

We have a customer who has recently integrated Genesys Cloud with Dynamics 365 using a third-party connector. They are experiencing an issue where Agent Co-Pilot does not automatically load/pop up when an interaction begins.

Currently, agents must manually open the Co-Pilot script from the embedded client, which isn't ideal as the customer conversation is often already underway by the time the script is opened.

• Is this expected behaviour with the current embedded framework?

• Is this something that is expected to be addressed in the upcoming embedded framework UI updates?

• Are there any recommended interim workarounds or best practices (e.g. pop-out windows, embedding options, or agent workflows) to ensure Co-Pilot is available from the start of the interaction?

Any insights or experiences from similar implementations would be greatly appreciated.

Regards,

Rohit

@Thomas Prendergast,  Based on feedback from the third-party vendor, the interaction window in embedded client is hosted by Genesys and does not provide any functionality to focus on specific tabs within it. What are your thoughts on it? How to do we automate it i.e. when agents click the interaction window it automatically focus the copilot widget. If this is a product limitation, any plan to include them in the feature roadmap?

Hi Rohit

On the Embeddable Framework it doesnt open copilot automatically, you will need to either click on the scripts button to open the Interaction Window or you have the option to pop and show that interaction window whenever you like. Even keep it open and loaded constantly.

Since you are using a third-party connector, it is the responsibility of that third-party connector provider to build this experience. In theory they could pop automatically or be present always.

In the future, we are planning to make Copilot available as a standalone component that can be placed on your UI. This is part of the Composable Desktop SDK initiative that will be available to all customers later this year.

Thanks

Thomas

Hi,

We have a customer who has recently integrated Genesys Cloud with Dynamics 365 using a third-party connector. They are experiencing an issue where Agent Co-Pilot does not automatically load/pop up when an interaction begins.

Currently, agents must manually open the Co-Pilot script from the embedded client, which isn't ideal as the customer conversation is often already underway by the time the script is opened.

• Is this expected behaviour with the current embedded framework?

• Is this something that is expected to be addressed in the upcoming embedded framework UI updates?

• Are there any recommended interim workarounds or best practices (e.g. pop-out windows, embedding options, or agent workflows) to ensure Co-Pilot is available from the start of the interaction?

Any insights or experiences from similar implementations would be greatly appreciated.

Regards,

Rohit