> 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/add-and-configure-receivers-in-intercom/global-receivers-page.md). # Global Receivers Page Learn how to view, search, and manage intercom receivers from the Receivers page in Verkada Command The **Receivers** page lists every receiver for your Verkada Intercoms and shows how each one connects to call flows and intercoms. Use it to search receivers, review recent call activity, and set a user's receiving method in one place. {% hint style="danger" %} Your role determines who you can see on this page and what you can edit. See Roles and Permissions for Intercom for more information. {% endhint %} *** ## Access the Receivers page {% stepper %} {% step %} **In Verkada Command, go to All Products > Intercom.** {% endstep %} {% step %} **In the left navigation, select Receivers.** **Receivers** appears at the same level as **Home**, **Reports**, and **Global Events**. {% endstep %} {% endstepper %} *** ### Receivers table The Receivers table is the default view. It lists every receiver that belongs to at least one call flow, along with: * **Name:** The user's name or the device or number's display name * **Type:** User, Desk Station, Phone Number, or Session Initiation Protocol (SIP) * **Call Flows:** Every call flow the receiver currently belongs to * **Intercoms:** Every intercom that can call this receiver * **Answered calls:** The number of calls answered in the last 7 days {% hint style="warning" %} Things to note: * When in use, **911** always appears at the top of the table. * Command keeps a receiver on this page even after you remove it from every call flow. Command only removes a receiver from the page if you delete it. * Phone numbers and SIP extensions show a display name. If you haven't customized one, Command uses the number or extension, such as `(800) 555-1234 ext. 567`. {% endhint %} *** ### View and edit receiver details Click a receiver's name to open the details panel. Command displays different fields based on the receiver type: {% tabs %} {% tab title="User" %} * Name * Configured receiving method(s) {% hint style="warning" %} See [Configure a user's receiving method](#set-up-a-users-receiving-method) for more information {% endhint %} * Call flows and their associated intercoms * Answered calls in the last 7 days {% endtab %} {% tab title="Desk Station" %} * Name * Associated site * Online/offline status * Call flows and their associated intercoms * Answered calls in the last 7 days {% endtab %} {% tab title="Phone Number" %} * Display name * Phone number with extension * The key press configured to accept the call * Call flows and their associated intercoms * Answered calls in the last 7 days {% endtab %} {% tab title="SIP" %} * Display name * Extension number * Intercoms that can call this SIP extension * Answered calls in the last 7 days {% endtab %} {% endtabs %} {% hint style="info" %} From any receiver details panel, click a call flow to open it to make bulk changes. {% endhint %} *** ### Configure a user's receiving method Each user has one receiving method that Command uses across every call flow they belong to. You do not need to set a method separately each time you add a user to a call list. A user can be reached in up to two ways at once: * **Command Web:** On or off * **Mobile:** Choose one: * Verkada Pass * Command app * Phone number (with a key press to accept) * No mobile method #### Choose where to set the method * The first time you add a user to any call flow, you choose their receiving method. * After that, you can only change the receiving method from the **Receivers** page, not from within a call flow. If you hover over a user's receiving method in a call flow, you will see a tooltip that points you to the Receivers page. * When you update a receiving method on the Receivers page, Command applies the change everywhere that user appears. You don't need to update each call flow individually. *** ### Filter and search for receivers Use the controls at the top of the Receivers table to narrow a large list: * **Search by name -** Find a receiver by user name, display name, or phone number * **Filter by Intercom -** Show only receivers that a specific intercom can call * **Filter by Call Flow -** Show only receivers in a specific call flow * **Filter by Type -** Show only users, desk stations, phone numbers, or SIP *** ### View users when Directories are enabled If your organization uses [Directories](/command/users-and-permissions/manage-users-in-your-organization/directories-for-user-group-management.md), Command requires additional permissions to view and edit users on the Receivers page: * Without a Directory, a Site Admin can view every user configured as a receiver on any intercom in their site. * With a Directory enabled, a Site Admin also needs a Directory User Viewer, Directory User Admin, Org User Viewer, or Org User Admin role to view users as receivers in their site. {% hint style="info" %} If you don't have permission to view some receivers, Command displays a banner. The banner explains that additional users or desk stations can answer calls from your intercoms, even though you can't see their details. {% endhint %} * A Site Admin with User Viewer permissions can update a user's receiving method only if the change affects a single site. * If a user answers calls across multiple sites, only a Site Admin who administers all those sites, or an Org Admin, can make the change. Command shows a confirmation that the change affects multiple sites. * Within a call flow, any user or desk station you don't have permission to view appears as *Unknown user/Desk Station*. --- # 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/add-and-configure-receivers-in-intercom/global-receivers-page.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.