Visitor, contact and authenticated user
Keep browser recognition, customer history and identity verification separate.
Visitor
A visitor record represents a customer interaction identity, including the widget’s browser token and submitted profile details. Browser storage helps continuity but is not a login credential for your own product.
Contact
A workspace contact can group linked visitor records and support history. Authorized agents use this context to see previous conversations. A contact record does not itself prove that a new person typing the same email is that customer.
Authenticated user
Your product’s authenticated user is established by your own login system. The public Message widget currently has no signed-login identify API. An imported CRM record or an email match alone is not equivalent to a verified website session.
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.