> 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-updates/september-12-2026.md). # September 12, 2026 Hey Storylaners! Updates to the conversations page, a new launcher style and simulations. #### ๐ŸŸ  Icons as avatars In addition to supported avatars in RepX, you can bring a custom icon of your own and upload it in **Settings**. The icon you upload replaces the avatar face your visitors would see in text and voice modes. *** #### โœจ Video launcher style In addition to text box and buttonish, we now support a floating video launcher style. When you choose this style, the chosen AI avatar appears as a card within your webpage, when you embed it. *** #### ๐Ÿ’ฌ Filters, sorting and export in conversations view In addition to filter conversations based on **date ranges**, you can now filter them by * **intent** * **topics** * **page URL** * **if the conversation was marked as qualified** You can also **sort conversations** by intent, when they started and when they got completed by hovering over the column titles. Hit **Export** to pull the filtered set out as CSV - useful for handing a batch of conversations to your team or an external tool for analysis. *** #### ๐Ÿงช Automated simulations Test how your RepX agent answers before you put it in front of visitors. \ \ Simulations run a set of conversations against your latest configuration of RepX and show you how RepX responded so that you don't have to type out and re-enact each conversation every time you tweak something in the RepX dashboard. \ \ You can run simulations when you update playbooks or when you add, edit or remove training material to check the quality of answers and conversations. *** #### โž• More improvements * Demos no longer auto-play when presented in a conversation. Visitors will have to hit the play button to start playing them. * When your website visitor or your RepX agent sends a message, a sound is played on the browser. If the user has switched to another browser tab, the tab blinks to indicate that the RepX agent has responded to get their attention back on chat. --- # 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-updates/september-12-2026.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.