EasyChat 1.2.12

What changed

• AI settings now have a reply timing mode. strict_delay stays the safe default: AI always waits the shared chat_ai_delay, even if operator presence is wrong.
• operator_backup brings back the previous backup behavior: while an operator is online, AI waits the shared delay; when no operators are online, a shorter offline pause is used.
• The messenger_ai_tick queue job re-checks the current delay before saving an AI reply. If the pause is still active, the job is requeued without using normal attempts.
• Before inserting an AI message, EasyChat verifies again that the triggering customer message is still the last one. If an operator already replied from the admin panel, Avito, VK or another external channel, AI does not enter the conversation.
• VK channels also subscribe to message_reply, so replies sent directly from the native VK group interface are imported into EasyChat as operator messages. Older VK channels get a repair path during update.
• Android background sync no longer extends operator presence, so a push refresh should not make the operator look online.

Who should read this

• Stores where AI replies in Avito, VK, MAX, Telegram or the website widget.
• Teams that need strict protection: AI must not reply before the configured delay even when online status is unreliable.
• Teams that preferred the previous backup behavior, where AI steps in faster after operators leave.
• VK group administrators whose operators sometimes answer in the native VK interface instead of EasyChat.

What to check after update