---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/conversational-interfaces

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Configure interaction record to store clientSessionId

# Configure interaction record to store clientSessionId in Virtual Agent API {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

You can configure to store clientSessionId to support third-party chat applications.

## Antes de Iniciar

Role required: admin

## Procedimento

1. Navigate to All, and then enter <kbd class="ph userinput">sys_cs_provider_application.list</kbd> in the filter.
2. Select the VA Bot to Bot Provider Application record to open it.
3. In the Provider Channel Identity form, select the Provider Identity Properties related list and click New.
4. On the Custom Adapter Property form, fill in the fields.  
   {#va-api-interaction-record-third-party-chat__table_fvw_j1j_cgc__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the customer adapter property, such as <kbd class="ph userinput">third_party_chat</kbd>. |
   | Value | Enter <kbd class="ph userinput">true</kbd>. |
   | Description | Enter an explanation for this property: <kbd class="ph userinput">The custom adapter property to contain the client sessions by the supported third-party application in the Interaction record.</kbd> |
   [Tabela 1. Custom Adapter Property form]

   {#va-api-interaction-record-third-party-chat__table_fvw_j1j_cgc}
5. Click Submit.