> 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/intro-to-repx.md). # Intro to RepX šŸ‘‹šŸ¼ New to RepX? This is where you can get started. ### What is RepX? RepX is your always-on, conversational AI SDR. RepX has conversations with your website visitors like a human would, shows them relevant demos, videos and resources, and helps qualify them by asking the right discovery questions. RepX can also ask and capture emails from your website visitors,Ā nudge them towards booking meetingsĀ or towards sign-ups. RepX is trained on your world: your website, your docs, your demos, and your messaging to deliver nuanced, helpful conversations. RepX doesn't just chat - it can play interactive demos, slides, videos, and more directly with chat windows. And it moves at the pace of the buyer, so visitors get answers immediately instead of waiting days for a call. {% embed url="" %} This guide walks through everything you can configure and how RepX works under the hood. ### Why RepX? Most B2B software websites are passive, overwhelming experiences. Buyers land on your site, struggle to find what they're looking for, and leave - 97% of them, in fact. Meanwhile, your sales team spends hours on repetitive discovery calls, answering basic questions and walking through the same product overviews. RepX solves both problems. Buyers get immediate answers and personalized product demos on their terms. Your sales team gets conversation insights, qualified leads with their emails and booked meetings from engaged propsects. {% @storylane/embed subdomain="app" linkValue="79xhb1dxofcg" url="" %} ### Key capabilities * **Multi-modal AI agent** that supports voice and video avatars, and text mode * **Instant demos** to present your product capabilities based on the buyer's use case and intent * **End user experience** that can also present videos, PDFs, your sales meeting scheduling URL and other resources inline * **Trained on key resources** including your website, help center, sales transcripts * **Transcripts** **and summaries** of buyer questions and engagement * **Qualification playbooks** to qualify the right leads through conversations * Support for **nudges** that encourage website visitors to start chats * **Alerts** sent to Slack when leads land on your website * **HubSpot, Salesforce, Marketo and Pardot integrations:** Sync lead conversations, along with data extracted from conversations into your CRM (e.g. pain points, interests, etc.) * **24/7 availability** so buyers get answers whenever they need them ### What to expect When you deploy RepX, you should see: * **More qualified leads** from your website traffic. Buyers self-select based on real discovery, not just form fills. * **More emails captured and booked meetings** from your existing traffic - RepX nudges visitors within chats to book meetings with your team. * **Faster sales cycles**. Prospects arrive to calls already educated and engaged, so your team can skip basic discovery and focus on closing. * **Better buyer experience**. They get answers when they want them, move at their own pace, and aren't stuck waiting for a response. * **Scale without headcount**. Grow your qualified leadĀ count without hiring proportional SDR teams- RepX handles qualification at scale. * **Instant demos** - Suggests engaging, interactive demo based on each buyer's use case, context, and intent * **Objection handling** - Trained on sales transcripts from your top performers to handle common objections with expertise --- # 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-chat/intro-to-repx.md?ask=&goal= ``` `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.