Editable & Persistent Form Responses (User Memory View)

Ability for users to view and edit their previous form submissions after completion. Form responses should be stored per user and act as an editable memory layer used across the studio.

I think we need some more explanation here. Any examples of other platforms that function the way you’re suggesting?

2 Likes

Hi there

In my case, I would like to use form as pricing input and store them in memories

Here’s the flow:

  • I define a default/base price for a product or service inside the studio

  • The user fills out a form that captures variables (scope, preferences, constraints, overrides, special conditions, etc.)

  • Those answers are stored as user-specific memories

  • When Pickaxe generates proposals/quotes, it uses:

    • the base price plus

    • the user’s stored form inputs to adjust or override pricing

The key requirement is this:

Users must be able to see and edit their previous answers, because those answers directly affect the output (pricing, offers, recommendations).

If this input where visible/stored in the container the user wrote them in it would lead less confusion among my clients. (Many of them are low-tech)

1 Like