EasyChat 1.2.2

What changed

• EasyChat now normalizes message time from Telegram, MAX, Avito, the web widget, the Android app and the admin panel through one server-side rule. This protects conversations when one external system sends UTC time and another sends the store’s local time.
• Conversation order is more stable: if several messages land in the same second, EasyChat also uses message_id, so cards do not move after a page refresh.
• After sending a message, the Android app now uses the exact server message_id and timestamp. The temporary local card is replaced by the real server record without jumping in the history.
• AI replies now read the same normalized history that the operator sees. This reduces the risk of AI using messages in the wrong order.
• Support teams get safe diagnostics for old timestamps: a suspicious conversation can be checked without printing message text, and repairs should be applied only after a database backup.

Who should read this

• Stores that use several channels at once: Telegram, MAX, Avito, the widget and Android operators.
• Operators who noticed that messages could visually change order after a page refresh.
• Teams that use AI replies: the history order now follows unified server rules.
• EasyChat support: old conversations with a wrong timezone can be checked safely and repaired only when needed.

What to check after update