> For the complete documentation index, see [llms.txt](https://kizunai.gitbook.io/kizuna-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kizunai.gitbook.io/kizuna-docs/04.-how-kizuna-works.md).

# 04. How KIZUNA Works

## How KIZUNA Works

KIZUNA is designed around a simple four-step process:

**CREATE → CONNECT → DEPLOY → ANSWER**

Each step moves the project from its existing knowledge to direct community support.

### 01 — CREATE

#### Create Your KIZUNA Agent

The process starts by creating a KIZUNA agent for the project.

The project gives the agent its identity and context so it can be associated with the specific project it represents.

The goal is to create an AI community manager that is built around the project's own identity rather than a generic assistant.

### 02 — CONNECT

#### Connect Your Knowledge

The project connects its trusted knowledge sources to KIZUNA.

These can include:

* Project website
* GitBook
* Documentation
* FAQs
* Trusted project resources

This connected knowledge becomes the foundation for KIZUNA's project-specific responses.

The principle is simple:

**YOUR KNOWLEDGE → YOUR KIZUNA**

### 03 — DEPLOY

#### Bring KIZUNA to Your Community

Once the agent and its knowledge are connected, KIZUNA is brought into the project's Telegram community.

Telegram is the primary community environment for KIZUNA.

This allows community members to interact with the project-specific AI directly inside the conversation.

### 04 — ANSWER

#### Let Your Community Ask

Community members can ask questions directly in Telegram.

KIZUNA uses the connected project knowledge as the foundation for its responses and provides answers relevant to the project.

The experience becomes:

**QUESTION → KIZUNA → PROJECT KNOWLEDGE → ANSWER**

### The Complete Flow

The complete KIZUNA experience can be represented as:

**PROJECT**

↓

**CREATE KIZUNA**

↓

**CONNECT KNOWLEDGE**

↓

**DEPLOY TO TELEGRAM**

↓

**COMMUNITY ASKS**

↓

**KIZUNA ANSWERS**

The project provides the knowledge.

KIZUNA connects that knowledge to the community.

The community gets access to project-specific information directly inside Telegram.

### One Simple Layer

KIZUNA is designed to keep the experience simple for project teams.

There is no need to create a separate destination for every community question.

The project connects its knowledge once, brings KIZUNA into Telegram, and gives its community a direct way to interact with that knowledge.

**CREATE. CONNECT. DEPLOY. ANSWER.**

That's KIZUNA.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kizunai.gitbook.io/kizuna-docs/04.-how-kizuna-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.