> 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/repx-chat/training-repx/demos-images-and-videos.md). # Demos, images and videos Learn how you can include content that RepX presents to visitors ### Interactive demos Demos let RepX *show* your product to your visitors, in addition to *describing* it. From the Training section, **add Storylane demos that show product capabilities** that you'd like buyers to explore deeply.

Any published demo that you create within your Storylane account can be added to your RepX agent. For each demo you add, you can provide:
* **a description** - what the demo shows and who it's for. RepX uses this to decide when the demo is relevant to a visitor's question or use case. * **a display instruction** - plain-language guidance on when to present demo. A display instruction gives you control over when a demo shows up. Here’s an example display instruction that you could use if you’re including a demo about reports or analytics in your product: "Show this to visitors asking about native reporting or dashboards, but not to visitors who are asking about Tableau integration." ### Videos Similar to demos, you can **upload MP4 videos.** If you already have a library of overview and explainer videos built over time, you can have RepX present them in conversations.\ \ RepX will present the videos you upload or connect along with the answers it generates, wherever relevant. Similar to demos, for each video, you can include a **description** (that tells RepX about the video you’re uploading) and a **display instruction** (that guides RepX when to present the video and when not to). ### Images While you can use demos to show an interactive experience of your product’s broad capabilities, you can use images to provide images that supplemnts answers RepX provides. Images are great for competitive comparisons, for providing a quick glance of your pricing plans, or for case studies and ROI material. \ \ RepX will present them along with the answers it generates. Similar to demos, for each image, you can include a **description** (that tells RepX about the image you’re uploading) and a **display instruction** (that guides RepX when to present the image and when not to)

--- # 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/repx-chat/training-repx/demos-images-and-videos.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.