> 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/_eva-3.4.1_1/using-eva/develop-your-bot/dialog-cells/end-cells.md).

# End Cells

The End Cell acts as a period. When placing this cell, the virtual agent stops talking at that point. It will only take back the dialogue if the user *(the virtual agent’s interlocutor)* interacts.

![](https://2823722678-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNuMuHVlHgsqK4L1Tp4%2F-MXi8kxjofuKtlpdvAhj%2F-MXi9CQ2H8cuXbN8gUwL%2F61%20Screen%20-%20End%20cell.png?alt=media\&token=798391af-7635-4555-b612-ca4d43fdd4fd)

{% hint style="danger" %}
**The End Cell is always used in Jump Flows, never in the User Journey**
{% endhint %}

“Why?”, you can ask yourself. Simple: because User Flow is a kind of the main menu, the guiding thread that takes the user to a series of actions. And these actions are conducted through complementary flows, in other words, the Jump Flows.

A good use case example is applying the End Cell after a Service Error message (as long as it is in a Jump Flow). The End Cell will avoid the user from running an infinite loop in a dialogue.


---

# 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/_eva-3.4.1_1/using-eva/develop-your-bot/dialog-cells/end-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.
