> 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/configuration/set-a-receiver-as-here-or-away.md).

# Set a Receiver as Here or Away

Have a user be automatically skipped by an intercom call flow when they are away

Every user receiver has a status: **Here** or **Away**. When a user is Away, Call Flows automatically skip them and move to the next receiver.

* Away status requires a duration and cannot be indefinite.
* Status changes sync across all platforms immediately.
* Status appears wherever the User is listed as a receiver, so admins and teammates can see whether calls will reach them.

***

### Set your status to Away

Set your status from Command Web, Command Web on mobile, the Command mobile app, or the Verkada Pass app.

{% hint style="danger" %}
A Site Admin can override the status of any user they have permission to view, if that user is included in a call flow associated with the Site Admin.
{% endhint %}

{% tabs %}
{% tab title="Command web" %}
{% stepper %}
{% step %}
Open Command web on desktop or mobile.
{% endstep %}

{% step %}
In the bottom left corner, click your **organization logo** to open the account menu.
{% endstep %}

{% step %}
At the top, click the **Set yourself as away** dropdown.

<div align="left" data-with-frame="true"><figure><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2F2PqlRZea6GzFCItC2A7u%2FAway_web.png?alt=media&amp;token=43364e79-fae0-4bec-ad12-3ea9d433dfd3" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Choose how long you'll be **Away**.

{% hint style="warning" %}
You can't set **Away** indefinitely. Choose a specific duration. When the time ends, Command sets you back to **Here**.
{% endhint %}
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Command mobile app" %}
{% stepper %}
{% step %}
Open the Command mobile app.
{% endstep %}

{% step %}
In the top left, tap <img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2F1btwKWTboxY8Q2XHkOHo%2FScreenshot%202026-09-02%20at%2010.11.58%E2%80%AFAM.png?alt=media&amp;token=ebbe6980-3e65-4499-be7c-3b97a1a815ce" alt="" data-size="line">.
{% endstep %}

{% step %}
At the bottom, select your organization's name.

1. Tap the **Set yourself as away** dropdown.&#x20;
2. Toggle your status to **Away**.
3. Set how long you'll be **Away.**

{% hint style="warning" %}
You can't set **Away** indefinitely. Choose a specific duration. When the time ends, Command sets you back to **Here**.
{% endhint %}

<div align="left" data-with-frame="true"><figure><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fy6dNge4IC2enWwuHeXDA%2FAway_Commad_app.png?alt=media&amp;token=20469fc7-3b8b-42a4-a4e6-ccc49d9e7f29" alt="" width="295"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Verkada Pass app" %}
{% stepper %}
{% step %}
Open the Verkada Pass app.
{% endstep %}

{% step %}
Tap the **Intercoms** tab on the bottom navigation bar.&#x20;
{% endstep %}

{% step %}
In the top right, tap **Set away.**
{% endstep %}

{% step %}
Set how long you'll be **Away**.

{% hint style="warning" %}
You can't set **Away** indefinitely. Choose a specific duration. When the time ends, Command sets you back to **Here**.
{% endhint %}

<div align="left" data-with-frame="true"><figure><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2F7TdehOkhB2nXNFVamEvK%2FScreenshot%202026-10-05%20at%2010.52.13%E2%80%AFAM.png?alt=media&amp;token=f7c1f573-50bb-445b-85ae-ebdb6c886ba6" alt="" width="361"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

***

### Set Desk Stations as Here or Away

A Desk Station shows a **Here** or **Away** status on the **Receivers** page that matches the toggle on the Desk Station.

* Site Admins can view the status on the **Receivers** page.&#x20;
* You can only update the status from the Desk Station.

***

### View Here or Away status

Your status appears wherever you are listed as a receiver:

* **Receivers table**—Users and Desk Stations set to **Away** show a moon icon.
* **Receiver details panel**—User and Desk Station status appears at the top of the panel.

A Site Admin can override a user's status from the receiver details panel. The Site Admin must have permission to view that user, and the user must be in a call flow associated with the Site Admin.

***

### Avoid an empty call flow

If you set a user to **Away** and no other receiver in an associated call flow is currently **Here**, Command shows this warning before the change goes through:

> *There are no other active receivers in the \[Call Flow Name] for \[Intercom Name] intercom. Please confirm that you understand that any call made from this intercom could be missed if you proceed.*

{% hint style="danger" %}
Users and Site Admin can still set the user to **Away**. Command does not block the change.
{% endhint %}

***

### See Away status in call history

If a user was in a call flow but wasn't called because they were **Away**, the Events timeline shows that the user was skipped because of their status.


---

# 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/configuration/set-a-receiver-as-here-or-away.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.