> 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/pt-br/guide/devices-and-settings/device-specific-controls/buttons-and-keys/call-buttons.md).

# Botões de chamada

Atribua números de telefone aos botões de hardware do dispositivo no Navixy para que o dispositivo faça uma chamada de voz para o contato correto quando um botão for pressionado.

Mapeia os botões físicos de hardware do dispositivo para números de telefone. Quando um botão é pressionado, o dispositivo realiza uma chamada de voz para o número atribuído. A quantidade de botões configuráveis depende do modelo do dispositivo, normalmente de 1 a 4.

## Configurações

* **Botão #1, #2, …**: digite o número de telefone para ligar quando esse botão for pressionado. Use o formato internacional (por exemplo, `+12025550100`). Deixe um campo em branco para desativar esse botão.

## Disponibilidade

Aparece em modelos de dispositivo que têm botões físicos de chamada configuráveis.

## Veja também

* [Ação do botão SOS](/docs/user/pt-br/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.md): configure o que um pressionamento dedicado de SOS faz.


---

# 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/pt-br/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.