Opal Chat currently requires users to manually select an instance each time they start using it. In scenarios where a user only has access to a single instance, this step introduces unnecessary friction.
It is also easy to overlook this requirement. When no instance is selected, the chat may return connection errors without clearly indicating that the issue is related to a missing instance selection. This creates a confusing user experience and makes troubleshooting harder than necessary.
Impact:

Adds an avoidable manual step to the user workflow
Leads to unclear or misleading error messages
Increases friction for new or infrequent users
May negatively impact user adoption and confidence, especially at scale

Example scenario:
When requesting CMP-related information using out-of-the-box agents, the chat can fail with connection errors if no instance is selected, without providing guidance on the root cause.
Suggested improvement:

Allow users to set a default instance that is automatically selected
Provide clear prompts or validation if no instance is selected, instead of returning generic connection errors

Expected outcome:

Smoother user experience with fewer interruptions
Reduced confusion and support overhead
Improved usability and adoption across broader user groups