> 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/reference/howto/non-successful-blind-transfers.md).

# Send unsuccessful blind transfers back to a team

In this HowTo you will learn a workaround on how to return unsuccessful blind transfers back to a team.

## Overview

Blind transfers, also called connecting without consultation, are very common. A caller is connected to a colleague without knowing in advance whether the colleague can accept the call. If the colleague is not at the desk or is on the phone, the transferred call ends up in the voicemail box or, in the worst case, is lost.

In this workaround, we configure members of a team (e.g., Sales) so that a blind transfer from Employee A to Employee B is not lost if Employee B cannot answer the call. Instead, the connected call goes back to the original team (e.g. Sales) and the caller can be dealt with again.

**What is needed?**

1. a team (e.g. Sales)
2. users/members in the team
3. call labels
4. action conditions

## The workaround explained in detail

1. 1 - When a **caller** enters Team Central, a **caller label** is attached to the caller, which remains with the caller for the duration of the call.
2. 2 - **Member A** answers the call and connects the caller without consultation to **Member B**, who does not answer the call. The call label on the caller can be used to check whether the caller is from **Team Sales** using an **Action Condition**.
3. 3 - The caller is then sent back to the appropriate team.

![Workarround Übersicht](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-572842aadeb154f9faf1e3d46b6e35ff92f6bfe5%2FBlind_Transfer_Return_DE.png?alt=media)

## Set up call label

In the Admin UI click **Call Distribution** and then **Call Labels**. Click **Add** to create a new label. Configure the call label as shown below. You can define the label yourself.

![Anruf Label erstellen](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-ee6eb1ca8458229a8ba2dbb339dca8352a2f53b6%2Fcreate_call_label_de.png?alt=media)

Make sure that you create an action condition at the same time. The action condition then has the same name as the call label.

## Set call label in team

The next step is to attach the previously created call label to a caller when they enter the team center and at the same time set the value **"1"** in the channel variable of the call label.

![Anruf Label im Team setzen](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-0123811b48ab0f2d4fe95b1adbe82d03b107ea18%2Fset_call_label_in_team_de.png?alt=media)

Navigate to the **External/Previous** - Action tab and click **Add** and then **Set Label**. Select your call label at **Name** and enter **"1"** at **Expression**. The caller is now given the call label with the entered value for the duration of the call when he joins the team.

## User Configuration

In order to be able to send calls that are not answered back to the **Sales** team, we have to link our action condition with a drop for the users.

![Aktionsbedinung bei Benutzern konfigurieren](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-609217b3622a4302e95932401456fa748712cc0e%2Fuser_configuration_de.png?alt=media)

Navigate to the **External/After** action tab and click **Add Drop** and then **Queue**. For **Condition**, select the action condition with the **positive status**. Decide at which [call status](/en/setup/acd/actions.md) the drop should occur. Finally, select the team to drop on under **name**. In our example: **Sales**.

The missed call, is dropped into the queue only if the condition is true.

## Display for which user the blind transfer failed

As soon as the caller gets back to the team from the failed connection attempt, other employees can take care of the call. If you now want to know which colleague's blind transfer failed, you can attach the user's name to the caller in an additional label.

1. Create a new call label as shown below.

![Neues Label anlegen](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-558b3635bc337916b08e8ffac119d8103b039f4f%2Flabel_missed_transfer_call_de.png?alt=media)

2. Set a new action of type **Set label** on the user before dropping to the team and configure it as follows.

**Expression**

```
${MDC_CALLEE_ACC_REALNAME}
```

![Displayname des Benutzer mitgeben](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-f9c0f1bd666cf6297c47c42c7f1b47e268f550be%2Fconfigure_user_displayname_de.png?alt=media)

The returned caller is now waiting in the team's queue again and at the same time has pinned the label of the user for whom the connection attempt failed.

![Anrufer mit Label](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-ca4d4caefedc4b88a4892633c677038feb1203f4%2Freturned_call_with_label_de.png?alt=media)

## Roll out actions via templates

You can easily roll out the actions created on your users to all your users using an action template. You can find more information [here](/en/setup/acd/actions.md#actiontemplates).


---

# 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/reference/howto/non-successful-blind-transfers.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.