Omnichannel conversations with your bank or your doctor have moved beyond the conceptual phase. Arin explores how the The Vonage Conversation API unifies the channels in a way that was not possible before. Let’s take a look using examples from our SimplyDoc telehealth starter kit.
Symbl.ai’s Speech-to-Text capability is an extremely useful and much needed conversational intelligence tool for closed captioning. We asked one of our WebRTC Engineers, Hamza Nasir, to build a transcription demo with this native Streaming API into our SimplyDoc Telehealth Starter Kit, powered by the Vonage Video API.
Even a custom development shop like ours often uses a CPaaS solution when our clients need to get to market quickly or require a large range of communication options within their WebRTC application. Vonage’s comprehensive suite of Communication APIs is a definite go-to for us. We even built it into our own SimplyDoc Telehealth Starter Kit.
When choosing your WebRTC application architecture, there are trade-offs between going with a native application against the standard, an open source media server, or using a commercial CPaaS platform. There are, however, some simple rules you can follow to lead you to the right decision for your use case.
