> 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/july-15-2026.md). # July 15, 2026 Hey Storylaners! RepX goes mobile, and gets the lead and acounts views you've been asking for. ### 📱 RepX for mobile RepX is now fully responsive. Try it on your phone at [storylane.io/repx](https://storylane.io/repx). If your RepX agent's interaction mode is set to video, we default to a text + optional voice experience on mobile. This provides enough room for visitors to see your RepX agent's responses. ### 💼 Leads and accounts view Similar to the Demo Suite, you can now see a Leads and Accounts page within RepX dashboard. The **Leads** page * lists all **visitors who have shared their email** through RepX chat, * the **intent** determined based on their conversation and * the **timestamp of the last conversation** they had with your RepX agent The **Accounts** page * lists all **companies detected based on the IP address** or based on the email shared, * each account's **intent** determined based on the intents of conversations all leads from that company have had, * the **last conversation timestamp**, * the **total number of conversations from all leads** mapped to that company * the **number of leads** belonging to that company \ In both these views, you can filter leads and companies by intent and the date range when they had interactions with your RepX agent. --- # 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/july-15-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.