Beanfield partners with Ribbon Communications to enhance Microsoft Teams Phone integration
Dan Armstrong of Beanfield
Ribbon Communications Inc., a global provider of real-time communications technology and IP optical networking solutions, has announced a collaboration with Beanfield, a provider of telecommunications services. Beanfield will leverage Ribbon’s solution, Ribbon Connect for Operator Connect, to streamline the deployment of Operator Connect for Microsoft Teams. This partnership aims to modernise and strengthen their networks.
“Our business customers are increasingly adding telecom services to their collaboration solutions as they embrace hybrid work models. Ribbon offers us a turnkey digital engagement model to rapidly deliver telecom services for Microsoft Teams Phone, leveraging Microsoft’s Operator Connect solution,” says Dan Armstrong, CEO, Beanfield. “Partnering with Ribbon allows us to become one of a select few providers in Canada to offer their services via Operator Connect, and provide our customers this new capability.”
Ribbon Connect for Operator Connect operates as an as-a-service (aaS) solution, providing service providers with a user-friendly portal-based administration toolkit. These tools simplify the sales, provisioning, and billing of telecom services, making it easier for businesses to transition from traditional telephony services to Microsoft Teams Phone. Ribbon Connect reduces the integration efforts typically required to enable Operator Connect by providing pre-assembled API integration, sales enablement and a multi-tier portal.
“Today’s service providers are eager to enable their customers to adopt the kind of modern calling experience that Teams Phone enables and our Ribbon Connect solution facilitates this integration,” says Dave Shier, Ribbon’s VP of sales, Canada. “We’re pleased to extend our relationship with Beanfield as they continue to provide advanced options to their end customers and build on their reputation in Canada as an innovator in the telecom space.”
Comment on this article below or via Twitter @IoTGN