> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/storylane-playbooks/retention-stage/customer-support-and-help-documentation.md).
# Customer Support & Help Documentation
Interactive demos eliminate the need for lengthy documentation, monotonous tutorials, and never-ending meetings, paving the way for a more engaging and efficient learning experience.
### The Goal
Enhance user understanding, reduce support tickets, and accelerate the onboarding process through interactive demos.
## Implementation Guide
### 1. Demo Structure
đź’ˇ For this purpose, consider the interactive demo as the how-to guide. Each demo should be straightforward and simple.
* **Steps 1-2:** Start with a common challenge or question that users have. Introduce the demo's objective, i.e., what the user will learn or solve by the end of the demo.
* **Steps 3-6:** Walk through the primary steps, using Storylane’s tooltips and hotspots. Provide additional insights or tips, utilizing Storylane’s [secondary CTA](https://docs.storylane.io/storylane-knowledge-base/demo-editor/guides-and-flows/customizing-steps#config) for supplementary information.
* **Steps 7-8:** Recap the key points, reinforcing the learning objectives. Provide resources for further learning or support contacts.
### **2. Demo Placement:**
* **Help Center:** Embed demos next to relevant articles or FAQs.
* **Product Interface:** Utilize Storylane’s feature to deploy demos within the product interface, offering guided tours as users navigate.
* **Support Tickets:** Include links to relevant demos in automated responses or support replies, aiding self-service resolutions.
## Customer Examples
* [**Sky High Security**](https://success.myshn.net/Skyhigh_Data_Loss_Prevention/Policy_Settings/Enterprise_DLP/Cloud-to-On-Premise_Evidence_Synchronization)
* [**Lifeomic**](https://lifeomic.com/mobile-app-support/)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.storylane.io/storylane-playbooks/retention-stage/customer-support-and-help-documentation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
