When Selecting an Operator to Transfer the Call To BackgroundCallCard::transferButtonClick
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
placement— registration of the placement,telephony— registration of the call that raises the cardWho can subscribe: any user
The BackgroundCallCard::transferButtonClick event occurs when the operator clicks the transfer button in the call card and selects the employee to transfer the call to.
The transfer button is available only in the connected state, which the application enables with the CallCardSetUiState command. In call list mode and in the card of a call that was itself transferred, the button is not shown.
This is the first step of the transfer scenario. Bitrix24 does not transfer an application call itself. The application receives the recipient, connects them, and switches the card to the transferring state with the same command — in this state the operator sees the "Redirect" and "Continue call" buttons. Clicks on these buttons arrive as the completeTransferButtonClick and cancelTransferButtonClick events.
The event operates within the application context in the PAGE_BACKGROUND_WORKER placement. This is a JS interface event, not a REST event: you cannot subscribe to it with a request to /rest/.
What the Handler Receives
Data is passed to the callback BX24.placement.bindEvent
callback({
"phoneNumber": "+19001234567",
"target": 12
});
Event Handler Parameters
Required parameters are marked with *
|
Parameter |
Description |
|
phoneNumber |
The phone number of the other party |
|
Where the call is being transferred to. The value depends on the item the operator selected:
The transfer type — to an employee or to a phone — is not passed to the handler. The application determines it from the value: an employee ID matches the If the operator selected a department rather than an employee, the event does not occur |
Event Subscription Parameters
The handler is registered from the widget with the BX24.placement.bindEvent method.
Required parameters are marked with *
|
Name |
Description |
|
event* |
The name of the interface event. For this event — |
|
callback* |
The function Bitrix24 invokes when the event occurs. The handler arguments are described above |
Code Examples
How to Use Examples in Documentation
BX24.ready(function () {
BX24.init(function () {
BX24.placement.bindEvent('BackgroundCallCard::transferButtonClick', function (eventData) {
console.log(eventData);
});
});
});
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide)
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
await $b24.placement.bindEvent('BackgroundCallCard::transferButtonClick', (eventData: { phoneNumber: string; target: number | string }) => {
console.log(eventData.target)
})
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
document.addEventListener('DOMContentLoaded', async () => {
const $b24 = await B24Js.initializeB24Frame()
await $b24.placement.bindEvent('BackgroundCallCard::transferButtonClick', (eventData) => {
console.log(eventData)
})
})
</script>
Errors
Check the following conditions.
- The widget is open in the
PAGE_BACKGROUND_WORKERplacement. In other placements, theBackgroundCallCard::*events are not registered, and the subscription silently fails - The event name is passed without typos and with the correct capitalization. The list of events available in the current placement is returned by BX24.placement.getInterface
- The call was raised by the application with the telephony.externalCall.register method. For calls made by Bitrix24 itself, the
BackgroundCallCard::*events are not emitted at all
Continue Learning
- Overview of Events for Working with the Call Card of a WebRTC Client
- Set Up an Event Handler for the Interface BX24.placement.bindEvent
- Call Card
- Manage the Call Card of a WebRTC Client: Overview of Commands and Events
- When Clicking the "Redirect" Button BackgroundCallCard::completeTransferButtonClick
- When Clicking the "Continue Call" Button BackgroundCallCard::cancelTransferButtonClick
- Change the Call Card Interface State from the Application CallCardSetUiState