> 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/august-2026/august-28-2026.md). # August 28, 2026 Hey Storylaners! This release is mostly about the training page — the part of RepX you spend the most time in when setting up an agent. It got faster, easier to scan, and better at handling the messy. ### 🎓 Training page, rebuilt #### **Updates to webpage training experience** * When you add URLs for RepX to learn from, you can **enter multiple URLs** one by one and RepX will crawl all those pages to learn from the content on those pages. You can also check the resync box. * When you add a URL and want RepX to crawl all the pages linked from that URL, RepX lists all discovered URLs **grouped by directories**. * If you don't want RepX to learn from your `/blogs`, for instance, you can uncheck the entire directory. * You can now see tabs in the URL section to filter URLs by the ones that have been **queued for training**, which ones have been **processed**, which ones have **failed** to get ingested. You * Previously, if URLs had fragments or anchors (anything after `#`), the part after # used to get truncated. This no longer happens. *** ### 📄 More file types in transcript uploads Sales call transcripts can now be uploaded as `.docx` and `.txt`, not just as `.vtt`. FAQs generated based on uploaded transcripts are used by RepX when generating answers. *** ### 📊 Marketo integration RepX now writes conversation data to Marketo - leads, activities, and the RepX fields on each record. You can set it up from [**Settings → Integrations**](https://app.storylane.io/repx-dashboard/settings/). *** ### 🌍 Multilingual support (in voice and text responses) RepX can now understand and respond in different languages, including Italian, French, Spanish, German, etc. \ \ Visitors can switch languages mid-conversation and RepX will respond in the same language the visitor talks or sends messages in. --- # 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/august-2026/august-28-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.