Comments
Completely agree this feature would be most helpful to many organizations. See also comparable requests:https://experience.dynamics.com/ideas/idea/?ideaid=67272aba-cec1-ed11-9ac7-0003ff45ac6dhttps://experience.dynamics.com/ideas/idea/?ideaid=3d0f82e8-8a01-ea11-b862-0003ff68edfaCome'on Microsoft, community is requesting and has been suffering from lack of this long enough.Any roadmap update?
Completely agree this feature would be most helpful to many organizations. See also comparable requests:https://experience.dynamics.com/ideas/idea/?ideaid=43f715b5-8a01-ea11-b862-0003ff68edfahttps://experience.dynamics.com/ideas/idea/?ideaid=3d0f82e8-8a01-ea11-b862-0003ff68edfaCome'on Microsoft, community is requesting and has been suffering from lack of this long enough.
Correction: If you look at the documentation, the pop-up message is technically correct because even if the conversation is closed, it remains in the queue. However, this pop-up is still misleading for end users, who do not understand this and fear that someone else might take the call after it is “released.” Additionally, the message displayed on the timeline during an external transfer is also somewhat misleading. It only says “Customer put on hold,” which is technically true, but there is no follow-up message indicating that the hold has ended and the call was successfully transferred. This lack of clarification increases confusion.
