Help
# supportb
brandon holley
11/18/2024, 3:39 PMCan I vapi agent utilize memory? How if so?
brandon holley
11/18/2024, 3:40 PM@Vapi Can I vapi agent utilize memory? How if so?
v
Vapi
11/18/2024, 3:40 PM@brandon holley
Yes, VAPI agents can utilize memory to maintain context and manage state across multiple interactions. This is typically achieved through the use of session management where the agent keeps track of the conversation state and user data within a session. Persistent storage can also be used to remember user preferences or any other data between sessions.
To implement memory in your VAPI agent, you would typically:
1. Use variables to store temporary data within a session.
2. Implement session management to keep track of the conversation flow.
3. Use a database or a similar persistent storage solution to save data that needs to be remembered across different sessions.
If you need specific instructions on how to set up memory for your VAPI agent, please refer to the Assistant API reference for detailed guidance or ask support for more info on this.
Vapi
11/18/2024, 3:42 PM@brandon holley
Absolutely! VAPI agents can utilize memory to provide a more personalized and efficient experience. The persistent assistant feature allows the agent to remember context and user preferences across multiple interactions. This is achieved by storing data in a session or a database that the assistant can access and update as needed.
To use memory in your VAPI agent, you would typically:
1. Enable session management in your assistant's configuration to maintain context between API calls.
2. Use a database or a similar persistent storage system to save user data and preferences.
3. Implement logic in your assistant to read from and write to this storage, allowing the assistant to recall past interactions and user information.
If you need more specific guidance on how to implement memory in your VAPI agent, please let me know what you're looking to achieve, and I can provide more detailed instructions or direct you to the appropriate resources.
Vapi
11/18/2024, 3:42 PMYou can continue this conversation by mentioning me in the message.
s
Shubham Bajaj
11/19/2024, 9:39 AMHey @brandon holley can you describe your issue clearly such as :-
- What response you expected to get
- What response you actually got instead
s
Saltlife Kid
04/25/2025, 5:01 PMHi I would love a detailed walkthrough on how to set up memory for my vapi assistant.
s
Sahil
04/25/2025, 5:54 PMVapi doesn’t have built-in persistent memory, but you can set it up by managing conversation history externally and feeding that context back into your assistant when needed. After each call, send the call data to your make(can be n8n or zapier) webhook to send the call data such as transcripts, summaries, or key points to an external storage. You can use something simple like Google Sheets or Airtable through [Make.com](http://Make.com), or something more advanced like database or vector database if needed. They both will work. Once the data is stored and linked to each user, usually by phone number or user ID, you’ll want to retrieve that information when the user calls back or when you initiate an outbound call. So basically for outbound example, it will see that number and look at the information about that number. Make sure to add the information dynamically through the prompt. By dynamic I mean 'the person calling's name is {{callername}}.' In your prompt and the name will change dynamically based on who is calling. The basic workflow is: Vapi sends call data to [Make.com](http://Make.com), Make stores it, and when a new call happens, Make retrieves the history and injects it back into Vapi.