I recorded this loom video to give you a better idea of my suggestion. It’s 4m long and you can speed it up if you’d like.
An option for the pickaxe maker to assign a specific user memory with the particular form details would be helpful also. I am having my users input the same answer on almost all my forms. Like who is your target audience? It would be cool to have a button where they could insert their stored memory and we can associate in our form user field as an option to suggest they insert their stored memory for this field if possible.
It could be helpful also as the use case you mentioned someone used a user memory for repeated using the user’s favorite movies. If it’s worth storing in user memory I think it’s worth giving an option to populate a form with the user memory data field.
3 Likes
This is a very good suggestion. Second that!
2 Likes
I agree, I wish users had the ability to put information in their profile that is used with the tools. Such as about company, target audience, background and skills, industry, etc.
You can make this a little bit easter by creating a drop down menu selection of 4-5 most common selections so the user doesnt t have to type it every time.
This goes along with my feature request of allowing user to upload knowledge specific to their profile for exactly this reason…
3 Likes
Absolutely agree!
Currently, we can have the prompt pull the User Memory into it - however, the User can’t see what was used to answer the Form question.
If we are able to pre-populate Form questions with user memory that the User can modify that would be a fantastic user experience upgrade!
As part of this, there’s two types of memory about the user to consider:
(1) User accessible memory. This should be accessible by the user and would most commonly represent memory recorded from answers and inputs the user provided.
(2) User non-accessible memory - this is memory about the user that the system has but the user cannot see. It is memory defined about the user that the user wasn’t involved in sharing - it could have been loaded from other sources, synthesis from user interactions by prompts in backend, etc. These memories are intended to help the businesses better understand their customers and personalize user experience but aren’t necessary for the user to see.
It’s important to be able to differentiate what the user can see & access vs what they cannot.
This feature of loading memory into the form would also unlock a ton of functionality on what forms can do for a user!
Just FYI I just got off the office hours call today and if you agree with my suggestion, I believe the Pickaxe team wants you to click the ‘vote’ button on the left of each post title.
Your comment doesn’t stand out as much as seeing 10+ votes on a suggestion does.
I see favorable 4 comments and 2 votes.
I believe our ideas will be considered faster when we have more votes on the ideas.