> 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/may-2026/may-19-2026.md).

# May 19, 2026

Hey Storylane! We've reimagined how RepX engages with users. RepX now has an upgraded user experience and is also faster.

### 💬 A new RepX experience

The new experience brings:<br>

* **a text-first chat experience** for your website visitors and
* **a voice mode**, which puts your RepX agent's voice front and center over the video&#x20;

***

### 📣 Starter questions and slide to drive engagement

* Add **starter questions**, which appear in the RepX launcher
* Add a **starter slide**, which is an intro slide that users will see when they start a new conversation with your RepX agent

***

### 🎨 Customizable branding and placement

From your RepX agent settings, you can now<br>

* position RepX's launcher on the **left** or **right** of the page
* brand the widget based on your brand's **primary colour** &#x20;

***

### <> Two ways to embed

From **RepX Chat** > **Settings** > **Embed**, you can now choose to embed RepX<br>

* as a **floating widget** that appears on top of your pages, similar to a traditional chatbot.
* as an **iframe** within some of your pages

\
If you're embedding RepX as an iframe, make sure to set <sub>`allow=microphone`</sub> in the \<iframe> tag so that RepX can hear what the user says when they grant mic permissions.&#x20;


---

# 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/may-2026/may-19-2026.md?ask=<question>&goal=<user_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.