- Joined
- Feb 18, 2024
- Messages
- 45
- Reaction score
- 46
As a 3CX partner, we regularly migrate customers from competing PBX platforms to 3CX. One recurring issue we encounter is the loss of DND visibility on BLF keys for desk phones such as Yealink handsets.
Many competing systems publish DND status to BLF subscriptions, allowing receptionists and other staff to immediately see when a user is unavailable. On these systems, a monitored extension in DND will typically display a different BLF state, often a red LED indication. After migrating to 3CX, these same users see the BLF remain available despite the extension being in DND.
This creates confusion for customers because from an operational perspective, a user in DND is not available to receive transferred calls. Receptionists and operators rely heavily on BLF keys to determine who is available before transferring a caller. The current behaviour can result in calls being transferred to users who have intentionally made themselves unavailable.
We understand that 3CX places significant emphasis on the desktop, web and mobile applications where presence information is clearly displayed. However, many of our customers still rely primarily on physical desk phones and expansion modules throughout the day.
Examples include:
"Display DND as Busy on BLF keys"
or
"Publish DND presence state to supported BLF subscribers"
This would allow partners and administrators to enable the behaviour where appropriate without affecting existing deployments.
From our experience, this is one of the few areas where customers migrating from other PBX platforms perceive a loss of functionality after moving to 3CX. Providing an optional setting would improve the migration experience and better align desk phone behaviour with customer expectations and established operator workflows.
Many competing systems publish DND status to BLF subscriptions, allowing receptionists and other staff to immediately see when a user is unavailable. On these systems, a monitored extension in DND will typically display a different BLF state, often a red LED indication. After migrating to 3CX, these same users see the BLF remain available despite the extension being in DND.
This creates confusion for customers because from an operational perspective, a user in DND is not available to receive transferred calls. Receptionists and operators rely heavily on BLF keys to determine who is available before transferring a caller. The current behaviour can result in calls being transferred to users who have intentionally made themselves unavailable.
We understand that 3CX places significant emphasis on the desktop, web and mobile applications where presence information is clearly displayed. However, many of our customers still rely primarily on physical desk phones and expansion modules throughout the day.
Examples include:
- Receptionists handling high call volumes where BLF visibility is critical.
- Manufacturing, warehouse and workshop environments where staff do not have access to the desktop application.
- Shared workstations and hot-desk environments where users are not permanently logged into the web client.
- Users who spend most of their day on a desk phone and have little reason to keep the desktop application open.
- Organisations that intentionally minimise desktop notifications and softphone usage to reduce distractions.
"Display DND as Busy on BLF keys"
or
"Publish DND presence state to supported BLF subscribers"
This would allow partners and administrators to enable the behaviour where appropriate without affecting existing deployments.
From our experience, this is one of the few areas where customers migrating from other PBX platforms perceive a loss of functionality after moving to 3CX. Providing an optional setting would improve the migration experience and better align desk phone behaviour with customer expectations and established operator workflows.
Upvote
7
