- Joined
- Jan 30, 2014
- Messages
- 12
- Reaction score
- 3
While testing the Boss-Secretary feature, I observed what appears to be incorrect missed-call behavior.
However, the missed call did not appear on the Boss's Yealink desk phone.
From the Boss's perspective, the call was never presented directly to their extension. The purpose of the Boss-Secretary feature is to have the Secretary screen calls before they reach the Boss. Therefore:
Can 3CX confirm whether this behavior is intended, or whether it is a bug in the Boss-Secretary implementation?
Test Scenario
- Boss-Secretary enabled.
- Incoming calls were routed to the Secretary for screening.
- Tested both scenarios:
- Secretary answered the call.
- Secretary did not answer the call.
Observed Behavior
In both scenarios, the Boss received a missed-call notification on the 3CX mobile client and the call appeared in the Boss's call history as a missed call.However, the missed call did not appear on the Boss's Yealink desk phone.
Expected Behavior
When Boss-Secretary is active and a call is routed to the Secretary for screening, the Boss should not receive a missed-call notification.From the Boss's perspective, the call was never presented directly to their extension. The purpose of the Boss-Secretary feature is to have the Secretary screen calls before they reach the Boss. Therefore:
- If the Secretary answers the call, the Boss should not receive a missed-call notification.
- If the Secretary does not answer the call, the Boss still should not receive a missed-call notification unless the call was subsequently offered to the Boss and went unanswered.
Additional Observation
The missed-call notification appears on the 3CX mobile client and in the Boss's call history, but not on the Boss's Yealink desk phone, suggesting inconsistent handling across endpoints.Can 3CX confirm whether this behavior is intended, or whether it is a bug in the Boss-Secretary implementation?