Robert - input collection via messages does require Bot Flows, to build that transactional logic (waiting until next input from User). With regular Inbound Message Flows we can only detect Participant Data.
We do plan to remove Chat v1 as part of our deprecation process, planned by end of June 2024.
------------------------------
Angelo Cicchitto
Genesys - Employees
------------------------------
Original Message:
Sent: 05-10-2024 21:28
From: Robert Wakefield-Carl
Subject: ACD Web Chat - improved behavior on Custom Attributes updates via Flow
Angelo,
Will Web Messaging have the ability to add files of collection before the session or will we always have to use a bot?
On the deprecation, if a client just does not have the recourses to swap out chat V1, will it actually stop working on 6/30?
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 04-23-2024 05:22
From: Angelo Cicchitto
Subject: ACD Web Chat - improved behavior on Custom Attributes updates via Flow
Hello Community - we detected improper behavior in legacy Web Chat that has to be adjusted: after the improvement is released all updates to custom attributes set from within a chat flow (both new and existing fields) will be persisted throughout the entire duration of interaction, including wrap-up and disconnect. This is planned over the next week.
As a reminder, ACD Web Chat v1 is soon to be deprecated, see this announcement: https://help.mypurecloud.com/articles/deprecation-removal-of-acd-web-chat/
#DigitalChannels
------------------------------
Angelo Cicchitto
Genesys - Employees
------------------------------