Keep conversations tied to the right person and channel

A contact is the stable person record. A contact channel is that person's identity in a specific channel, such as webchat, API, skill chat, or AI teammate chat.

Conversations attach to contact channels. This lets Alloy keep conversations connected to the right person and the right communication path.

Public webchat can identify a visitor through a webchat token, a provided external ID, or a generated ID.

When the same external ID is sent again, Alloy reuses the same webchat contact channel. If profile fields such as name, phone, or email are supplied, the existing channel can be updated instead of creating a duplicate identity.

Internal chat currently supports AI teammate chat and Ally chat. The shared Chats surface lets users start conversations, open history, rename or delete threads, send attachments, stop generation, and use voice when enabled.

Users can use `Enter` to send, `Shift+Enter` or `Alt+Enter` for a newline, and `Alt+C` to toggle Chats.

Internal chat can support `@` teammate mentions and `#` shared-file mentions when sources are available.

File mentions are scoped to the current AI teammate's readable shared folders, not the organization's entire Storage tree.

The webchat widget can be embedded into a website and initialized with an API key, optional API and websocket URLs, event ID, contact data, language, positioning, and open state.

The widget supports public-session persistence, messages, attachments, iframe resizing, voice setup, and websocket updates for matching conversations.