Embedded agent web chat header customization support

1. Why it is useful?

The current embedded web chat interface offers limited customization options, particularly in the header area. Adding support for custom header elements (such as dropdowns, icons, or buttons) would allow organizations to extend chat functionality and provide users with additional contextual controls without modifying the core UI.
This flexibility enhances both usability and integration potential, enabling teams to create richer, more localized, and more brand-aligned experiences.

2. Who would benefit from it?

• Developers and solution designers who want to integrate chat with other web application settings or language options.

• Enterprises and global organizations needing a language selector, settings menu, or branding components directly within the chat header.

• End users, who would benefit from easier access to options like changing language, theme, or viewing help/settings without leaving the chat interface.

3. How should it work?

Providing instance method like in Gen1 (Acrher) web chat which allows to inject custom header configuration. The configurations would set type of header element, label, items and allows inject trigger event that can be handled by embedded page.

Supported use case could be language selection dropdown or quick action buttons like show privacy notice or email transcript.