> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.md).

# Botones de llamada

Asigne números de teléfono a los botones físicos del dispositivo en Navixy para que el dispositivo realice una llamada de voz al contacto correcto cuando se presione un botón.

Asigna los botones físicos de hardware del dispositivo a números telefónicos. Cuando se presiona un botón, el dispositivo realiza una llamada de voz al número asignado. La cantidad de botones configurables depende del modelo del dispositivo, normalmente de 1 a 4.

## Configuración

* **Botón #1, #2, …**: ingrese el número de teléfono al que llamar cuando se presione ese botón. Use el formato internacional (por ejemplo, `+12025550100`). Deje un campo vacío para desactivar ese botón.

## Disponibilidad

Aparece en modelos de dispositivos que tienen botones físicos de llamada configurables.

## Ver también

* [Acción del botón SOS](/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.md): configure qué hace una pulsación dedicada de SOS.


---

# 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://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.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.