The primary purpose of memory is for the Agent to learn and remember details about the end user (ex: Name, work location etc), and consequently use this information to improve the end user experience.

Expected benefits include reduction in latency, improved customer satisfaction and reduced token consumption among others.

Problem statement

Given that agents will now have memory and remember things about the end-user across chat threads, the end-user has no way to:

1. View details the agent knows about her, or

2. Add or remove datapoints from memory

Sample Use Case

End-user has been a long standing user of wxO chat (with agent memory implemented).

They told the agent previously that her base work location is Bangalore and she works as a Customer Success Manager responsible for sales.

They routinely uses wxO Flows for travel needs - specifically to book flights to customers.

Recently, she switched into a Solution Architect role that required for to relocate to Kochi. Now she wants to:

1. Know what the agent remembers as her base work location

2. Change her base location to Kochi, and remove her previous role as "Customer Success Manager" before booking her flight

User story

1. As the end-user, I should be able to store certain details with in the agent's permanent memory, so that these details are not periodically purged and can be easily edited for a dedicated place in the UI (ex: name, role, conversational tonality)

2. As the end user, I should be able to view the datapoints the agent remembers about me at any point of time, so that I have transparency & trust regarding agent memory

3. As the end user, I should be able to remove datapoints from agent memory and also add datapoints to the agent memory if I want to, so that data accuracy can be maintained

4. Chat: Users can have an incognito mode that does not save their chat to memory (activate/deactivate memory)

5. [Future] Chat: Maybe we provide disclaimers to indicate that certain things came from memory