> 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/10.-product-experience.md). # 10. Product Experience ## Product Experience ### Built for Simplicity KIZUNA is designed to keep the experience simple for project teams. The project provides its identity and knowledge, connects the agent to Telegram, and gives the community a direct way to interact with project information. The intended experience follows a clear path: **CREATE → CONNECT → DEPLOY → SUPPORT** ### For the Project The project owner starts by creating a KIZUNA agent. The agent is given the project's identity and context, followed by the connection of trusted project knowledge. The project then brings KIZUNA into its Telegram community. The journey is: **PROJECT OWNER** ↓ **CREATE KIZUNA AGENT** ↓ **CONNECT PROJECT KNOWLEDGE** ↓ **CONNECT TELEGRAM COMMUNITY** ↓ **KIZUNA SUPPORTS THE COMMUNITY** ### For the Community The community experience is equally simple. A member has a question about the project. Instead of leaving Telegram and searching through different resources, the member can interact with KIZUNA directly inside the community. The experience becomes: **QUESTION** ↓ **KIZUNA** ↓ **PROJECT KNOWLEDGE** ↓ **ANSWER** ### One Conversation Layer KIZUNA brings project information into the same environment where the community already communicates. This removes the need to treat every question as a separate search task. The community can interact with the project's knowledge through conversation. ### Supporting the Team KIZUNA is designed to support the project team, not replace it. By making existing project information easier to access, KIZUNA can serve as an additional community-support layer. This allows the team to spend more time on the project itself while KIZUNA handles project-information interactions within the community. ### The Complete Experience The KIZUNA experience can be summarized in one flow: **YOUR PROJECT** ↓ **YOUR KNOWLEDGE** ↓ **YOUR KIZUNA** ↓ **YOUR TELEGRAM COMMUNITY** The project provides the information. KIZUNA turns it into an accessible AI experience. The community gets a direct way to ask and learn. **One intelligent layer for your community.** --- # 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/10.-product-experience.md?ask=&goal= ``` `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.