> 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/june-2026/june-23-2026.md).
# June 23, 2026
Hey folks! Conversations your RepX agent has had are now visible in Storylane's RepX dashboard.
### 💬 Conversations page
You can access the Conversations page from RepX Chat dashboard - here's a [direct link](https://app.storylane.io/repx-dashboard/conversations). For every conversation, we show:
* a **conversation summary**, alongside the full transcript
* the **location** of the visitor (city, state and country)
* an **intent** level - determined automatically as **high**, **medium** or **low** by the topics your visitors touched upon
* a **list of topics** the visitor discussed
* a timestamp of when the **conversation started** and when it was **completed**
* **company information** (domain, industry, revenue range, employee size, confidence score about the detection) based on their IP address
Once you open a conversation, you can use the **left** and **right** arrow keys to navigate across the list.
### 🔡 Conversation variables
With conversation variables, you can now extract information from conversation that matters to you. There are default conversation variables - you can also create custom ones. When you create a custom variable, you can write a prompt to go with it. \
\
At the end of every conversation, RepX runs the prompts you've configured against the conversation and extracts relevant information based on the prompt. You can then send the extracted information to your CRM or other systems through Zapier or webhooks. \
\
There are four default conversation variables: **visitor name**, **email**, **phone number**, **qualified.** The prompt for the 'qualified' variable is editable. If a conversation passes the criteria set through this prompt, the conversation is marked as qualified. Qualified conversations can be filtered from the conversations page.
You can create **custom conversation variables** based on your needs. For example, you can create a variable named **'Pain points'** and write a prompt that extracts any pain points that users might mention in conversations 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/june-2026/june-23-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.