Just keep adding to the sludge! More proprietary protocols and islands! The biggest problem with "Unified Communications" in business is effortless federation

Just keep adding to the sludge! More proprietary protocols and islands! The biggest problem with "Unified Communications" in business is effortless federation with your vendors and customers. Teams just makes a bigger mess, but then so does Slack and Cisco Spark. So add a Web conference tool or two (I have WebEx and Skype for Business conferencing), but the audio is annoyingly poor on S4B business. Don't forget our phone system, SharePoint, OneDrive and Yammer. And while you are at it, have you kept up on LinkedIn and Twitter? To communicate with international colleagues, you will also also need Whatsapp. Perhaps you are working at a company with Google Apps with Hangouts, and may your deity of choice help you if you have Salesforce Chatter (A torrent of mental diarrhea) Of course bots are the future because I always wanted a text interface, or better yet, an ASR/TTS interface because I like practicing my English with a 3 year old. This is a cluster and it is quickly getting worse. None of these companies are actually trying to help. So far as I can tell, they just want to grow their adoption numbers, try to preserve some revenue as long as they can and maybe kill the PSTN, but I can't even make a phone call between any of these systems. Then, with one small blip an entire system goes down, so I have to call you and send a email with the file you need. XMPP is dead, SIP/SIMPLE isn't appropriate for IRC/Slack type apps. WebRTC is great for clients, but what about the backend, and federation? I love what I see with Riot, and I appreciate Google trying to move forward with the IMS replacement of SMS (Good luck explaining that one to the public, let alone market it...) While all of these companies will babble on endlessly about being open and committed to international standards bodies, real time communication applications are where they are at their worst.