Channels

Identity depends on the access channel. Web uses mint + userCode; email and WhatsApp resolve against UCT contact fields bound to the receiving mailbox / number.

Web

Authenticated: mint with systemName, companyCode, userCode.
Anonymous: omit userCode; guest history must not attach to a real UCT user.
Details: Authentication and Widget.

Email

Match sender to UCT userCompanyMail or userPrivateMail (normalize case / trim).
Tenant and system come from the mailbox config, not the email body.
Unknown sender: fixed “not registered” reply — no other user’s data.

Match sender mobile to userCompanyMobile or userPrivateMobile (normalize digits / leading +).
Tenant/system from the WhatsApp provider / number config.
LID / privacy IDs: one-time link flow (ask for registered mobile or userCode) before go-live.

Knowledge isolation

Anonymous / system / company knowledge tiers must not leak across products (e.g. TravelMatic ↔ SimpleCRS). Only promote systems with uploaded knowledge for RAG acceptance.

Channel toggles and configs live in ChatAdmin. See Go-live for UAT checklists.