Self Checks

• I have read the Contributing Guide and Language Policy.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When configuring Conversation Opener, the Save button becomes disabled if the opener message is empty. However, the UI does not clearly indicate what is wrong.

This is especially confusing when suggested opening questions have already been filled in. From the user perspective, the modal looks mostly completed, but Save stays greyed out with no visible validation message, no highlighted field, and no direct indication that the opener message is required.

I was able to confirm that this is the current behavior in the frontend: the button is disabled only based on whether the opener message is empty, but there is no explicit field-level error state.

This creates a poor UX because users have to guess why they cannot save. It feels like the form is broken rather than invalid.

Suggested improvement:

• show a clear inline validation message such as Opening message is required
• highlight the opener input area with an error state, for example a red border
• optionally add stronger feedback such as focus, shake animation, or scroll-to-error when the user tries to save
• make the required nature of the opener message more visually obvious

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.