Cloud-based communication platforms should be enterprise-ready — and here’s how

Last Friday we ran our first webinar, which we named “How an Inc 500 company Accelerates Time to Market Through iPaaS”. Our guest speaker was CTO from Star2Star Communications, a US-based telecommunications company, and the product he was talking about was their cPaaS (Communication Platform as a Service) offering.

To be entirely honest, although I knew what Sergey Galchenko, the CTO of Star2Star would be talking about in general, I was fascinated when actually hearing his presentation. The webinar turned out to be not only about time to market and iPaaS, but also about seeking innovation, searching for competitive differentiation features, looking for ways to be as efficient as possible when developing new products and concepts.

There is a webinar recording, but let’s face it, it is a conscious effort to try and find a free hour of time to watch it. So, in addition to the recording, I tried to sum up the highligts of the webinar in a short article:

Communication Platform as a Service: it’s all about simplicity of use

First of all, Sergey explained how his company’s vision of their cPaaS offering product differs from the traditional approach. Their major point was the simplicity of use of such platform, both for line-of-business users as well as developers. According to him, the API-first approach is one of the key elements:

We really have to provide it [API] for fairly complicated integration scenarios. We have been thinking about making integrations more achievable by traditional companies.

Most important thing about integrations is that you should be able to re-use them

Following that, Sergey shared why an integration middleware should be considered as an important part of Communication Platform as a Service offerings. Although Communication Platform as a Service is quite a stand-alone solution covering all types of business communication scenarios, it is inevitable that it needs to be connected to corporate data sources like CRM systems, and website elements like web forms. Sergey actually presented several concrete use cases to illustrate his considerations, one of which even involved a chatbot.

However, building integrations is not enough. Especially for large companies like Star2Star that have a substantial amount of customers, integrating their products with their clients’ systems is a resource-consuming process. Mainly because none of the previously accomplished integrations can be replicated on a larger scale.

The problem for a service provider is that when integration is done, it needs to be done in such a way that, since I invested time and effort into this integration, I should be able to reuse it for other customers.

Sergey continued explaining why Star2Star decided to incorporate a third-party iPaaS offering into the overall Star2Star Communication Platform as a Service architecture.

You’re about 43% through with reading this article.

Finish reading the rest 57%