Genesys Cloud - Main

HI Angelo, is there a deployment guide or blueprint to do this?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Hi Brian - for now you can refer to suggested solution I mentioned in previous post, based on Participant Data attributes rather than External Contacts: we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name". This would work with our native Agent UI.

Note that if you use Embeddable Framework (for CRM integration), see comments in this Idea for further guidance.

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Hi Brian - for now you can refer to suggested solution I mentioned in previous post, based on Participant Data attributes rather than External Contacts: we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name". This would work with our native Agent UI.

Note that if you use Embeddable Framework (for CRM integration), see comments in this Idea for further guidance.

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Hi @Angelo Cicchitto,

It may just be me, or something with my dev org, but I am not sure this is a fully functioning solution.

In a digital bot flow as an example, we have no way to set participant data natively, so we must do this in the message flow.  But in the message flow, we have no way to engage in a 2 way "Ask for" type tool that I can see to do this, we only have the Send Response which is a one way communication. 

Of course we can work around this, but it seems a bit weird to have go to the extent of building a separate "Say your name" bot to capture the value, and then we have to capture the output slot and/or evaluate the intent returned to finally set the participant data.  It's just a lot for something that could likely be done in one "wait for reply" tool and then just parse the response.

I could have sworn in the message flows before the new version was pushed out that there was a native 2-way tool just like that which would wait for a reply before continuing or timeout, but maybe my memory is fuzzy there and I am having a massive brain fart.

Cheers,

Hi Brian - for now you can refer to suggested solution I mentioned in previous post, based on Participant Data attributes rather than External Contacts: we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name". This would work with our native Agent UI.

Note that if you use Embeddable Framework (for CRM integration), see comments in this Idea for further guidance.

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Valid comment - see this Idea, now in Development: https://genesyscloud.ideas.aha.io/ideas/DXVBOTS-I-25

Hi @Angelo Cicchitto,

It may just be me, or something with my dev org, but I am not sure this is a fully functioning solution.

In a digital bot flow as an example, we have no way to set participant data natively, so we must do this in the message flow.  But in the message flow, we have no way to engage in a 2 way "Ask for" type tool that I can see to do this, we only have the Send Response which is a one way communication. 

Of course we can work around this, but it seems a bit weird to have go to the extent of building a separate "Say your name" bot to capture the value, and then we have to capture the output slot and/or evaluate the intent returned to finally set the participant data.  It's just a lot for something that could likely be done in one "wait for reply" tool and then just parse the response.

I could have sworn in the message flows before the new version was pushed out that there was a native 2-way tool just like that which would wait for a reply before continuing or timeout, but maybe my memory is fuzzy there and I am having a massive brain fart.

Cheers,

Hi Brian - for now you can refer to suggested solution I mentioned in previous post, based on Participant Data attributes rather than External Contacts: we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name". This would work with our native Agent UI.

Note that if you use Embeddable Framework (for CRM integration), see comments in this Idea for further guidance.

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?

Hi Brian - for now you can refer to suggested solution I mentioned in previous post, based on Participant Data attributes rather than External Contacts: we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name". This would work with our native Agent UI.

Note that if you use Embeddable Framework (for CRM integration), see comments in this Idea for further guidance.

Any update on when this will be available for web messaging instead of web chat since web chat is being phased out?

Unfortunately we don't have a blueprint for this, it's a fair ask: we are planning to make this process a lot easier, including updates to External Contacts.
For the interim, we've restored a legacy Agent UI feature for Web Chat, making it possible to update the customer name visible in Agent UI by updating Participant Data attribute named "name".

HI Angelo, is there a deployment guide or blueprint to do this?