> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/introducing-lucy.md). # Introducing Lucy August 28, 2023 - Rechat’s AI-powered Personal Assistant, Lucy, is now built directly into your Forms. {% embed url="" %} Have you ever had a question about a form but didn't have the time or resources to read the document or learn the answer? Lucy, Rechat's AI-powered Personal Assistant, now makes it easier than ever to get answers to your most pressing questions about your Forms in Rechat. When you open a Form, Lucy will introduce herself with some suggestions of questions you might have. Click on a suggestion, and Lucy will provide an answer. You can also type in your own questions using the chat field and press the enter or return key, or click send. --- # 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://help.rechat.com/whats-new/introducing-lucy.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.