> 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/intercom/troubleshooting/loss-of-network-connection-for-intercom.md).

# Loss of Network Connection for Intercom

Learn what happens to Verkada Intercom’s functionality during an internet outage

When a [Verkada Intercom](https://docs.verkada.com/docs/video-intercom-overview.pdf) loses connectivity, here’s what you can expect:

* If the intercom is in single door controller mode, it continues to run the last known configuration. This means users whose credentials were configured before the lapse in connectivity can still badge in.
* Local streams established while the Intercom was still online continues as usual, as long as the page is not refreshed.
* Access and call events are stored locally onboard.
* When connectivity is restored, the intercom pulls the most recent configuration and uploads the cached access and call events to Verkada Command.

## Impact on calling

Verkada Intercoms require an internet connection to place calls **with one exception**: local Session Initiation Protocol (SIP). If the SIP server is reachable over the local network, then calling functions as usual, even during an internet outage.

{% hint style="danger" %}
**Important**. Any other receiver type ***cannot*** receive calls from, or place calls to an intercom without an internet connection.
{% endhint %}

## Impact on unlocking

If the intercom is operating as a single door controller, or if the unlock output is being used:

* Dual-Tone Multifrequency (DTMF) via local SIP can unlock.
* Badging with valid credentials can unlock.

If the intercom is paired to a door in Command that is wired to a Verkada access controller:

* The Intercom uses cloud unlock and **only the badge readers can unlock**.


---

# 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/intercom/troubleshooting/loss-of-network-connection-for-intercom.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.