> 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-chat/setting-up-repx/conversation-variables.md).

# Conversation variables

With conversation variables, you can extract the most important information from a conversation that matters to your sales team and your pipeline. 

* **Conversation variables** represent a piece of information you want RepX to pull out of every chat. 
* Each conversation variable is associated with a **prompt**. 
* When a conversation ends, RepX runs each of the prompts you've associated with variables against the full conversation and stores the results.
* There are **four default conversation variables**. You can create additional custom conversation variables from [**Settings > Variables**](https://app.storylane.io/repx-dashboard/settings/variables). 

\
Every variable - default or custom has

* **a name** - that indicates what its purpose is
* **data type** - can be text, true/false, number, date, email, phone
* **extraction prompt** - the prompt that tells RepX what needs to be extracted from the conversation and put into this variable

### Default conversation variables

| Variable name | Data type     |
| ------------- | ------------- |
| Visitor name  | String        |
| Email         | String        |
| Phone number  | String        |
| Qualified     | True or False |

In the table above, you'll find the list of default conversation variables. **Qualified** is the only default variable for which the prompt can be edited. You can edit its prompt from **Settings > Variables** to configure what a qualified conversation means to your business. \
\
For example, you can customize it to say 'Mark this conversation as qualified if the visitor mentiosn they have more than 500 employees and they want to see pricing, or if they talk about how long it would take for implementation.'

***

#### Examples of custom variables

You can create new variables from **Settings > Variables** in RepX. Some examples of custom variables you can create to extract information from conversations:

| Name                     | Can be used to capture                                                                                                             |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| Pain points              | The specific problems the visitor described with their current setup (when you set this up, add some examples of pain points here) |
| Primary product interest | Which of your products the visitor was really asking about                                                                         |
| Current tooling          | The competitor or incumbent tool the visitor said they're currently using or want to move from                                     |
| Timeline                 | When the visitor said they're looking to make a decision                                                                           |

***

#### Where variable show up

Once extracted, every variable is available in three places:

* **In the Zapier event `repx_conversation_completed` event and the webhook payload**, inside the `extracted_variables` block. Both default and custom variables are included.
* We're making an update to show the variables in the conversations page, soon.


---

# 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 dynamically 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-chat/setting-up-repx/conversation-variables.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 `build a script that syncs our docs to a CMS` 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.