> For the complete documentation index, see [llms.txt](https://help.reekolect.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reekolect.ai/reekolect-resource-center/how-reekolect-works/bot-management/pre-built-chatbot-templates.md).

# Pre-Built Chatbot Templates

Why create new a chatflow from scratch? Use Pre-Built Templates to work even quicker, and make your chatbot faster!

Reekolect offeres multiple templates that allow for our users to quickly and effeciently start their chatbot joirney.

### How to use a template?

1. Go to your chatbot and click on its name.
2. Click on the second option of "Pre-Built Chatbot Templates".
3. Search for the desired template using the left hand search bar, or select from the showcased templates by scrolling through the options.
   1. Users also have the option to filter their search via the filters under the search box on the left side of the scene.
4. For using a template, hover over the image and click the the "**Use Template**" icon.
5. Click "**Use Now**" to send the template to your flows, and be redirected to the chatflow, where you can start your editing!


---

# 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.reekolect.ai/reekolect-resource-center/how-reekolect-works/bot-management/pre-built-chatbot-templates.md?ask=<question>&goal=<user_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.
