Genesys Cloud - Developer Community!

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hi Josh,

I'm not referring to the name you can set via participant data, and have it show in the chat window, I'm talking about the Remote Name which you can search in the interaction view, see below screenshots. For Webchat this Remote Name appears as per whatever you add to the capture form, I did add context.firstName and context.lastName which sets the name in the web messaging chat log for the agent, but not the Remote Name

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hi Nathan,

In Architect you can get the externalContactId for the conversation, and after that update the contact using the API below

Hi Josh,

I'm not referring to the name you can set via participant data, and have it show in the chat window, I'm talking about the Remote Name which you can search in the interaction view, see below screenshots. For Webchat this Remote Name appears as per whatever you add to the capture form, I did add context.firstName and context.lastName which sets the name in the web messaging chat log for the agent, but not the Remote Name

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hi Jan,

Thanks for the suggestion, most of our customers aren't using external contacts so this wouldn't work in most cases, an external contact could be added then set though, this does present the External Contact to the agent in the profile panel, but doesn't set the Remote Name.

The flow could look up for an external contact using the inbuilt action Search External Contacts

If an external contact doesn't exist, then create one using the post /api/v2/externalcontacts/contacts

I tested using the Search External Contact action (with hard coding my contactId) and this does set the External Contact against the interaction when I answered the web messaging interaction, opening the Profile panel IF the external contact is in the same division as the flow.

Unfortunately, this still doesn't set the Remote Name.

Hi Nathan,

In Architect you can get the externalContactId for the conversation, and after that update the contact using the API below

Hi Josh,

I'm not referring to the name you can set via participant data, and have it show in the chat window, I'm talking about the Remote Name which you can search in the interaction view, see below screenshots. For Webchat this Remote Name appears as per whatever you add to the capture form, I did add context.firstName and context.lastName which sets the name in the web messaging chat log for the agent, but not the Remote Name

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

Hi Jan,

Thanks for the suggestion, most of our customers aren't using external contacts so this wouldn't work in most cases, an external contact could be added then set though, this does present the External Contact to the agent in the profile panel, but doesn't set the Remote Name.

The flow could look up for an external contact using the inbuilt action Search External Contacts

If an external contact doesn't exist, then create one using the post /api/v2/externalcontacts/contacts

I tested using the Search External Contact action (with hard coding my contactId) and this does set the External Contact against the interaction when I answered the web messaging interaction, opening the Profile panel IF the external contact is in the same division as the flow.

Unfortunately, this still doesn't set the Remote Name.

Hi Nathan,

In Architect you can get the externalContactId for the conversation, and after that update the contact using the API below

Hi Josh,

I'm not referring to the name you can set via participant data, and have it show in the chat window, I'm talking about the Remote Name which you can search in the interaction view, see below screenshots. For Webchat this Remote Name appears as per whatever you add to the capture form, I did add context.firstName and context.lastName which sets the name in the web messaging chat log for the agent, but not the Remote Name

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',

For what it's worth, Nathan, your specific question about the Remote Name is also covered in greater detail here. In short, the Remote Name is only updated in very specific circumstances.

Hi Jan,

Thanks for the suggestion, most of our customers aren't using external contacts so this wouldn't work in most cases, an external contact could be added then set though, this does present the External Contact to the agent in the profile panel, but doesn't set the Remote Name.

The flow could look up for an external contact using the inbuilt action Search External Contacts

If an external contact doesn't exist, then create one using the post /api/v2/externalcontacts/contacts

I tested using the Search External Contact action (with hard coding my contactId) and this does set the External Contact against the interaction when I answered the web messaging interaction, opening the Profile panel IF the external contact is in the same division as the flow.

Unfortunately, this still doesn't set the Remote Name.

Hi Nathan,

In Architect you can get the externalContactId for the conversation, and after that update the contact using the API below

Hi Josh,

I'm not referring to the name you can set via participant data, and have it show in the chat window, I'm talking about the Remote Name which you can search in the interaction view, see below screenshots. For Webchat this Remote Name appears as per whatever you add to the capture form, I did add context.firstName and context.lastName which sets the name in the web messaging chat log for the agent, but not the Remote Name

Hey @Nathan Kaden 

This can be updated by using a Set Participant Data block in your web message flow to update the attribute "name" 

When an agent receives the interaction, that is what is displayed to them. You can populate any value captured by the bot into that attribute

Hi Angus,

Thanks for pointing this out, this will work for when we're using a custom capture form to collect detail pre launching the web messaging session.

Do you know of a way to update this name from within the Architect Inbound Message Flow for when we're using a bot to capture the name?

Use the Database.set command and set name.

Genesys("command", "Database.set", {
          messaging: {
              customAttributes: {
                          name: 'Messagers Name',