Forum Discussion
Missed calls are not shown on history that came through call queue
Hi shravanDH
The best way I've found is to enable Conference Mode on the Call Queue and setup an iPhone with Teams where either a dummy user or an actual agent is signed into the Queue. This way missed calls are displayed as red in the iPhone's (not Teams App's) call history. There's no notification badge, meaning somebody has to check the iPhone's call history every now and then. You can however switch the view between all recent or just missed calls. You can also see calls which were answered on another device / by another agent (shown in white/black depending on dark/light mode) if you tap on the entry to see the call details. This does not work on Android. I hope this helps.
Ouch. That's just shy of $3K per year for something which should be built into the system.
Dave_Purscell so thats an more affordable solution - for just that problem. https://twincapfirst.ch/teams-easy-call-report-en/
Will probably go this route, as long as Microsoft is not able to solve that issue.
- Thanks for the link. Took me a while to translate and navigate their cookies popup. The text was mostly in English but the buttons were all in German. 😄
Looks like an interesting solution. Unfortunately, I cannot utilize it because of compliance restrictions under HIPAA. They are operating in Azure in a EUR datacenter. We have to be domestic. Sigh...
Hopefully they (or a competitor) will see the untapped market and setup a second copy in the US.- Are there any news regarding this issue ?
Our "transfer" to Teams Phone System stuck because of this behaviour.
Are there any plans from Microsoft to fix this ?Sadly we have not received any response from Microsoft.
Fortunately, all of the members of this particular department have a county provided iPhone for their business use. Our work around (such as it is) for this critical department is that their iPhone detects the incoming Teams call and adds it to the missed calls for the iPhone itself. In other words, we are relying on an accidental behavior from a different vendor.
Come on Microsoft. Please fix this deficiency of your solution.
