Identify logged-in users: current availability
The installed widget does not yet expose a signed login-identity integration.
Identity and private data
The shipped widget does not provide a public identify, signout or userHash login API. Browser continuity and a pre-chat email are not proof of account ownership. Use the connector’s supported customer-verification flow before disclosing private order information.
Use the current pre-chat workflow
Configure supported fields at https://app.message.com/settings/chats/pre-chat. Treat submitted name and email as customer-provided context, not as proof of identity.
Separate history from authorization
Browser continuity can retrieve that browser’s previous chats. Website login and logout do not currently call a widget identity API. Do not deploy a userHash snippet or rely on an unsupported signout call to separate users on shared devices.
Verify private requests
For supported commerce connections, use the order-verification flow before releasing private data. Confirm the requirements of an authenticated chat integration with Message support before making it part of your login flow.