Anonymous or identified
You can always send the name, email and phone without a
userHash. Your team sees who is talking, but the history stays on that device.
Send who the user is
userHash, the call only updates the details.
Compute the userHash on your backend
secret: a random string of your own, at least 32 characters, kept on your server (an environment variable). Talqui never sees it.tenantId: your tenant ID.userId: your user’s ID in your system, the same one every time.
Send your own user ID
If you use webhook notifications, also send your user ID as contact metadata. The webhook returns it, so your backend knows which of your users received the reply:Logout
When the user logs out, forget them on this device. Otherwise the next person who logs in sees the previous user’s conversation.Good to know
- A conversation started anonymously doesn’t move to the identified user. After
identifywith a newuserHash, the chat shows that user’s history. - Calling
identifywith a differentuserHashon the website switches users on the spot: the previous visitor’s conversation is dropped from the page first.