> 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/acd/labels.md).

# Call Distribution with Labels

Configure the call distribution in the PASCOM telephone system with labels

## Trainingsvideo

{% embed url="<https://www.youtube.com/watch?v=x1XDszqEmoA>" %}

## Concept

Labels are so-called **"containers"** that contain information such as Customer number, VIP, blacklist etc., which the PASCOM telephone system can process. Labels are divided into ***static*** and ***dynamic*** labels and are used in various areas.

How do labels differ:

* **Static:** Only serve as a container for information such as Customer number, mandate number etc. which are then displayed in the software client for the users. We explain how to add labels to a phonebook entry in this \[Tutorial] (../../phonebook/phonebook-management/README.md#labels).
* **Dynamic:** Are linked to an [Action Condition](/en/setup/acd/conditions.md) whereby the PASCOM telephone system can react to labels. In addition, labels with conditions can not only be assigned to phonebook entries, but can also be set at any point in your call flow and checked accordingly..

### Create Labels with Conditions

{% hint style="info" %}
For better understanding, in this example we will greet a VIP customer in a queue differently than e.g. a normal costumer.
{% endhint %}

First you need a new label that you can create with a click on **ACD**> **Call Labels** and **Add**.

Choose a **generic label** and give the label the name **VIP**. If the label should be displayed to users in the app, check the corresponding box. In addition, the label must now be linked to an **action condition**. Finally click on **Save**.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-cf396ccfca8ee47ed8abdb43a113810141d250e6%2Fsetup_label.en.JPG?alt=media" alt="Create Label" width="60%"><figcaption></figcaption></figure>

* We explain how to assign the label to a customer in the phone book in this [Tutorial](/en/setup/phonebook/phonebook-management.md#labels).
* How to import labels automatically can be found in the tutorials for the [phonebook](/en/setup/phonebook.md).

### Configure the Action Condition

Action conditions can be configured in different ways. An action condition should react to a certain value. Here indefinite values ​​but also explicit values ​​can be queried. We'll explain exactly how this works in the following steps.

### React to indefinite values

In this type of value query, it doesn't matter what value the label has. Here it is only checked whether the label has any value or not. For our VIP customer we therefore use a VIP customer number which can have any character string.

![Label indefinite value](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-14b9b4e7c87cc7b8e1854aea1e860ac877230a7b%2Fphonebook_label_1.en.JPG?alt=media)

The associated action conditions can be found under **ACD**> **Action conditions** which you can now click on **Edit** and adjust.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-989f0877d224dc5cda0601a6c37c7dba39f3e3aa%2Fcondition_1.en.JPG?alt=media" alt="Adjust Action Condition" width="60%"><figcaption></figcaption></figure>

**Explanation of the parameters**

| Parameter        | Description                                                                                                              |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **MDC\_Label-8** | Variable that is behind the label and is queried.                                                                        |
| **!=**           | Is the operator that is used. In this case this means if our value in MDC\_Label-8 **does not equal** the queried value. |
| **" "**          | Placeholder for the queried value. In this case the placeholder is empty.                                                |

**Summary**

The action condition now returns **true / false** if the MDC\_Label-8 Variable **is not** empty. This allows an indefinite value in the VIP label, namely the VIP customer number. If a caller (phonebook entry) has assigned an empty VIP label, the query of the action condition results in **false**.

**Example**

In our example queue, 2 \[prompts] (../prompts-moh/README.md) were placed. If a VIP caller with an assigned VIP label that is not empty, comes into the queue, the VIP announcement is played for the caller. If the VIP label is empty or no label was found, the normal prompt is played.

![Example Callflow](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-bbdaaa68dd0b2136ad77a66ff258bc0e187408c4%2Fexample_label_callflow1_EN.jpg?alt=media)

{% hint style="info" %}
If considered when creating the label, the corresponding value is displayed to the users in the PASCOM app.
{% endhint %}

### React to explicit Values

In this type of value query, a label is queried for a specific value. Here it is checked the value of the call label exactly matches the value in the action condition. In the following example, the VIP label has the value **yes**.

![Label exact Value](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-20e332e960a471ad74d9bd7dc5b59cf0be0e0924%2Fphonebook_label_2.en.JPG?alt=media)

The associated action conditions can be found under **ACD**> **Action conditions** which you can now click on **Edit** and adjust.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-31f3f1df5b098567f151d9630c760200d4530a91%2Fcondition_2.en.JPG?alt=media" alt="Adjust Action Condition" width="60%"><figcaption></figcaption></figure>

**Explanation of the parameters**

| Parameter        | Description                                                                                                      |
| ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| **MDC\_Label-8** | Variable that is behind the label and is queried.                                                                |
| **==**           | Is the operator that is used. In this case this means if our value in MDC\_Label-8 **equals** the queried value. |
| **"yes"**        | Placeholder for the queried value. In this case the value is **yes**.                                            |

**Summary**

The action condition now returns **true / false** if the MDC\_Label-8 **equals** the value in the condition. This allows you to query an explicit value in the VIP label, namely whether VIP label is **yes**. If a caller (phonebook entry) has assigned a VIP label whose value does not match the action condition, the return value is **false**.

**Example**

In the example queue, 2 \[prompts] (../prompts-moh/README.md) were placed. If a VIP caller with an assigned VIP label, whose value corresponds exactly to the value of the action condition, comes into the queue, the VIP prompt is played for the caller. If the value of the VIP label does not match the value of the condition, the normal prompt is played.

![Example Callflow](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-528e260e745ff89f89361553a1f869de56e25bf3%2Fexample_label_callflow2_EN.jpg?alt=media)

{% hint style="success" %}
If considered when creating the label, the corresponding value is displayed to the users in the PASCOM app.
{% endhint %}

### Set and Check Labels dynamically

You have learned that labels attached to your customers phonebook entries can display and be queried. Call labels can be used even more versatile and can be placed dynamically at any place in your callflow. The link between a label and an action condition remains persistent across the entire PASCOM system. This means that labels can not only be queried, but also given to the caller at a certain point.

{% hint style="info" %}
For better understanding, in this example we will greet a prospect in a queue differently than e.g. a contract customer.
{% endhint %}

### Set Labels dynamically

Labels with an action condition can be set like normal \[actions] (../conditions/README.md). In the following example, the label was set in an IVR menu. Use **Add**> **Set label** to place the corresponding label.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-031d3c6c617cc97509a5d99a62edf02a05489c37%2Fset_label.en.JPG?alt=media" alt="Set Label" width="70%"><figcaption></figcaption></figure>

| Parameter      | Description                                      |
| -------------- | ------------------------------------------------ |
| **Typ**        | Set a Label                                      |
| **Name**       | Select the appropriate label from a dropdown box |
| **Expression** | Enter/set the value **yes**                      |

**Summary**

If your customers now enter the IVR menu and press the 1 key for prospective customers, the caller will be given the **prospective** label for the duration of the call. In the queue there are again 2 \[prompts] (../prompts-moh/README.md). If the caller comes into the queue with the **prospective label**, he hears a different announcement than e.g. Contract customers.

**Example**

![Example](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-d7780fe86c2133252473dd4b148f285d61df1952%2Fexample_label_ivr_EN.jpg?alt=media)

{% hint style="success" %}
The label that was set in your Callflow is only given to the caller for the duration of the call and disappears after hanging up. If you want to permanently assign information to your customers, store the label directly in the phonebook entries.
{% 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 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/acd/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.