We have just rolled out an important update to the Gruveo web app that boasts compatibility improvements as well as exciting new features. Find the full scoop below.
We have improved Safari 11 compatibility even though Safari’s WebRTC implementation remains limited. Switching from a one-on-one call to a group one or toggling call recording no longer means that the Safari users will automatically lose video. When switching to a group call, Gruveo will try to choose a video configuration suitable for most call participants, including the Safari ones. And toggling call recording will now have no negative effects for Safari users whatsoever.
The Temasys WebRTC plugin has served us well to enable Gruveo in the otherwise unsupported browsers (think Internet Explorer and older Safari), but the time has come to say goodbye. We dumped Internet Explorer support on the same day that plugin-less support for Safari 11 was released. And with older versions of Safari fading away, we feel that removing Temasys plugin support altogether will let us deploy our development resources more productively.
In what has been a truly long wait for a lot of Gruveo developers out there, Safari support finally lands in the Gruveo Embed API. A newer version of the browser is required, namely Safari 11.1+ on macOS, or Safari on iOS 11.3+. See the Embed API documentation for the updated details on the supported browsers.
You can now use a dot (.) when registering a Gruveo handle or creating a call room. The handle or call room name cannot start or end with a dot, or have two or more dots next to each other. This change was prompted by more and more businesses looking to allocate multiple handles on Gruveo. Having the option to use the dot as a separator should give you more flexibility when getting Gruveo handles for your organization – think @acmeinc.support, @acmeinc.sales, @acmeinc.marketing etc.
We’ve listened to your feedback on the Gruveo call button, and we’ve made a couple of important changes. First of all, you can now explicitly choose whether clicking the button will start a video or a voice call. Second, we have removed the Gruveo branding and your @handle from the button, leaving the button title simply as “Video call” or “Voice call”, with a respective icon. These changes are aimed at making the button more versatile and its functionality more understandable to your website visitors.
Do you have any questions on today’s Gruveo update? Let us know in the comment section below, or get in touch with us directly!
We are excited to announce the launch of the Gruveo Affiliate Program! The program lets you make money by partnering with Gruveo as an affiliate and earning a whopping 25% recurring commission on any customers you refer.
Here is how it works: When you become an affiliate, we’ll provide you with a special affiliate link. You’ll then use that link to refer businesses in need of an easy-to-use video calling solution to Gruveo. When we receive a visitor through your affiliate link, we’ll associate that visitor with your affiliate account. If they then order a Gruveo subscription, you’ll receive a 25% commission on any payments they make.
The commissions are recurring, which means that you will receive income from referring a Gruveo subscriber for as long as they stay with us.
We’ll also provide you with a special Affiliate Dashboard where you can monitor your affiliate account activity, as well as with text links and banners to help you successfully promote Gruveo.
To learn more and sign up as a Gruveo affiliate, head to our Affiliate Program page today!
Call recording is a standard feature of the Gruveo API and SDKs that allows you to obtain HD-quality recordings of your users’ conversations almost immediately after the call is over. Up till now, the API only supported uploading of the recordings to your Amazon S3 bucket, which wasn’t the most convenient choice for some users. By popular demand, we are now extending the API’s capabilities to also offer recording uploads via FTP/SFTP.
If you’d like FTP/SFTP uploading of call recordings to be set up for your API account, please contact us with the following information:
Please refer to the API/SDK documentation for details.