Using "conversation_details" Variable
Written by Medha Anand
Updated on April 19th, 2023
- Getting Started
- Bot Building
- Smart Agent Chat
- Conversation Design
-
Developer Guides
Code Step Integration Static Step Integration Shopify Integration SETU Integration Exotel Integration CIBIL integration Freshdesk KMS Integration PayU Integration Zendesk Guide Integration Twilio Integration Razorpay Integration LeadSquared Integration USU(Unymira) Integration Helo(VivaConnect) Integration Salesforce KMS Integration Stripe Integration PayPal Integration CleverTap Integration Fynd Integration HubSpot Integration Magento Integration WooCommerce Integration Microsoft Dynamics 365 Integration
- Deployment
- External Agent Tool Setup
- Analytics & Reporting
- Notifications
- Commerce Plus
- Troubleshooting Guides
- Release Notes
Conversation Details
conversation_details is a variable, that acts as a common store between all the code steps. The data stored in conversation_details is shared between all the code steps in the bot.
Data stored in this context variable will be saved at a conversation level for a given user. This means that the data will only be available till the conversation is active and is not marked as complete. Once the conversation is marked as complete, any data stored in this variable for the given user will be lost. This data is maintained on our server for a maximum of 3 hours after which it is permanently lost.
This variable should be used for storing contextual information related to the current conversation that the user is having with the bot. Some examples of this are policy IDs or policy details that the user is exploring in the current conversation.
conversation_details is used to store information that will be needed as long as the current conversation is going on. The initial information which conversation details contain is empty i.e. {}.
For instance, consider a use-case where a user wants to renew a policy, the user will choose the option to renew his/her policy and the API returns a list of policies associated with them. When the user selects their policy number, we cannot add it in an entity since the policy number can change and is perishable. But, we can use conversation details here, for storing this policy number.
Points to note:
- The information which is stored should be related to the conversation.
- The Data storage limit is 2500 characters.
- The data in conversation details stays for 3 hours only.
- This can be used to share data across code steps.
