Slack + Microsoft Teams + Webex News

10 Things You Didn’t Know About Message Interoperability

Blog October 29, 2019
If everyone uses a different app, nobody is communicating efficiently
Dominic Kent


10 Things You Didn’t Know About Message Interoperability

Message interoperability

Message interoperability is when multiple messaging platforms come together as one.

Through the use of APIs, product development and the pressing enterprise requirement of syncing conversations across messaging platforms, Mio has developed the only enterprise-grade messaging interoperability tool for Slack, Cisco Webex Teams and Microsoft Teams.

Here’s some key points that you might not already know about.

  1. More than just chat
  2. Not limited to one to one chat
  3. Threaded conversations
  4. Security is paramount
  5. One-time config
  6. Not one-size fits all
  7. Non-supported features can be emulated
  8. Harder than you think
  9. Not just for collaboration
  10. You don’t have to go it alone

BONUS – Free trial

#1 – Message interoperability supports more than chat

The messaging experience is not limited to simply text. Therefore, it’s crucial that any messaging interoperability platform supports all forms of content that are shared in messages.

Mio supports file uploads, link sharing, emojis, reactions and GIFs across platform. You can send a message containing any, or all, of the above from the platform of your choosing i.e. Slack, and have it delivered in your colleagues platform, i.e. Cisco Webex Teams.

#2 – Message interoperability isn’t limited to one to one chat

Just as messages aren’t limited to simply text, messages aren’t limited to chat sessions between two people. The biggest difference between Skype for Business and Microsoft Teams is the introduction of persistent chat in the form of Teams.

Teams, channels and spaces across Microsoft, Cisco and Slack platforms all provide a team messaging experience. So, it’s vital that message interoperability includes the collaborative messaging experience too.

Mio supports team messaging through the channel sync feature. Watch the video below to see how Mio sync Webex Teams spaces and Slack channels below.

#3 – Message interoperability supports threaded conversations

When chats get passionate and there is a lot going on, or simply if your colleagues like to space out their thoughts, threaded conversations save the day.

Message interoperability would not be complete if threads weren’t included. Rather than having to switch between apps to go back and check the thread, you can stay in the platform of your choosing and remain up to date with each and every thread to keep track of information.

Threads are supported by message interoperability
Threads in Slack

#4 – Your security is paramount at all times

Mio’s approach to security is transparent. This enables your company to have a high degree of confidence when communicating across platforms.

Mio securely integrates with your messaging platforms and never stores messages or files. Protecting your data can be broken down into these key areas:

  • Classifying and prioritizing data
  • Data encryption in transit and at rest
  • Authorizing access
  • Network security

You can find out more in our security whitepaper here.

Security is a major consideration when it comes to message interoperability

#5 – Config can be a one-time thing

In the latest product update, Director of Product Marketing, Meredith Schulz, revealed the future sync feature.

When you configure your channels that need to be synced across platform, turn on future sync so that each time a new channel, space or team is created, it will automatically start syncing like your existing config.

Unlike in other solutions, you don’t need to setup additional config each time you add a user into a team.

Future Sync
Future Sync

#6 – You don’t have to sync everyone

If future sync is not for you, like when you don’t want to sync channel you create, you don’t have to.

Whilst message interoperability achieves full synchronization between teams that need to chat across platform, sometimes you need users to be restricted to one platform.

When configuring users, admins have total control of which people or channels they sync.

Channel and user mapping
Channel and user mapping

#7 – Non-supported features can be emulated

In a perfect world, all functionality will be supported. However, not all chat platform APIs allow total transparency between features.

Rather than restricting the user experience or requiring the installation and use of another app, Mio emulates features as necessary for a completely native end-user experience.

Below is a feature matrix showcasing the unsupported features that Mio emulates to deliver a seamless native experience.

Mio feature matrix

#8 – Interoperability is harder to achieve than you think

We know that collaboration tools are rarely one-size-fits-all. To aid this, there are a few methods in place that you could utilize to connect your messaging apps.

However, these don’t achieve total interoperability and you’ll likely just have another way of doing what you do today.

Integration between apps does exist across platforms like Slack, Microsoft Teams and Webex. However, this is usually achieved in bit-parts. Integrations like Webex Meetings into Slack provide access to your preferred meeting functionality, but users of Webex Teams are left having to switch between platforms to chat with colleagues that use Slack.

Multi-vendor environments often include Slack and Cisco Webex Teams

Web hooks and bot integrations provide further functionality. Often, triggers are setup so when a user of Webex Teams performs an action, something is triggered in Microsoft Teams.

Again, these only provide certain functionality and administration is often repetitive and time consuming.

To achieve genuine message interoperability, you need a platform dedicated to providing exactly that.

#9 – Message interoperability isn’t the only interoperability in the collaboration space

Last year we rounded up what a great year 2018 had been for interoperability across the collaboration industry. Pexip pioneered video interoperability and both Cisco and Microsoft introduced interoperability between their own platforms.

We’ve since added to our post with new additions from the likes of Cisco, Google, Microsoft and Slack. Check out the latest interoperability announcements here.

Message interoperability timeline
Message interoperability timeline

#10 – You don’t have to go it alone

Historically, it’s been a chore trying to keep teams in sync. When enterprises have distributed teams across multiple locations, or when shadow IT crops up, managing messaging platforms is tough.

That’s why the pro and enterprise plans come with access to a dedicated account manager. You can see the major differences between our plans below.

Mio plans
Mio plans

Bonus # – You can get a 60 day free trial

If messaging interoperability between your Slack, Microsoft Teams and Cisco Webex Teams account is for you, you’re in luck.

For a proof of concept for your combination of platforms, a 60-day free trial is available. With easy admin setup and onboarding webinars to help you onboard, it’s easy to get setup with Mio.

All you need to do to register for a demo here.

Achieve messaging interoperability with Mio
Leave a comment

One Comment
  1. […] multiple messaging platforms exist in your organization, Mio can provide┬ámessaging interoperability┬áby connecting the platforms of your old and new employees across the platforms of their […]