Morning Matthew! We just finished migrating to web messaging from web chat (which is deprecating in June), and accomplished this same feat using the steps covered in this article.
In essence, how we named the custom attributes in the messenger widget snippet is exactly how the inbound Messenging flow sees/receives it. So all we had to do was add a Get Participant action at the beginning of our inbound messaging flow in order to assign those custom attritbutes to flow variables. This community thread shows an example.
Given we had already added those same custom attribute variables to our published script, we could then aassign those flow variables to the respective fields in the Set Screen Pop action in Architect.
------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology
------------------------------
Original Message:
Sent: 04-24-2025 09:10
From: Matthew Aubin
Subject: Passing Participant Data from Website
We have a custom configuration that passes website information into Genesys when a customer initiates a chat. I am looking into sharing this information with our sales agents using scripts, but feedback from Genesys states that because this is a custom configuration from our website that I should look here for assistance.
Any help or suggestions from our team here would be appreciated!
Thank you,
Matt A.
#Scripts
------------------------------
Matthew Aubin
Customer Service Manager
------------------------------