Update Customer Identifier

The Update Customer Identifier Data Operation is used to update the unique identifier associated with the user that is currently having a Conversation.


Enterprise Feature

This Data Operation requires an ENTERPRISE license. If you would like to enable this feature for your Airkit Organization, please contact your Airkit representative or contact [email protected].

Use Cases

Customer Identifiers can be used in tandem with the Find Conversations by Customer Identifier Data Operation to maintain context across conversations. As Customer Identifiers need to be unique for each user, it is not uncommon to associate them with some property tied directly to the user, such as their phone number or email address. Update Customer Identifier Data Operation allows you to keep using these sorts of things as identifiers, even if:

  • a user changes their phone number, or
  • a user changes their email address.

Data Operation Properties

Conversation ID

Expects type text. This text should correspond to the identifier that a Conversation got assigned upon being initialized; this identifier will be stored under channels.message.conversationId in the relevant Session.

This property defines the Conversation that the Update Customer Identifier Data Operation will reference in order to determine the customer whose identifier will change.

Customer Identifier

Expects type Text.

The new Customer Identifier. This value should be unique for each user even after it is updated.

Run Results

By default, Airkit stores the output of this Data Operation in an auto-created variable called customer-identifier that can then be passed into subsequent operations. The value of customer-identifier indicates whether or not the Customer Identifier was successfully updated.


Customer Identifiers can only be updated if the Customer is having a Conversation is occurring in deployment.

Unlike most Data Operations, the Update Customer Identifier Data Operation cannot be run without referring to a deployed application. Before you can test any instance of this Data Operation, it must be able to refer to a published Conversation Chat Bot. For more on how to publish a Conversation Chat Bot, see Configuring Conversation Chat Bots.