> 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/introduction-to-playbooks.md). # Introduction to Playbooks Learn how you can customize how RepX qualifies leads within different webpages. Someone comparing plans on your pricing page probably arrives with a very different intent and has very different questions compared to someone who just landed from an ad on another page. With Playbooks, you can control * **starter questions that are shown in the launcher** to visitors on certain webpages * how RepX greets visitors through the **intro message** on those pages * the **CTA buttons** that show up within RepX against certain pages * the **qualification behaviour** of RepX on those pages For example, you can have a playbook associated with the `/pricing` page and another playbook associated with all `/solutions` pages on your website and configure very different engagement settings for each set of pages. Since a single, generic conversation flow may not serve visitors on different pages well, the **qualification behaviour section** within playbooks allows you * to define the **qualification questions** RepX asks, * if it should **capture emails**, and * if it should push visitors to either **meetings or signup links** ### Default playbook Every account comes with a default playbook. When RepX loads on a page, we check if the URL of the page matches any of the playbooks you've setup. If the URL doesn't match the URLs in any of your playbooks, RepX follows what's been defined in the default playbook. RepX loads the starter questions defined in the default playbook when the launcher appears. Then, if the visitor opens RepX, it greets them based on the intro message defined in the default playbook and loads the CTA buttons configured in the chat. \ \ As the conversation goes forward, it follows the qualification behaviour defined in the default playbook to ask the right questions and nudge visitors towards the right meeting or signup links.

### Creating new playbooks You can create additional playbooks to define RepX's behaviour on specific pages on your website. From the Playbooks page, you can click **Add playbook** to define the name of the playbook first. Then, you can choose the URLs where this playbook should be effective. You can have a playbook that runs only on the page `yourwebsite.com/pricing`. You would do this by associating the playbook with "exact match" of the URL `yourwebsite.com/pricing` when you setup the playbook. You can also associate a playbook with URLs based on "starts with" or "contains" - in such a situation, the playbook runs seamlessly when you add new webpages that have the same pattern as the URL you define in the playbook.

This is useful when a group of pages shares the same intent - say, all your case study or integration pages. You can configure engagement settings once for all those pages together, in one playbook. --- # 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/introduction-to-playbooks.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.