Skip to main content
Question

Transfer Bounce Back to originating extension when the destination user rejects or misses the transfer

  • August 5, 2026
  • 2 replies
  • 42 views

How can we configure that enables transferred calls to return to the transferring extension when the destination user rejects or misses the transfer? If transferred call is not answered by the receiving extension it should return to the originating extension.

Or if there is any alternatives we can use to achieve this requirement?

2 replies

@PhongVu Could you please look into this?


Mary-Community_Moderator
Community Manager
Forum|alt.badge.img+3

Hi ​@bibekchaulagain,

If you are looking to have transferred calls return to the original sender when missed or rejected, here is how RingCentral handles this behavior along with the primary ways to achieve your requirement:

How Transfer Types Handle Missed or Rejected Calls

  • Warm Transfer (Consultative Transfer): This is the main built-in way to meet your requirement. With a warm transfer, the originating extension speaks with (or waits for) the receiving extension before completing the transfer. If the receiving user rejects the call or fails to answer, the call stays on your line so you can immediately pull the caller back.

  • Blind Transfer (Cold Transfer): Once a blind transfer is executed, the transferring extension disconnects from the call. If the destination user rejects or misses the call, RingCentral routes the caller to the destination extension's voicemail or call handling rules—it will not automatically bounce back to the original extension.

Alternative Workarounds to Achieve This Setup

If your team needs callers to return to the original agent rather than dropping into a secondary user's voicemail, consider these alternatives:

  1. Mandate Warm Transfers: Train agents to always use Warm / Consultative Transfer on the RingCentral App or desktop phone instead of Blind Transfer. If the target extension is unavailable or rejects the call, the agent simply cancels the transfer and reconnects with the customer instantly.

  2. Use Call Park & Announce: Instead of transferring directly to an extension, the originating agent can Park the call on a specific park location and notify the intended recipient (via RingCentral chat or intercom). If the recipient does not pick up the parked call before the Park Recall Timer expires (e.g., 60 seconds), RingCentral will automatically ring back the originating extension that parked the call.

  3. Adjust Destination Call Handling Settings: In the Admin Portal under Users > Call Handling & Forwarding, you can change the target extension's "When no one answers" setting. Instead of going to personal voicemail, you can route unanswered calls to a shared ring group, main operator line, or call queue.

If this resolution helped solve your issue, please mark this comment as the best answer!