Instead of having a trigger conversation started. Have a pre-baked in message feature in the conversation soon as the user opens the webchat. Cause what's happening now is: The user sends a message before the trigger sends out the message and confusion errupts. e.g. Trigger is in place User sends out a message before the event triggers (conversation started) - Do you guys have express shipping? Conversation started triggers first message (welcome message) -Hey welcome to XYZ brand, what can we do for you today? I'm pointing this out because we've had this issue occur multiple times and then the user just may not answer. https://cdn.discordapp.com/attachments/1435561491578486846/1435561492236730429/image.png?ex=690c6a53&is=690b18d3&hm=e9f1d2fe506a16af2ee628a9503bde99c8e43c02a94e0b43f4c94b61fc21a8cf&

Hey, just to make sure I'm understanding your ask properly, are you referring to a greeting message? Example: I click open a chat bubble, and instead of typing first, there's a small proactive greeting: "Hi, welcome to XYZ brand, what can we help you with?"

@early-cartoon-84199 have you "Always Alive" active?

Nope, does it fix that?

Hi SabriH, Yes, we use the trigger Conversation Start to display a message before the user begins the conversation. It would be beneficial to have a field in the webchat configuration where we can insert the bot's first message, which is sent during the UI build. https://cdn.discordapp.com/attachments/1435561491578486846/1436290378427928576/image.png?ex=690f1127&is=690dbfa7&hm=8f94c5c73da9505d22a6790f6e59cbf647cdae0e665fec2c70686542edba1e32&

Ok noted! Would it help if it was a configuration setting in the Webchat configurations?

Yes, the message should appear in the UI without waiting for the bot or conversation to be fully ready.

If this goes to production it's a major quality of life update