Video Transcription
Ken Blanc: So a little bit about architecture here. This's a very simple drive, but I think one of the key points that I like to just point out is that with RingCentral Office and the integration into Teams, we've already talked about the capability to manage the location and the users through the service web.
But, you know, in most cases, when you're implementing a Teams environment, you're going to have a separate carrier connection into every location, you're going to have a separate session border controller possibly at each physical site that you have, so from a management perspective, it takes a lot to implement a Teams environment that way, when you're using the RingCentral platform, we're going over the top, 99% of the time, over the internet, and managing everything from a single web interface.
So, ease of use, ease of management, definitely, less headaches, as far as potentially finger pointing and things like that, that goes on in our environment in telecom. But also to you it builds in a level of DR Or disaster recovery. Because you're going to be using a licensed RingCentral Office licensed user, on the backside on the RingCentral side, even though you're working in a Teams environment.
So, what does that mean for the user, it means that, if for some reason, there's potentially an issue with either platform, really, to be honest, you could use as an example, let's say you're not able to use your Teams environment on a given day, you could always log into your RingCentral Office users, RC app or desktop softphone, and you'd still be able to get to your phone calls. You'd also have all of your call log records in there too.
So, if you needed to call back somebody, that information is going to be in there as well. So, it really builds in a level of DR as well.