> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/setup/pascom-trunk/incoming-call-labels.md).

# Labels for Incoming Calls

Use labels for incoming calls to signal caller origin and for advanced routing.

Incoming call labels provide a powerful tool for managing and visualizing your incoming calls. This feature not only enables **automated routing** within your phone system but primarily serves as a **visual signal** for your employees. Whether for location identification or department assignment: see at a glance which area a caller is contacting – before you even answer the call. Optimize your communication and ensure maximum transparency across your teams.

## Create Generic Label

To add information to a call, you first need a **Label**. This acts as a container for the information you want to display or analyze. First, create a new generic label in the Admin UI.

For detailed instructions on how to create and configure labels, see our [guide](/en/setup/acd/labels.md).

**Summary:**

1. Navigate to **Call Distribution** > **Call Labels**.
2. Click **Add** and select a **Generic Label**.
3. Enter a meaningful **Name**, e.g., `Location` or `Sales`.
4. Check the **Show in app** option so the label is visible to your employees.
5. Click **Save**.

## Assign Label in Trunk

After creating the label, link it to your trunk. The PASCOM cloud phone system will then automatically use this label for all incoming calls via this trunk.

![Assign label in trunk basic settings](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-673f8ada2184b08146b1ffc3032c8548820b4d71%2Fassign-incoming-call-label.en.png?alt=media)

1. Navigate to **Gateways** > **Trunks**.
2. Select the desired trunk from the list and click **Edit**.
3. Switch to the **Basic Settings** tab.
4. Find the setting **Label for incoming calls**.
5. Select the previously created label from the drop-down menu.
6. Confirm the setting by clicking **Save**.

![Call Rule name is applied to the label](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-70944215088b5509a70d5471ce12347045e6dbf7%2Fdescription-of-the-call-rule-in-label.en.png?alt=media)

## Functionality and Analysis

The configuration is now complete. The system will now automatically populate the label with the name of the Call Rule assigned to the trunk for every incoming call.

**The Process in Detail:** When a caller dials one of your physical phone numbers that is assigned to a **Call Rule** in your trunk, the system writes the **Name of this Call Rule** into the configured label.

**Your Benefits:**

* **Signaling at the PASCOM App:** Your employee immediately sees the label and its content (the Call Rule) in the PASCOM App. Example: A caller dials the number for the Munich location. The call rule is named "Munich HQ". The PASCOM app displays: `Location: Munich HQ`.
* **Automated Routing:** Use the label content to intelligently distribute calls in call distributors.
* **Grafana Analytics:** Analyze in Grafana which call rules (and thus which marketing numbers or locations) are called most frequently.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/setup/pascom-trunk/incoming-call-labels.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 `build a script that syncs our docs to a CMS` 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.