EasyChat 1.14.0

Current for EasyChat 1.18.1+

What changed

EasyChat now recognizes a signed-in customer through their protected CMS session on the very first widget message. The customer no longer has to start a previous conversation or repeat their email address.
When a visitor starts as a guest, signs in on the site, and continues, both the widget and operator workspace retain one conversation. The customer card is enriched automatically with CMS-verified email and phone details.
Orders are resolved directly through the immutable authenticated account ID in OpenCart, WooCommerce, Shop-Script, and 1C-Bitrix. This is more reliable than email- or phone-only matching and works on a first contact.
Shared-device account changes are isolated: a new account cannot read the previous account’s conversation and receives a separate widget session.
The short-lived sign-in assertion is bound to one widget session, is never kept in browser storage, and does not expose contact details in a URL.

Who should read this

Online stores whose customers ask about orders through the widget, and operators who need an accurate customer card without duplicates or repetitive identity questions.

What to check after update

After updating

Sign in to a test storefront customer account and send its first widget message. Confirm that the widget header shows verified sign-in and EasyChat receives the customer’s email and phone. Start another test conversation as a guest, sign in, and send another message; the history must remain in one conversation. Open the customer card and confirm that orders are available without asking for the email again.

Last updated on August 17, 2026

EasyChat 1.15.0 EasyChat 1.12.2