> 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/classic-alarms/monitoring-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms.md).

# Verkada Monitoring Phone Numbers

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

{% hint style="success" %}
Verkada announced the global End of Sale (August 1, 2026) and End of Life (August 1, 2027) for Classic Alarms. Eligible customers can upgrade to New Alarms at no charge through January 31, 2027. Visit [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) to get started.
{% endhint %}

{% hint style="success" %}
This article is a guide for classic Alarms. Refer to this [article](/new-alarms/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms/verkada-monitoring-phone-numbers.md) if you have new 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:

{% stepper %}
{% step %}
**Our monitoring team will contact users who are specified in your org’s** [**contact list**](/classic-alarms/configuration/configure-classic-alarms-site-settings.md)**.**
{% endstep %}

{% step %}
**The team will verify the nature of the emergency and determine if emergency dispatch is needed.**
{% endstep %}
{% endstepper %}

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

These are the numbers that we use to notify you of an emergency:

### Voice

+16193044016

#### SMS

+16193298928

+16193298846

+16193298736


---

# 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/classic-alarms/monitoring-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms.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.