Skip to main content
Follow these guidelines to ensure that your customizations remain stable, maintainable, and supported across product updates.

​
Use supported configuration options

Use only the supported configuration options documented in UI configuration to customize the chat interface. These include: Using only supported configuration options ensures that your customizations remain compatible with future releases.

​
Do not override internal CSS or modify the DOM

Do not target or override internal CSS classes, IDs, or selectors that are not documented as part of the public API. Do not modify, add, or remove DOM elements. Internal styling and DOM structure can change at any time, including the use of generated or hashed class names. These changes can break customizations without notice and increase maintenance effort. Always rely on the documented configuration options instead of inspecting or modifying internal styles or structure.

​
Validate customizations during upgrades

Validate all customizations before and after upgrading to a new version:
  • Review official release notes to identify changes that might affect your configuration.
  • Test your implementation in a non-production environment.
  • Remove or update any deprecated configuration options.
This process helps reduce the risk of regressions and production issues.

​
Request additional capabilities

If the documented configuration options do not meet your requirements, submit an enhancement request. Include a clear description of your use case, expected outcome, and business impact. Well-defined requests help prioritize future improvements and ensure that new capabilities address real user needs.