> For the complete documentation index, see [llms.txt](https://docs.kasko.io/product-builder-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasko.io/product-builder-manual/product-features/save-for-later.md). # Save For Later The feature allows customers to temporarily save the existing progress and temporarily leave the webapp, and customers will receive an email with a secure link that will take them back to the webapp with all the data prefilled and continue the flow. Along the customer journey, customers will see the save for later button and they can click it whenever they want to save the progress and come back later. When the button is clicked, an email will be sent to the customer, with a link taking customers back to the webapp on the page they left before and it will prefill all the data that was previously saved. To set this up, you will first need to go to the Product Feature section and enable Save For Later. You can then decide if you want to turn on **Autosave** feature as well.

Enable this function by clicking the switch and making sure it is on the right side

{% hint style="info" %} **Autosave feature** will automatically capture the customer data once the email is provided without customers clicking any button. {% endhint %} Once the feature is enabled, you will need to configure the `save_for_later_triggered` email. (read more in [Emails](/product-builder-manual/fundamentals/create-your-first-product/emails.md)) and make the related changes (where to include the save for later button) in your webapp (read more in [Webapp](/product-builder-manual/fundamentals/create-your-first-product/webapp.md))

After enabling Save for Later, you can choose to turn on Autosave Progress and see and configure all emails


--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kasko.io/product-builder-manual/product-features/save-for-later.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.