> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/new-alarms/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms/verkada-monitoring-phone-numbers.md).

# Verkada Monitoring Phone Numbers

Save the phone number Verkada’s monitoring team will use to contact you

{% hint style="success" %}
This article is a guide for New Alarms. Refer to this [article](/classic-alarms/monitoring-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms.md) if you have classic Alarms. See [New Alarms vs Classic Alarms](/new-alarms/getting-started/new-alarms-vs-classic-alarms.md) if you are unsure which version of Alarms you have.
{% endhint %}

When a Verkada alarm is triggered, our monitoring team will notify the contacts listed for your alarm site. The number that will text and call you when an alarm is triggered depends on your region:

**US / Canada:** +1 (877) 845-7851

**AU / NZ:** +61 468 079 011

{% hint style="info" %}
Users on the notifications list should save this number to their contact list as **"Verkada Monitoring"**. For organizations using both classic Alarms and new Alarms, save this number as ’New Alarms - Verkada Monitoring."
{% endhint %}

We highly recommend enabling [**Emergency Bypass**](/new-alarms/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms.md) for this contact. This allows the number to ring even when your phone is in a Focus mode, such as Do Not Disturb (DND).

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=ff_TxRmg__c).
{% endhint %}


---

# 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://help.verkada.com/new-alarms/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms/verkada-monitoring-phone-numbers.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.