User Overview

A user refers to an end user who interacts with an Agent. GPTBots enables developers to assign unique identity IDs to different users. Using this user ID (UserId), user identities can be linked across various channels, supporting cross-channel identity unification, business queries via Tools, and management of user attributes and chat histories.

Definitions

User

A user is an end user who interacts with an Agent.

User ID (user_id)

A unique identifier assigned to end users by enterprise developers. Through the API, developers can set a UserId for an anonymous_id. For usage scenarios and advanced applications of UserId, see Set User ID.

• The user_id takes precedence over the anonymous_id.
• Multiple anonymous_id values can be associated with a single user_id simultaneously.

Anonymous ID (anonymous_id)

When users interact with an Agent via third-party platforms (such as Telegram, WhatsApp, LINE, etc.), GPTBots uses the unique identifier from that platform as the anonymous_id. For details on how anonymous IDs are generated, see [Anonymous ID Generation Logic](## Anonymous ID Generation Logic).

Third-party Platforms

GPTBots currently supports Agent integration with various third-party platforms, including Intercom, Webchat, LiveChat, Telegram, WhatsApp, and more.

Conversation ID (conversation_id)

The conversation ID (conversation_id) is a unique identifier generated based on the Agent, conversation type, and user_id (or anonymous_id). A conversationID serves as the smallest unit for isolating different business scenarios and typically contains multiple message IDs.

• conversationID automatically expires after 60 minutes, except for those generated via the API channel, which do not expire.
• When a conversationID expires on third-party platforms and widget channels, a new conversationID is generated to start a new conversation.

Message ID (message_id)

The message ID, or messageID, identifies a single message exchange between an Agent and a user, representing the smallest unit of conversation.

• messageID is generated by the GPTBots platform and cannot be customized by developers.
• messageID belongs to a conversationID, with one conversationID typically containing multiple messageIDs.

Conversation Type

Conversation Type (conversation_type) is used to identify the scenario in which a user initiates a conversation, such as Workspace-Workflow, WhatsApp, API, Workspace-Search, etc.

Conversation ID Generation Logic

When users initiate conversations with an Agent through third-party platforms, the system generates an anonymous_id based on the user's platform and automatically creates a conversationID from this anonymous_id to contain one round of dialogue between the user and Agent.

• When using the API, developers must first generate a conversationID and pass it as a parameter before starting a conversation with an Agent.
• For non-API channels, GPTBots automatically generates the conversationID. The specific business process is illustrated below:
  

Anonymous ID Value Logic

Anonymous ID Logic for Built-in GPTBots Channels

When a user is logged in to the GPTBots platform, the system automatically sets their GPTBots Account ID as the user_id and associates it with the anonymous_id (browser fingerprint ID).

Conversation Types

Conversation Type (conversation_type) is used to identify the scenario in which a user initiates a conversation. You can use the conversation_type field value to filter log data by scenario.

⚠️ Note: The field values in the table can be used as filter conditions when using the Get Conversation List API.
For third-party platforms like LINE and Telegram that support multiple channels, the "Agent-Log" allows filtering by secondary conversation types.
The field values in the table can also be used as the value for the anonymous_id_source field in the Update User ID API.