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

# Call buttons

Assign phone numbers to the device's hardware buttons in Navixy so the device places a voice call to the right contact when a button is pressed.

Maps the device's physical hardware buttons to phone numbers. When a button is pressed, the device places a voice call to the assigned number. The number of configurable buttons depends on the device model, typically 1 to 4.

## Settings

* **Button #1, #2, …**: enter the phone number to call when that button is pressed. Use international format (for example, `+12025550100`). Leave a field empty to disable that button.

## Availability

Appears on device models that have configurable hardware call buttons.

## See also

* [SOS button action](/docs/user/guide/devices-and-settings/device-specific-controls/buttons-and-keys/sos-button-action.md): configure what a dedicated SOS press does.


---

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