LaFawnduh617

My feedback

  1. 527 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    61 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    LaFawnduh617 supported this idea  · 
  2. 5,383 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    812 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    LaFawnduh617 supported this idea  · 
  3. 226 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    48 comments  ·  Public » IP Phones  ·  Flag idea as inappropriate…  ·  Admin →
    LaFawnduh617 supported this idea  · 
    An error occurred while saving the comment
    LaFawnduh617 commented  · 

    I have the same issue with the auto attendant feature, but no call queue setup, as it is meant to route all calls directly to an O365 group to receive both audio and transcribed voicemail.
    The feature works beautifully (*outside of the delay*), but we are not yet able to publish the number to our website for this reason.
    This issue has been raised in multiple community Teams channels and hosts have offered info relating to a fixed 15 second interval built into the call queue feature for call routing, this might explain the issue some users are facing, but they could not answer to the 5-7 second delay that seems to be consistent across end user experience, whether or not the call queue function is enabled.
    Any update here? Just a comment would be helpful to know it is being looked at closer. Otherwise, we can move onto other VoIP solutions temporarily if the timeline on the fix is unclear or too far out.
    Thank you

Feedback and Knowledge Base