> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/eses/versiones-anteriores/resumen-de-cambios-versiones-anteriores/novedades-de-la-version-2022.2/actualizaciones-del-ticket.md).

# Actualizaciones del Ticket

Cuando se ha lanzado un Ticket mediante la recepción de un correo electrónico entrante, se enviará un correo electrónico de reconocimiento automático que confirme la recepción del correo electrónico original y la creación de un Ticket como resultado de la recepción del correo electrónico. Además, el correo electrónico original se incluye como parte de la confirmación, y conserva el formato original. Esto ayuda a resolver un par de problemas de visualización de formato que las personas pueden haber visto en los correos de confirmación automática cuando se crea un nuevo Ticket. 

![](https://1038353727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdGgPaQ6xmH3DzmvAwDYk%2Fuploads%2FkNa06vP4kale13cmyuxv%2FUpdate-to-Ticket-222.gif?alt=media\&token=aa5c30b0-a2c5-4088-8404-51588d4a7bbf)


---

# 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.enate.net/whats-new/eses/versiones-anteriores/resumen-de-cambios-versiones-anteriores/novedades-de-la-version-2022.2/actualizaciones-del-ticket.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.