Background / Current Behavior
When using Input form trigger Agents, pressing the button to run the Agent causes the first message in the conversation to be automatically populated as either:
- The Goal message, if it is configured for the Agent, or
- The Agent name, if no Goal message is configured.
In other words, the initial user-side message is currently tied to the Goal message (when present) or falls back to the Agent name.
Issue
Because the initial message is automatically derived from the Agent name or Goal message, it cannot always be phrased in a way that is natural or intuitive for end users. This can lead to confusion, especially when:
- The Agent name is technical or internal-facing.
- The Goal message is written for configuration/administration purposes rather than as a user-facing utterance.
Requested Enhancement
Add a feature that allows administrators to explicitly customize the initial message sent when an Agent is executed via an Input form trigger button.
- If a custom initial message is configured, that text should be used as the very first message when the Agent is triggered.
- This should be independent from both:
- the Agent name, and
- the Agent’s Goal message.
Expected Benefits
- The first message can be tailored to each Agent’s specific use case, improving clarity.
- Users see a natural, context-appropriate message instead of an internal Agent name or configuration-oriented Goal message.
- Overall user experience is improved, and users are less likely to be confused about what the Agent will do or how to interact with it.
