> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/build-dialogs/dialog-cells.md).

# Dialog Cells

Create reusable conversational resources and use them across different flows.

**Dialog Cells** are based on resources that are **created and stored in their respective repositories**. Once created, these resources can be selected and reused when building different flows in the Workspace.

This makes Dialog Cells especially useful for conversational elements that should remain consistent or be reused across multiple parts of the conversational project.

Each Dialog Cell serves a specific purpose:

* **Intent:** Identifies what the user wants to accomplish.
* **Entity:** Identifies specific information within the user's intent, helping refine the conversation.
* **Answer:** Defines the responses delivered by the conversational project.
* **Service:** Connects the flow to external services through Webhooks, REST Connectors, or APIs.
* **Prompt:** Uses Generative AI to generate content dynamically during the conversation.

Because these resources are managed centrally in repositories, **changes can be reflected wherever they are used**, making Dialog Cells especially useful for content and configurations shared across multiple flows.


---

# 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://docs-conversational-ai.syntphony.com/build-dialogs/dialog-cells.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.
