> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/learn/functional-capabilities/product-and-developers-guide/multi-channel-chatbot.md).

# Multi-Channel Chatbot

The **Multi-Channel Chatbot** capability is enabled by the following component of **Sunbird UCI**

1. **Chatbot UX tool -** Chatbot UX tool renders predefined and free-flowing conversations and emits usage data. This chatbot is embedded in the Learning apps. It is used to:
   1. Enable consumption of pre-defined and free-flowing conversations
   2. Embed to webapp (portal) of Sunbird ED
2. **Chatbot services** - Chat services is a micro-service that provides APIs to manage the lifecycle and workflows of creation and consumption of conversations on chatbots. These services are leveraged by the learning app to enable chatbot with -
   1. Add pre-defined and free-flowing conversations
   2. Enabled customized chatbot for different platforms such as learning apps, WhatsApp, etc.
3. **Chatbot admin tool** - Chatbot admin tool is used to create/add conversations, configure its behavior. This editor is leveraged by the learning apps for chatbot in:
   1. Creation of different types of predefined steps, actions, and workflows
   2. Creation of different types of free-flowing sets of questions with their respective answers

{% hint style="info" %}
Powered by [Sunbird UCI](https://uci.sunbird.org/)
{% endhint %}


---

# 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://ed.sunbird.org/learn/functional-capabilities/product-and-developers-guide/multi-channel-chatbot.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.