### The Goal
Educate existing customers and partners on new or underutilized features, promoting increased usage and sales.
## Implementation Guide
### 1. Demo Structure
* **Step 1:** Introduce the feature as a solution to a particular problem, and invite users to explore it.
* **Steps 2-5:** Dive into the functionality of the feature using Storylane’s tooltips and hotspots, with a backdrop enabled. Use users's language, and talk about benefits instead of technical terms.
* **Step 6-7:** Summarize the benefits and end with a CTA to try out the feature and [add a secondary CTA](https://docs.storylane.io/storylane-knowledge-base/demo-editor/guides-and-flows/customizing-steps#config) to the additional resources for further learning or support.
{% hint style="info" %}
We suggest to focus on 1 feature - 1 demo. If you want to showcase multiple features to your viewers in a single demo, utilize Storylane's [Product Tour](https://docs.storylane.io/storylane-knowledge-base/demo-editor/guides-and-flows/flows-and-product-tour) which gives viewers the option to pick their own adventure.
{% endhint %}
* **Experience the Example Below** 👇
{% @storylane/embed subdomain="app" linkValue="p3ozvd6r0bqt" url="" %}
### 2. Keep Demos Ungated
* The goal is to increase the feature adoption, so make sure to keep demos ungated all the time, allowing readers to access the demo without barriers, and ensuring they grasp the basic concept.
### 3. Branding and Navigation
* Make sure the demos are in your company's [custom-branded domain](https://docs.storylane.io/storylane-knowledge-base/demo-editor/branding/custom-domain), to ensure high trust and reliability.
* Set up a Navigation Bar to allow viewers to jump between steps easily & quickly.
### 4. Leverage Integrations
* If you are sending product update emails, track and personalize demos by [passing data](https://docs.storylane.io/storylane-knowledge-base/demo-editor/personalization/personalize-from-url-params#passing-data-from-crm-or-marketing-automation-platform) from CRM or Marketing Automation platforms to increase engagement.
* Get notified in [Slack](https://docs.storylane.io/storylane-knowledge-base/analytics/integrations/slack) whenever someone relevant visits a demo, so that the Sales/CS team can have a clear overview and act if needed.
### 5. Demo Placement
* Deploy these demos within feature update emails, in the help center/knowledge base, and on partner portals.
* When sending emails, we suggest adding [demo GIFs](https://docs.storylane.io/storylane-knowledge-base/sharing-demos/export) to emails to reduce the text and make the content more visual.
* Utilize Storylane’s [embed features](https://docs.storylane.io/storylane-knowledge-base/sharing-demos/embedding) to seamlessly integrate the demos within different platforms, ensuring they are easily accessible.
## Customer Examples
* [**Onspring**](https://onspring.com/solutions/regulation/simple-cmmc-management-in-onspring-software/)
---
# Agent Instructions: 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:
```
GET https://docs.storylane.io/storylane-playbooks/retention-stage/feature-explanations.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.