> 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/training.md).

# Training

RepX is not rule-based - you don't need to build workflows for every possible question like you would with traditional sales chatbots.\
\
Instead, you connect your content, and RepX leverages all of it to answer questions from visitors. It is through training you shape what your RepX agent knows about your products and how it represents them to every visitor. In other words, you can think of training as less like configuring software and more like onboarding a new sales rep. You can  RepX the same material you'd give a new hire: your website, your decks, your best call recordings, your demos and your answers to the questions buyers actually ask.\
\
As your content keeps getting updated and more of your team contributes, training is what keeps those answers accurate and consistent. Training is fully self-serve. There are two kinds of content you can add from the Training section in RepX:

* **Content RepX learns from:** your URLs, docs, and FAQs. This is the knowledge RepX draws on to answer questions.
* **Content RepX presents:** your demos and slides. This is the visual material RepX can surface inside the conversation.

### How RepX generates answers

Every time a visitor sends a message, RepX does a few things in parallel to put together the best possible response:<br>

1. **It finds the most relevant content to answer with.** RepX uses AI to pick the most relevant material from everything you've given it (your website, your documents, and your sales transcripts) to generate its answer based on your own information.
2. **It looks for something to show.** At the same time, RepX tries to identify the most relevant slide, demo or video it can surface for the question being asked, so the visitor can also see something visual and interact with it, along with the answer.
3. **It carries the conversation forward.** In many cases RepX also passes along the history of the conversation, so each reply takes the full context into account rather than treating every message in isolation.

### Knowledge sources

You can connect several types of sources. Each one plays a different role in how RepX answers and what it shows.

#### Website content

Point RepX at your website, help center, or any public page for it to present answers based on them. You can connect your entire website, or scope RepX to specific pages - useful when you want it to learn from your product and pricing pages but leave out sections like blogs that may not be relevant to buyers. RepX reads these pages and uses them as source material when generating answers.

When adding a URL, you can

* **Include just that URL**
* **Include that URL and links from that URL**

When you choose the latter, RepX presents all discovered links for you to review - you can exclude links you don’t prefer RepX to be trained on.\
\
If you update any of your webpages after you originally added them, you can click the three dot overview menu and have RepX resync content from that page anytime.

#### Docs

Docs are for internal documentation you want RepX trained on. You can upload PDFs and Markdown files.&#x20;

Use docs for the material that isn’t available on your website but has information that can help RepX provide better answers. Docs are never surfaced to visitors in conversations.

#### FAQs

When a visitor asks a question, RepX prioritizes finding the most relevant FAQ and delivering the answer associated with that FAQ. Use FAQs whenever you want a near-precise, pre-approved answer surfaced for a particular question, anywhere exact phrasing matters. Common examples:

* **Pricing:** where you want a specific, consistent answer every time.
* **Compliance-related questions:** where the wording needs to be exact.
* **Marketing-approved messaging:** where your team has a preferred way of saying something, even if it isn't phrased that way elsewhere on your site.

#### Sales transcripts

RepX can **generate FAQs from your sales transcripts** to present better answers in conversations. From the sales transcripts section, you can upload a .vtt or .doc file.\
\
When you upload a sales transcript, RepX processes the file and identifies FAQs (they’ll show up in the FAQs tab under the section ‘From transcripts’. FAQs derived from sales transcripts are treated the same way as how FAQs you add directly are treated - RepX prioritizes looking at the entire list of FAQs when generating answers.&#x20;

#### Interactive demos

From the Training section, you can also **add demos that show a broad product capability** you want buyers to explore deeply if they’re interested. Demos let RepX show your product to your visitors, in addition to describing it. \
\
Any published demo that you create within your Storylane account can be added to your RepX agent. For each demo you add, you can provide:<br>

* **A description** - what the demo shows and who it's for. RepX uses this to decide when the demo is relevant to a visitor's question or use case.
* **A display instruction** - plain-language guidance on when to present demo. A display instruction gives you control over when a demo shows up. Here’s an example display instruction that you could use if you’re including a demo about reports or analytics in your product: "Show this to visitors asking about native reporting or dashboards, but not to visitors who are asking about Tableau integration."

#### Videos

Similar to demos, you can **upload MP4 videos or link RepX to YouTube video library.** If you already have a library of overview and explainer videos built over time, you can have RepX present them in conversations.\
\
RepX will present the videos you upload or connect along with the answers it generates, wherever relevant. Similar to demos, for each slide, you can include a description (that tells RepX about the video you’re uploading) and a display instruction (that guides RepX when to present the video and when not to).

#### Slides

From Slides, you can **upload images that RepX can present in conversations**. While you’ll use demos to show an interactive experience of your product’s broad capabilities, you can use slides to provide images that compare your product with competition, share pricing plan overviews, or case studies and ROI material. RepX will present them along with the answers it generates.

Similar to demos, for each slide, you can include a description (that tells RepX about the slide you’re uploading) and a display instruction (that guides RepX when to present the slide and when not to)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storylane.io/repx/training.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.