> 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/training-repx/webpages-docs-and-sales-transcripts.md).
# Webpages, docs and sales transcripts
Learn how you can include different types of content that RepX can generate answers from
### Website content
Point RepX to 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
From here, you can upload any internal documents that you've got around any topic you want RepX to learn from. You can upload PDFs, Markdown, DOCX and other file types.
**Use docs for content that is not 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 FAQs** 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 also **generate FAQs from your sales transcripts** to present better answers in conversations. From the sales transcripts section, you can upload a .vtt, .doc, .txt or .pdf files of your sales transcripts.\
\
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 FAQs when generating answers.
---
# 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-chat/training-repx/webpages-docs-and-sales-transcripts.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.
