> 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-canada.md).
# Verkada Monitoring Phone Numbers - Canada
Find the correct Canadian dispatch phone number by province
{% hint style="success" %}
This article is a guide for 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 %}
In Canada, dispatch phone numbers can vary depending on the province, municipality, and in some cases, even by the exact street address of your site. For this reason, you must enter and verify the dispatch information for each site individually.
***
### Locate local dispatch number
Contact your partner to obtain the correct dispatch name (also known as a PSAP, or Public Safety Answering Point) and dispatch phone number. If you are unable to locate this information, contact [Verkada Support](https://www.verkada.com/contact/).
Once you have the correct dispatch number, enter it into Command during the setup of your Canadian [alarm site](/new-alarms/configuration/alarm-sites.md).
{% hint style="danger" %}
It is the organization’s responsibility to enter the correct emergency first responders’ routing numbers for Canadian sites and verify their accuracy for the specific Alarm site location. Failure to confirm local emergency dispatch numbers may lead to misrouted calls or delayed responses. Verkada is not responsible for verifying the accuracy or suitability of the routing numbers entered by the organization and disclaims any liability for damages resulting from incorrect configuration.
{% 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-canada.md?ask=&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.
