We just launched our 2.1.2 release!
As we said in our first post we have been around for over a year.
We had our first subscribers with our alpha release, we announced our beta last November at WebSummit, we have been in production since March(1). So, with this note, we are diving right into our latest release… we will talk more about our overall unique capabilities existing subscribers have been enjoying, in upcoming postings…
We thank to all our subscribers who have helped us refine our solution! We know that some of our you have been asking for it, so here it is! We are happy to introduce “Texting” with our 2.1.2 release!
Here’s how it works:
- WebRTC is the technology we are using for the video chat. Some of the major browsers like Safari and Firefox do not support WebRTC technology yet (or are buggy). Until now, we were just displaying a message for our users who wanted to start a video chat saying that they need to switch to Google Chrome browser. From now on, these users will be connected with a text chat session!
- Sometimes you may not be able to pick up a video call. We now give you the choice to answer an incoming call via texting. You can still connect to your potential customers and will not be limited to the messages that they can leave you.
- We know that during a video chat, there comes a point where an address or a link is needed to be sent. With 2.1.0 release, we also provide texting during a video call. On the left, we now have a texting button where our users can text while remaining on the video call.
- We also give our customers the ability to turn video calls off and use texting only. All you have to do is to select “Chat Only Call” option on the button configuration settings.
We are very excited about our new features and looking forward to receiving your feedback.
We will constantly keep updating our product to give you the best experience and cannot wait for you to see what we have on our plan!
See you on the next release!
(1) we had aimed at January, but we had to wait for a WebRTC bug be fixed in the Chrome browser…