Workstream communications: Unified communications for reals


It all started with Voice over Internet Protocol (VoIP). Prior to VoIP, the PBX was totally independent with its own server connected to proprietary endpoints (telephones) over a proprietary network. VoIP enabled telephony to co-mingle with other servers, networks and endpoints.

Telephony grabbed hold of the concept of unified communications (UC) and made “PBX” a legacy term. A single UC client could support voice, voicemail and instant messaging (IM). UC APIs offered communications capabilities to other applications.

+ Also on Network World: Office, Outlook, Slack, Handoff: The digital workplace reborn +

While the UC industry has done a great deal with multi-modal communications, it has not been successful at unifying communications. In many ways, we are more connected and converse more than ever before, but most of these conversations occur outside of the UC suite.

Email is the big one. Email still technically works, but it was never designed for today’s workload. Last in, first out just isn’t practical with today’s volume of messages. The Radicati Group recently reported that 132 billion emails are expected to be sent and received daily by the end of 2017.

Leave a Reply

Your email address will not be published. Required fields are marked *