> 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/driving-more-chats.md). # Driving more chats See how you can leverage playbooks to drive more chats and convert more visitors * Starter questions * Nudges #### Starter questions Starter questions are questions RepX displays, to encourage users to start having conversations. A relevant question or nudge is far more likely to earn a click than something that's more generic, which is what makes starter questions a direct lever for lifting the number of visitors who start chatting with your RepX agent. Because starter questions live inside playbooks, they can be specific to your webpages. On a playbook associated with the pricing page, you can set some starter questions about pricing. On a page that talks about a specific feature, you can have RepX show starter questions specific to that feature. This is how starter questions look like when you use different launcher styles.

Starter questions when you use the launcher style Buttonish

Starter questions when you use the launcher style Type-first

### Nudges Nudges are coming soon. Nudges are AI generated based on the page the visitor is on, and they encourage users to start chats as well. --- # 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/driving-more-chats.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.