Consult then transfer in Teams

Hi DavidHton4,

Welcome to post in the community.

Generally, after your consult via Call, you can click the Transfer in the page like the picture below:

For your current situation, you need to verify the users have an Enterprise Voice or Business Voice license. For further reference, there is the corresponding article:

https://support.microsoft.com/en-us/office/transfer-a-call-in-teams-b7f40f14-e083-46b9-b739-68038c8f73a0

If they have the licenses and the issue persists. to provide further assistance, we need to collect some information to narrow down the issue:

1. Please provide the screenshot the issue on your side.

2. May I know if the issue appears as your organization or the specific user?
3. Does the issue appears as the Teams web app? It is recommended to use the latest version of Chrome or Edge browser.

Looking forward to your update and we'll always be here for you.

Regards,

Joey

Hi - since the upgrade to Teams, I am unable to consult then transfer a call using voice (it still works if you only want to text/chat). When you try to consult using voice, you then do not have the option to complete the transfer, you can only end the call or resume the call with the original caller. This was possible prior to the upgrade/facelift to Teams. It is vital that we can use the phone system in this way. Any ideas apprciated!

HI - since the upgrade, our business seems to have a similar, yet opposite issue.  When trying to Consult and Transfer and the person they are looking to Consult with doesn't answer the call, the reception team cannot get back to the original caller in order to try consult with someone else.  They have to hang up on the original caller!

Any help you could offer, would be so very much appreciated!

Although it shouldn't make a difference, we are using Direct Routing, but this happens with all attempted abandoned Consult and Transfer calls (i.e. anytime the person they are trying to reach is not contactable and they need to revert to the original caller).

We were experiencing the same issue, and because of other issues that we have been following, suspected it was due to the new meeting experience.

We had the impacted users turn off the new meeting experience and restart Teams and the Consult and Transfer functionality returned to working as it should.

This seems like a pretty serious bug related to the new meeting experience, but at least this worked for us to be able to do the consult and transfer.

We are also experiencing this issue and use a system called WaveNet to route in PTSN calls. 

Seems to affect both old and new experience. 

Hi

We have had a similar issue yes.  Our partner, Wavenet, have been very good in assisting us - they've said that this could point to how Microsoft deals with calls from anonymous callers.

I don't know if this helps you as our partner has helped us directly here through their TeamsLink solution.  But perhaps knowing if this is an anonymous caller or not may help you isolate your issue.

Good luck - let's hope MS fixes the buggy 'new' meeting experience soon.

Hello

We have moved several clients over to Teams direct routing in the last few months and all of them are having issues with consult and transfer. According to our UK direct routing partner we are in the top 5 in the UK for Teams direct routing seats, but if Microsoft don't fix this issue soon we will be abondoning Teams voice.