Introducing History for GPT Actions (AI Memory Key)
What's New?
We're excited to announce a significant enhancement to our GPT action: the ability to retain and utilize history. This new feature allows the GPT actions to produce more relevant and personalized responses based on past interactions with GPT actions.
Type of History
There are five types of history that can be stored:
- This Account: Remembers all GPT conversations across all workflows in the account where the history type is set to "This Account."
- This Workflow: Remembers all GPT conversations within the specific workflow where the history type is set to "This Workflow."
- Per Execution: Remembers all GPT conversations within the workflow for a single execution where the history type is "Per Execution."
- This Step: Remembers all GPT conversations for the specific action across multiple executions where the history type is "This Step."
- Custom: Allows the user to create a custom history type that can be used within the same workflow or multiple workflows.
How to Use?
- Enable the option in Labs.
- Select the "GPT Powered By OpenAI" action.
- Switch on "Enable history."
- Select the "History for" from the dropdown.
- Add system instructions if needed.
Advanced Options
- System Instructions: Users can add instructions to provide more information to the GPT action for more specific and desired output.
- Exclude Instructions from History: This toggle can be used when the user wants to exclude the system instructions from the history.
- Exclude Responses from History: If this is turned on, responses of this action will not be stored in the history. This is useful for responses that are sentiment-based (positive or negative) or any analytics received as output.
Points to Note
- If "Enable History" is switched on, then by default GPT-4 models will be selected.
- History will be independent for each contact.
In Case You Missed It: Introducing New Templates to Elevate Your Marketing Efforts
Stay ahead with our latest updates and make the most of your CRM experience. Visit our blog for more insights.
