Minichat, stability, and template corrections

Features

Improvements

Bugs

General Summary

We have released improvements to the stability of the platform's communication flows. The minichat now functions correctly in all environments, with a more stable real-time connection, automatic reconnection, a visual conversation status indicator, and enhanced support for images and documents. Internal flows have also been fixed to ensure more consistency in sending Meta templates and activating Form Flow.

Features

Minichat: Added visual conversation status indicators to the chat, alongside support for sending and receiving messages, images, and documents. This creates a smoother and more transparent experience for minichat users, allowing operators to intervene in the conversation if necessary.

Improvements

Minichat: The minichat received stability improvements to work correctly in all environments. The stability of real-time communication was also enhanced, incorporating automatic reconnection after internet drops.

Bugs

Template Header: The API now accepts Meta templates with a TEXT header type without requiring the header field in the payload. Consequently, these templates work correctly again, while the validation of media header templates remains unchanged.

Form Configuration: Adjusted the Form Flow activation logic to consider the conversation's `avatar_id` when fetching the configuration. Now, when there is no specific configuration for the avatar, the system falls back to the host's generic configuration (`avatar_id` is null), always prioritizing the specific configuration. This prevents data capture failures due to conflicts from multiple records and correctly respects the configured activation for each avatar.