Settings and activity

2 results found

1. Warm transfer to call queue is not retaining caller ID

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Phone & Messaging » General Phone  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Fearghal shared this idea  ·  Sep 10, 2024

2. Retain Caller ID information regardless of blind/warm transfer type

   177 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   15 comments  ·  Phone & Messaging » Hardware  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Needs More Information  ·  AdminJessica Hernandez (Community and Social Media Engagement Manager, RingCentral) responded

   Hello everyone, this has been implemented in 22.3.1. This version of the app was rolled out to all accounts over 8/25-8/31. No additional action is required to initiate the feature on the app, please confirm you are on at least 22.3.1. This feature allows for caller ID to transfer in these scenarios. Warm/Consultative Transfer: - Incoming call from PSTN/RC # to RingCentral and transferred to RC number Blind Transfer: - Incoming call from PSTN/RC # to RingCentral and transferred to RC number - Incoming call from PSTN/RC # to RingCentral and transferred to RC voicemail The feature requires the following endpoints to work successfully. This applies to both the user invoking the transfer as well as the user who is the destination of the transfer.Desk phones: Any Poly, Avaya or Unify models. RingCentral App: Version 21.4.30 or laterRingCentral Mobile App: Version 22.1.10 or laterRingCentral Phone App: Version 22.2 or later This feature does not work with Cisco or Yealink phones. This feature has not been formally tested on Mitel phones, it may or may not work.

   Hello everyone, this has been implemented in 22.3.1. This version of the app was rolled out to all accounts over 8/25-8/31. No additional action is required to initiate the feature on the app, please confirm you are on at least 22.3.1. This feature allows for caller ID to transfer in these scenarios. Warm/Consultative Transfer: - Incoming call from PSTN/RC # to RingCentral and transferred to RC number Blind Transfer: - Incoming call from PSTN/RC # to RingCentral and transferred to RC number - Incoming call from PSTN/RC # to RingCentral and transferred to RC voicemail The feature requires the following endpoints to work successfully. This applies to both the user invoking the transfer as well as the user who is the destination of the transfer.Desk phones: Any Poly, Avaya or Unify models. RingCentral App: Version 21.4.30 or laterRingCentral Mobile App: Version 22.1.10 or laterRingCentral Phone App: Version 22.2 or later… more
   Fearghal supported this idea  ·  Sep 10, 2024
   An error occurred while saving the comment
   Fearghal commented  ·  Sep 9, 2024  ·  Edit…  ·  Delete…

   I can confirm this was briefly fixed for us two months ago and after two weeks of working it suddenly stopped passing caller ID after warm transfer. We are on 24.3.252.11815. This is critical for us for agent callbacks to customers for technical queries and needs to be fixed.

   Save Submitting...