> 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/playbooks/qualification-behavior-and-goals.md). # Qualification behavior and goals The qualification behaviour section in a playbook lets you shape how RepX qualifies visitors on those pages and what it nudges them towards next. Within the qualification behavior section, you can control: * the **qualification questions RepX asks visitors** * **if RepX should ask for a visitor’s email** at all * if yes, **when in the conversation RepX should ask for email** * if RepX should nudge users towards **additional meeting or signup goals**

### Qualification questions Here, you can list the questions RepX needs to ask visitors to qualify them. For example, you might want to know the problem the visitor is trying to solve, their timeline for buying and if they currently use another product to solve the problems they're talking about. You can type in qualification questions that try to get the visitor to share this information. **In chats, when RepX answers a visitor's question, it makes sure to include these questions into the conversation as it goes.** You can add, edit, or remove questions for at the playbook-level: so you can have a different set of qualification questions for a playbook that runs on the `/pricing` page vs a playbook that runs on a page like `/solutions/industry` .

Configuring qualification questions RepX asks

### Email capture You can choose if RepX should ask visitors for their email. It's much lower friction for visitors to share their email than to book a meeting - so we highly recommend you have this enabled. * Yes, ask users for their email: RepX asks for the visitor’s email during the conversation. If you're okay to accept personal emails, uncheck 'Only work emails accepted'. * No, never ask for email: RepX never asks for an email on pages covered by this playbook. **When RepX asks for emails** If you’ve chosen to capture emails, you can decide where the ask lands relative to your qualifying questions: * **After a set number of messages:** * RepX starts asking for the visitor's email after they've sent a certain number of messages even if qualification questions aren't over. * If you set the number to 3, for instance, RepX asks for the user's email after they send their third message. * The agent continues alternating between the rest of the qualification questions and the email-ask until the user shares their email address. * **After the conversation meets qualification criteria:** * RepX waits until the visitor shares information that makes the conversation qualified and only after that, it asks for their email. * You define what “qualified” means by writing your qualification conditions in plain language. For example: *Consider the user as qualified if they mention that they mention they want to switch in the next six months.* * Once the user shares information that meets the qualification criteria, RepX starts asking for email and alternates between the email-ask and the rest of the qualification questions.

### Meeting or signup goals Once RepX has captured an email, you can have it push the visitor towards a meeting goal or a signup goal. You can set up two types of goals: * **Book a meeting:** Paste a meeting link from a scheduling tool like Chili Piper, RevenueHero or HubSpot Calendar. * **Sign up for a trial:** Paste your sign-up link. RepX points the visitor to it when self-serve is the better fit. When you add more than one goal, one of them is marked as the **default goal**. RepX offers the default goal whenever no other goal fits the conversation. You can make any goal the default by clicking **Set as default**. For every other goal, you tell RepX when to recommend it in the **Recommend this when** field. For example, you might keep a trial sign-up as your default and add a meeting goal that RepX recommends only when *the visitor mentions they're in the sales team*. If you don't have email capture enabled but just meeting or signup goals, RepX will start alternating between recommending a goal and qualification questions when the user meets the qualification criteria you've set.

--- # 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/playbooks/qualification-behavior-and-goals.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.