Hello Sathish,
I believe you can address it by implementing custom participant id by using the messenger SDK deployment configuration. WHen initializing the Messenger, you can pass the user's information using the deploymentId configuration. This also allows you to add custom attributes object that includes the user's id info.
Here is an example:
Genesys("messenger", {
deploymentId: "your-deployment-id",
customAttributes: {
firstName: "User's First Name",
lastName: "User's Last Name",
email: "user@example.com"
}
});
Hope this helps!
------------------------------
Cameron
Online Community Manager/Moderator
------------------------------
Original Message:
Sent: 01-09-2026 03:06
From: Sathish Mohanakrishnan
Subject: Web Messenger
Hello,
We have setup web messenger in our environment and it is working as expected. We are experiencing a small issue with regards to the participant information (identity). We are using two way from our website to connec to webmessenger . One is SSO and one is non-sso. Both are being used by employees. Non-SSO is being used predominently used by users who are logged out of their PC or unable to login into their PC.
While employees using SSO, their name is showing instead of participant however, when employees use non-sso, their email address or name does not show and only shows as "Participant". Due to this it is becoming diffficult to identify who have reached out.
We were able to pass in their email address in the messenging history but that does not solve the issue. Any direction on this will be helpful
#DigitalChannels
------------------------------
Sathish Mohanakrishnan
Principal Systems Engineer
------------------------------