> 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/edit-your-chat-flow/components-in-chatflow/request-information.md).

# Request Information

Here is a structured guide on Chat Components under "Request Information":

Here’s a structured breakdown of the available **chat components** and their use cases:

#### **Basic Input Components**

1. **Name**
   * Requests the user's name.
   * Customize the request message in the **Customize Bot Message** section.
2. **Phone Number**
   * Requests the user’s phone number.
   * Allows selecting a **specific country code** from a dropdown.
3. **Email**
   * Requests the user's email address.
   * The message can be customized in the **Customize** panel.

#### **Choice-Based Components**

4. **Single Choice**
   * Allows users to select **one** option from a list (up to 5 options).
   * Each option can be linked to the next component.
5. **Multiple Choice**
   * Enables users to select **multiple** options (up to 5).
   * Each option can be connected to a subsequent action.

#### **User Input & File Upload**

6. **Text Question**
   * Requests an **open-ended response** from the user.
7. **File Upload**
   * Allows users to upload a **file, image, or video**.
   * Customize the request message in the left panel.

#### **Advanced Interactive Components**

8. **iFrame**
   * Embeds an **external webpage** into the chat.
   * Requires a **URL, title, and CTA button**.
9. **Appointment**
   * Lets users book an appointment.
   * Set **availability hours, time slot intervals, and future booking days**.
   * Integrate with a third-party scheduling tool.
10. **Location**

* Requests a **text-based location** from the user.

11. **Date/Time Picker**

* Collects **date and time** inputs.
* Offers a calendar-based selection for users.

#### **Feedback & Numeric Inputs**

12. **Rating**

* Collects user ratings and feedback.
* Supports **5 rating options**.

13. **Range Selector**

* Allows users to input a value within a **specified range**.
* Supports custom **prefix, suffix, and step values**.

14. **Numeric Input**

* Accepts **only numerical values** as input.

#### **Dynamic & Logic-Based Components**

15. **Smart Question**

* Directs the conversation based on user responses.
* Supports **keyword-based routing** (exact match or keyword presence).

16. **Redirect**

* Connects to another **pre-built chat flow**.
* The conversation seamlessly continues in the selected flow.

#### **API & Integrations**

17. **API Component**

* Integrates a **third-party service** into the chat flow.
* Handles **response codes** (200 = success, 400 = error).
* More details available in the **Developers** section.

Each of these components plays a crucial role in enhancing chatbot flexibility, enabling **seamless conversations, user interactions, and third-party integrations**. 🚀


---

# 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/edit-your-chat-flow/components-in-chatflow/request-information.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.
