> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-dashboard/exportar-datos/nomenclatura.md).

# Nomenclatura

A continuación te explicaremos ciertas nomenclaturas de los datos

## Abandonos en fila

En el caso de los abandonos, somos capaces de registrar los motivos por los cuales un cliente ha abandonado la fila.

{% hint style="info" %}
La tabla a continuación solo aplica para la fila de espera, no para otros flujos de la llamada.
{% endhint %}

| Nombre            | Descripción                                                                                         |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| server-disconnect | El servidor ha desconectado al usuario tras la orden de rechazo de la llamada por parte del agente. |
| user-disconnect   | El usuario se ha desconectado intencionalmente de la fila mediante la opción de abandono.           |
| ping-timeout      | La conexión del usuario presenta altas latencias y no ha respondido en más de 20 segundos.          |
| browser-close     | El usuario cerró la pestaña, navegador o aplicación.                                                |
| transport-error   | Ha habido un error durante la conexión, como caídas de red.                                         |


---

# 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.videsk.io/es-dashboard/exportar-datos/nomenclatura.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.
