This effort may take many weeks or months of careful planning. Remember that in general, people will be averse to losing the app they live in all day. If the Microsoft Teams integration is not available yet, you may need to find a workaround solution or a different SaaS provider entirely. This could be a good exercise to remove redundant bots that don’t need to be replicated as connectors. You most likely have dozens – some have hundreds – of bots or integrations running in Webex.įirstly, you’ll need to conduct an audit of what you have. It’s the add-ons and plugins that make collaboration apps thrive. You’ll have to reconfigure all your Microsoft connectors so your Webex apps and bots work in Microsoft You will need to tell your team they should prepare to lose data or have a lapse in access to that data for a period of time. You will need to re-map channels that exist in both Webex and Microsoft into one Teams channel and migrate all of the existing content over. Here are two key considerations as you work to get buy-in from your Webex users: You’ll need to prevent data loss when migrating Webex channels to Microsoft Teams channels We often hear this following a merger or acquisition – when the new company is using Webex and the assumption is that everybody has to collaborate in the same app. You have two options, and you may not have known the 2nd was even possible! 1 – Remove Webex and migrate to Microsoft TeamsĪn extremely common question is: “How do we officially move users off Webex when we move to Microsoft Teams?” Your Cisco users may have organically introduced Webex as the collaboration tool in your company and could see Microsoft as the competing intruder. When you plan for that great day when your Microsoft Teams rollout is complete, do you have a plan for your Cisco Webex users? So this hybrid UC co-existence could come in a variety of ways. In a recent independent survey, we learned that 62% of businesses using Cisco endpoints are using Microsoft Teams in parallel. What is missing from these plans is a common scenario we run into with our customers…ĭeploying Microsoft Teams when some users also use Webex.
WEBEX TEAMS BOTS SERIES
Microsoft outlines 4 key stages to rolling out Teams:įurther to this, Microsoft has published a series of videos to aid your Teams deployment. These are both robust, tried, and tested frameworks that help deploy and adopt Skype for Business and now Teams.īefore you get started on your rollout, Microsoft has published a Getting Started Guide for IT Admins. The introduction of Microsoft Teams came with the Practical Guidance for Cloud Voice framework – formerly the Skype Operations Framework. If this is the case at your company, read below as there are special considerations for those Webex users when the rest of your company is deploying Microsoft Teams. If not, do employees generally know which app to use to get the fastest response from any given colleague?.If each employee has a login for both chat apps, will they need to actively use and monitor both on both desktop and mobile?.Does each user have an account provisioned on both apps or only one of them?.How can you be sure a colleague who primarily uses Webex will be able to message a colleague who primarily uses Microsoft Teams?.
Using two or more messaging platforms within your organization isn’t inherently wrong.īut, when unifying communication, there are potential friction points if not architected appropriately.
If you use Cisco hardware for video conferencing, this could mean you have users already using Webex for messaging. So, the chance of traditional Cisco houses using Teams have increased exponentially. Microsoft Teams now boasts over 145 million daily active users.
0 kommentar(er)
