Settings and activity
7 results found
-
5 votes
Gabriel
supported this idea
·
-
207 votesPlanned ·
AdminJessica Hernandez
(Community and Social Media Engagement Manager, RingCentral)
responded
Hi everyone, this is under development now. Current plan is to have available late Q4 2024. Will keep everyone updated if dates change. Thank you!Gabriel
supported this idea
·
-
87 votesGabriel
supported this idea
·
-
23 votesGabriel
supported this idea
·
-
3 votes
An error occurred while saving the comment Gabriel
supported this idea
·
-
170 votesGabriel
supported this idea
·
-
2 votes
An error occurred while saving the comment Gabriel
commented
I'd agree here. An example of this is a user sets a call to be blocked in Teams, yet because calls are not sent E164, Teams doesn't properly recognize the number, and thus the call is not blocked. If a user is Teams only with direct routing, they should be able to use their preferred device to block the call, not log in through a web interface.
Gabriel
supported this idea
·
Agreed. This is something that Avaya IP Office has, and it's very convenient for users who have multiple lines that they monitor voicemail for. Not all users have an email address, and with SSO implemented, this presents a challenge for checking voicemails via web or email (yes, SSO can be set on override, though InfoSec doesn't love that option). Having users call in just to see if voicemails might be on a shared line wastes time.
The message waiting indicator works for shared lines (at least on Avaya J139s), but if a user has even their direct line and two shared lines, it's unclear where that voicemail may be without dialing in (which is also problematic, but a different suggestion).