It looks like some people in the thread below have figured it out — we actually have this. You can start a chat both ways; the system will automatically recognize if this person is on Skype for Business or on Teams.
Thanks and let me know if you have any questions.
An error occurred while saving the commentDavid Johnson commented
We had users who tried Teams, decided they didn't like it and went back to Skype For Business. In this case trying to message them from Teams sends the message to their Teams account (no Skype logo), which they aren't using. They see nothing in Skype, and only receive a missed message email several hours later.
If the Skype user messages someone in Teams from Skype For Business the message shows in Teams with a Skype logo against it. Teams users can reply to these messages and carry on the conversation, but after a while the Skype message will disappear from Teams and the Teams user is unable to message the Skype user again.
So I think our problem is that users who have tried Teams once effectively break messaging between the two products because there's no way to specify a Skype account when starting a new conversation.
Hi guys! Thanks for submitting this. I totally hear you and have experienced this as well.
The good news is, we’re actively working on this. We recently pushed an update that improved performance when channel switching and scrolling. So this should be considerably better for you.
We’ll continue to make improvements on performance, so stay tuned for updates.
Keep the suggestions coming and thank you for helping us make Teams awesome!
Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.