Slack + Microsoft Teams + Webex News

Mio Product Updates – for Syncing Slack, Webex & Microsoft Teams

Highlights Mio Updates November 25, 2019
Product Updates

Mio Product Updates – for Syncing Slack, Webex & Microsoft Teams

Product Updates

Welcome to our new product updates view!

This new view now makes it easy for you to see both the latest and historical product updates.

Navigate using the menu below, or scroll to see the latest updates!
July | June | May | April | March | February | 2018

Updates for Private Group Chat across Slack & Microsoft Teams

Group chat interop for Slack and Microsoft Teams

Earlier this year, we released v1 of our cross-platform private group chat functionality.

Today we’re pleased to announce v2 of this feature, which improves the end-user experience for our Slack and Microsoft Teams customers.

Before we dig into details, here’s a quick summary of what’s new:

1- Multi-party group conversations initiated on Microsoft Teams will now always be synced as private Slack channels. The private channels will always begin with a prefix of “_teams-chat-*********.”

2- Group DMs initiated in Slack will have fixed membership in multi-party conversations in Microsoft Teams.

3- When needed, Mio will send contextual in-chat messages to explain what’s happening.

Before we get to the reasons behind these decisions, lets recap on v1 behavior.

Group chat behavior in v1

Microsoft Teams > Slack group chats

  • When multi-party conversations of 9 people or less were initiated in Microsoft Teams, Mio created it as a group DM in Slack.
  • Therefore, when Slack’s group DM limit of 9 was exceeded, Mio would automatically convert that group DM into a private channel.

Slack > Microsoft Teams group chats

  • When a group DM was initiated on Slack, Mio would, and still does, sync it as a multi-party conversation in Teams (ie- feature parity!)

Defining our MPIM Philosophy:

You’re probably wondering why we decided to change the Teams > Slack group chat logic.

As it turns out, while both Slack and Microsoft Teams both have a private group chat feature, the underlying architecture and capabilities between them are rather different. 

In fact, we’d even go as far as saying that group DMs in Slack behave more like direct messages and multi-party conversations in Teams behave more like channels.

We ultimately categorized our decision-making within 4 key pillars:

  • Membership
  • Privacy
  • Initiator
  • Maintaining chat history

1 – Membership: handling platform differences between group chat limits

Membership in Slack group DMs is limited to 9, but in Teams, multi-party chats can be up to 100.

Membership in Slack group DMs is limited to 9, but in Teams, multi-party convos can be up to 100.

With such a big difference, we knew we needed to handle Teams > Slack translation without designing a lowest-common-denominator experience for Teams users.

How ever-evolving, large membership in Teams is handled in Slack

Translating Teams group chats with 10+ participants to a true group DM in Slack isn’t possible. 

Even when it is, it’s likely to exceed that limit in the future, due to natural Teams behavior of frequently adding/removing participants.

So, rather than creating a group DM in Slack when possible, and private Slack channel when not possible, we opted for a more consistent and less disruptive workflow. 

Now Mio always (not sometimes) creates a private channel in Slack. 

This allows Teams users to freely add and remove participants without disrupting Slack users each time. Additionally, the private channel always assumes a standard prefix resulting in higher user confidence.

How Slack’s fixed membership is handled in Teams

When a group DM is started by a Slack primary, everything works natively across platforms as expected, until a Teams user changes its membership.

If this occurs, Mio will uphold the original membership of the Slack owner’s group DM.

A message from Mio is also posted, explaining what just happened and why.

A message from Mio is also posted, explaining what just happened and why.

2 – Privacy: When to post on behalf of unsynced users, and when to not!

Because group DMs are typically reserved for non-channel-specific side conversations, privacy is extremely important to maintain.

When handling unsynced users in both Slack and Teams group chats, additional consideration was given as to whether or not to add the Mio service user (or bot) to pass unsynced user messages. 

Because including a passive member in private chats could cause concern from employees, we opted instead to design a polite join/ leave flow as needed.

This includes the following scenarios:

  • When Teams users initiate a multi-party conversation that includes Slack users, Mio joins to post a “heads up” message so everyone on Teams understands the privacy policy, then leaves.
  • As shown above, when a Teams users changes membership of a private group chat originating on Slack, Mio joins, corrects, and immediately leaves, ensuring privacy stays intact. 
  • Any unsynced user participating in a private group chat will be auto-prompted (just like DM auto-prompt) and will be told their messages may not be seen by colleagues on the other platform until they are synced.

3 – Initiator: Honoring the owner of the group chat

In the case of group chats, aiming for exact feature parity when translating across platforms is not always the best approach for end users. 

Instead, we aimed to honor the initiator’s intent.

For example, even though we translate Teams multi-party conversations into private Slack channels, this logic didn’t work when initiated on Slack. 

We didn’t want to force Slack users to create a private channel every time they want to start direct messaging a group with Teams users. 

Instead, maintaining a happy path for the Slack initiator ultimately results in fewer fallback scenarios requiring explanation to end users. And, as mentioned above, it also keeps original membership and privacy intact.

The initiator pillar of our design thinking also highlighted the need to always create private channels when multi-party conversations are created on Teams. This is because we would never want to prevent Teams users from adding a 10th, 11th, 12th, etc participant to their group chat.

4- Maintaining group chat history for Slack users

Knowing the act of converting a Slack group DM to a private channel was potentially disruptive to both chat flow and history, our new v2 update keeps all chat history together, even as group membership changes in Teams.

As a future v3 improvement, Teams users can expect additional cross-platform support when opting to not include chat history in the group chat for newly invited participants.

Default naming convention for private Slack channels

When designing and developing a default name given to auto-generated private Slack channels, we carefully considered desired goals, constraints, and various options before landing on the right solution.

Goals 

  1. Provide context as to what this private channel is about (ie- a chat from Teams)
  2. Be unique – Slack doesn’t allow two channels with the same name to exist
  3. Be short – the name shouldn’t trail off the sidebar
  4. Be distinguishable – when 3+ exist in the sidebar, it’s easy to recall and find the right one

Constraints

  1. Slack channel name requirements: Channel names in Slack must follow specific rules, including no use of spaces, special symbols, or capitalizing. Channel character limit is 80. The only two symbols available to use are a dash or underscore.
  2. Need an unlimited supply of channel names: We essentially needed to code something that allows for unlimited options, while not having to generate an infinite cherry-picked list.

Naming convention options we tried but ultimately didn’t work

1 – Create the channel name using its member’s names.

This sounded like a nice idea at first. However, it became troublesome as membership changed within Teams. 

In large multi-party conversations, there were too many participants to include before the 80 character limit was met, and it wasn’t discernable from the sidebar.

For example:

If Jelena, Jacob, Tom, Amruta and Jennifer are in one private channel, and  Jelena, Jacob, Tom, Amruta, Jennifer and Meredith were in another, it would appear the same in the sidebar using a membership-focused naming convention, with a “…” at the end.

2 – Give it a random alpha-numeric combination

Next, we considered a base36 character randomization strategy. This would allow for unlimited combinations and seemed like a simple solution.

It wasn’t.

Similar to the membership example above, it wasn’t distinguishable at a glance or easily remembered.

Example:

“Hmmm, is 3t3j4fwo8gn my chat with Jelena, Jacob, Tom, Amruta and Jennifer? No, that’s Jelena, Jacob, Tom, Amruta, Jennifer, and Meredith, and t3j340owf8xn is the one I’m looking for.”

3 – Use a date or timestamp

We tested using a timestamp, but again, this didn’t pass the quick “remember and sort” user test for similar reasons.

Example:

“Where is my chat with my project team…what day did we create that chat? It’s either Teams-chat-112519-1113, or Teams-chat-116519-0913, but I can’t remember.”

Our solution

As Teams group chats are synced for Slack users, these will always appear at the top of the Channels section in the Slack sidebar. 

As Teams group chats are synced for Slack users, these will always appear at the top of the Channels section in the Slack sidebar.

Beginning with an underscore ensures the alpha-order of the channel will appear before other channels that start with a or 1.

The name will always begin with the descriptor  “_teams-chat”, followed by a randomized memorable combo-word to set it apart from others.

Creating a combo-word (ie- blue+dog, dog+jay) from two approved lists allowed for more variables and adds of a bit of fun to make these special private channels easier to remember.

Should a naming conflict arise, we’ll add two randomized numbers at the end of the name.

Future improvements to default private channel names are on the way!

While it is possible to rename channels, we recognize most users would need their Slack admin to rename the channel.

You can expect a v3 enhancement which encourages renaming the default name and provides an easier workflow for anyone to do so.

Enterprise Grid + Microsoft Teams

For Enterprise Grid users with multiple workspaces, adding their synced private channel within just one Slack workspace could lead to confusion.

To combat this, Mio creates a private channel once per workspace where any member of the conversation is a member.

Example:

If there are 4 users in Slack across 7 workspaces, Mio will create a private channel in each of the 7 workspaces to allow users to remain synced at all times.

It is important to note that we considered using multi-workspace channels, but as this is a newer feature from Slack, there is not yet an API available.

V2 Improvements for Slack Enterprise Grid customers

We will continue to refine multi-workspace handling for synced group chat.

In the future, we aim to reduce potential notification noise caused by multiple instances of the synced private channels via developing an intelligent “last active workspace” algorithm. 

Final remarks

As you can imagine, countless hours were spent diagramming, whiteboarding, testing, coding, re-coding, and debating the pros and cons of this private group chat update. 

While it was hard work, we’re proud to say we are quite happy with the end experience and know you will be too! 

December Preview

1. More Team Sync automation settings for admins

You can expect new team sync settings within the Mio Control Hub to enable more granular automation settings when syncing teams.

New options to save you time and productivity include:

  • Sync new channels: When a channel gets added on platform A, Mio will automatically create (and sync) a channel with the same name on platform B.
  • Sync channel name changes: If a user renames a synced channel – like when two departments merge – on platform A, Mio will rename the synced channel on platform B.
  • Sync archived channels: When a channel is archived in one platform, Mio will automatically archive in the opposite platform.
Custom Team Sync

2. Mio roadmap

If you head over to m.io/roadmap, you’ll find the latest features that our product team is hard at work developing.

Mio roadmap
Mio roadmap

We’ve sorted the roadmap into sections so customers can understand what is coming:

  • Near term
  • Mid term
  • Long term
  • Released and live

Each feature had its own card where you can read in more detail what the feature will deliver.

Multi-party instant messaging on the Mio roadmap
Multi-party instant messaging on the Mio roadmap

The majority of our roadmap comes from suggestions and experiences from real-world customers.

So, if you have a pressing need for something in Mio, let us know by speaking to your Customer Success Manager or leaving a comment on this new home for product updates.

You can also see specific details of features that have recently gone live on our release notes page.

Request demo

July

1 – Sync MPIMs (Multi-party instant messages)

Some conversations require more than one person. But, not all conversations are appropriate for specific channels and spaces.

Enter MPIMs- a commonly used feature within Slack & Microsoft Teams.

With our latest release, employees in Slack can now invite their colleagues who use Microsoft Teams to join a 3-way, 4-way or anything up to an 8-way direct message.

By the time you have more than 8 people in a DM, you’re back in the channel world (according to Slack).

The same is applicable across all our combinations of platforms. That means you can host multi-party instant messages between Microsoft Teams and Slack.

Multi-party instant messaging between 3 people in Slack and Microsoft Teams
Multi-party instant messaging between 3 people in Slack and Microsoft Teams

You can see in the image above that the entire conversation (text, emojis, files etc) between multiple users is replicated on both Slack and Microsoft Teams.

To give you a bit of insight into our development process, MPIMs proved to be deceptively more complicated than you might have thought!

Read on for additional details and edge-case scenarios 🤓

For starters, the feature is not named the same on each messaging platform:

  • Slack = “MPIM” (Multi Party Instant Message)
  • Microsoft Teams = “Group Chat”

Handling Slack MPIMs of 9 or more

Secondly, you may have noticed we mentioned there is an 8-person member limit to MPIMs in Slack.

For this reason, if Mio needs to sync a 9+ person group chat from Microsoft Teams, it will be synced in Slack as a private channel.

For Slack Enterprise Grid users, this can also be a private, multi-workspace channel, with members across multiple Slack workspaces, in addition to Microsoft Teams members.

Handling cross-platform MPIMs with synced and non-synced employees

As you may remember, it’s easy to quickly get your channels synced with Mio using our Team Sync feature, and for DMs, you can use People Sync to prompt your employees to sync their chat accounts.

Channels don’t require members in them to be synced, whereas DMs do.

So…what does this mean for MPIMs, you ask?

Non-synced employees will be able to create and read all MPIMs from other local or synced members, but until they are synced, Mio cannot send their outgoing messages across platforms.

For that reason, Mio will automatically ensure non-synced employees are prompted to sync when creating or sending their first message in an MPIM.

2 – Sync private channels

As of July, we can officially confirm that the ability to sync private channels in team sync is now live. As mentioned in the June product update, Mio now supports syncing both public and private channels.

Sync private channels
You can sync private Slack channels across Webex Teams within the Mio Control Hub

When private channels are synced, your users can:

  • Maintain a consistent group conversation in any channel – no longer just public channels
  • View file uploads sent across platform in private channels
  • Send emoji reactions and @Mentions across platform in private channels
  • Edit and delete messages that appear in private channels
  • Search for Slack messages in your Microsoft Teams channel directory (and vice versa)
  • The same also applies in Slack <> Cisco Webex Teams and Microsoft Teams <> Cisco Webex Teams

When initiating syncing of private channels, you also have the option to change a channel to public. It won’t be possible to revert this once synced, so decide wisely!

Changing a private channel to public

When effecting this change, you also have the option to make this standard each time you sync a private channel within your current session.

What if you want to make a previously synced Slack private channel public?

You cannot change a Slack private channel back to public after it has been synced. However, we’ve created this process to achieve your end goal:

  1. Find the channel/space in your Mio Control Hub under Team Sync
  2. Edit the sync
  3. Search for the channel or space you’d like to change back to public.
  4. Remove the channel (this will stop syncing) and save the sync
  5. Now, change the channel or space setting back to public within Slack or Microsoft Teams
  6. Go back to your Mio Hub > Team Sync
  7. Sync the channel (which should now show as public) & save.

That’s it for July! For a full history of recent releases and product updates, you can scroll down for the previous month by month briefings.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn, and Medium.

June

In the June product updates, we introduced new features for private channels, enhanced the synced channel membership experience, and launched the Mio status page.

We’ve also introduced another new member of staff.

1 – Private Channels

Just like syncing public channels, Mio now supports syncing private channels.

Each messaging platform handles private channels and membership in different ways, so let’s dive into the details by platform:

Slack and Cisco Webex Teams

Sync a private Slack Channel with Cisco Webex teams

If you sync a private channel in Slack with Webex Teams, it will create a global space in Webex Teams, so that only invited members can join this space.

Sync a moderated Webex Teams space with Slack

Webex Teams has moderated spaces that only a moderator can administer. Nobody other than the moderator has privileges to invite additional members to the space.

It is this functionality (moderated Webex Teams space) that Mio will sync with Slack.

Slack and Microsoft Teams

Sync a private Slack channel with Microsoft Teams

When you add a Slack private channel to Microsoft Teams, Microsoft creates a private team and a public channel in that private team – emulating a private channel feature for Microsoft Teams. You also have the option to make it public if this betters suits your team.

Sync a channel in a private team in Microsoft Teams with Slack

If you have channels in private teams within Microsoft Teams, these can be synced with private channels in Slack. By syncing public channels in private teams, Slack users will maintain the consistent private channel experience.

When adding a public channel in a private team to Slack, admins can also choose to make it public in Slack.

Private channels
Private channels

Finally, we’ve made it clear which channels are private by including a padlock next to the channel name. Like our “supertopsecret” channel above.

When private channels are synced, your users can:

  • Maintain a consistent group conversation in any channel – no longer just public channels
  • View file uploads sent across platform in private channels
  • Send emoji reactions and @Mentions across platform in private channels
  • Edit and delete messages that appear in private channels
  • Search for Slack messages in your Microsoft Teams channel directory (and vice versa)
  • The same also applies in Slack <> Cisco Webex Teams and Microsoft Teams <> Cisco Webex Teams

2 – Synced channel membership improvements

We’ve improved channel membership handling for synced people to reduce noise in your organization.

Once synced, people will be added to new channels as they are @ mentioned or invited.

Like before, people will still be able to search for any public channel and join it (once it has been synced using Team sync).

This is especially helpful for Microsoft Teams to Slack, where Microsoft Teams membership is at the team level, not channel member.

In this scenario, rather than inviting all Slack Primary members to all synced Teams channels, members will be added to the synced channel in Slack as they are mentioned or invited.

3 – Mio status page

If you head over to m.io/status you will find the real-time status of our service. You can use this page to monitor any outages or issues that may occasionally occur.

Mio status page
Mio status page

The color indicators relate to: up and working fine (green), an incident known (amber), and and outage reported (red).

The not available symbol represents functionality not currently available via the specified platform.

4 – Remove teams

In the May product updates, we introduced functionality to remove a sync. This month, we’ve made it possible to remove a whole team, should you ever need to.

You might need to remove a team if:

  • The team was for a temporary project
  • All members of the team have left the business
  • The team has been rolled into a new team or channel
  • A duplicate team exists

To do this, head to Manage Teams.

Manage Teams
Manage Teams

Under the actions column, click the “” next to the team you wish to remove.

Click "..." then Remove
Click “…” then Remove

You will receive a warning notification which will make you aware of what happens when you remove a team. Check this through to make sure you are okay with that, then hit Remove Team.

Remove Team
Remove Team

5 – New to our team

Amruta Birar

Amruta has joined as a Quality Assurance Engineer. She brings technical expertise to automate QA.

Amruta Birar
Amruta Birar

Amruta has been pursuing her career in a direction so that she can serve the world to develop products that provide meaningful insights to make a world a better place!

“Most of the problems in the world are due to lack of good communication and Mio solves that problem. I am excited to be a part of this journey and create an impact in the domain of quality assurance!”

That’s it for June! You can also visit our product release notes page to see a full history of recent releases.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn, and Medium.

May

In May’s product updates, we added several new features within the Mio Control Hub to offer admins more insight and capabilities when syncing their teams across Slack, Microsoft Teams & Cisco Webex Teams.

We also welcomed two new full-time staffers (you may be familiar with them already!).

Let’s dive right into the details!

1- More dashboard metrics

The Mio dashboard now has additional metrics to give you further insight into how your teams are benefitting from Mio.

Dashboard metrics
Dashboard metrics appear when you first log in to your Mio Control Hub

Once you’ve synced two or more teams, the above tiles will appear demonstrating key cross-platform metrics about the channels and people synced within your teams. This is especially important when first rolling out or trialing Mio.

Time frames are included to examine change over the last 14, 30 and 60 day period – as well as an option to see all-time stats. Platform usage breakdowns are also included within channel activity.

Channels synced
Channels synced

The channels synced tile shows the number of channels currently synced across platforms within your entire organization, in comparison to the total number of channels available to sync.

People synced
People synced

Similarly, the people synced tile shows the number total number of users that are synced in your organization, in comparison to the total number of users within your organization.

Channel activity
Channel activity

The channel activity tile shows a detailed view of the total number of messages sent between platforms among all channels synced in your organization.

You can see a platform percentage breakdown to better understand usage. In the screenshot above, you can see 63% of users are sending messages from Slack and 38% are using Webex Teams. Toggle between the last 14, 30, 60 days, or all-time to measure change and adoption.

People sync details
People sync details

People sync details shows the number of synced people by their primary platform. The number of users yet to be synced is also shown so you know how far away you are from complete cross-platform collaboration.

Direct messages
Direct messages

The direct messages tile shows how many direct messages have been sent from one platform to another. As you prompt more people to sync their accounts, this stat should also increase.

@Mentions
@Mentions

The @mentions tile shows how many times users have been @mentioned in channels across platforms.

2- Remove a sync

When teams no longer require syncing across platforms, we’ve added a “remove sync” option.

Remove sync
Remove sync

Within Team Sync, you can now view and remove any syncs that are no longer needed in your organization. By clicking the “” icon next to each sync, you will be presented with the options to edit or remove the sync.

Once the sync has been removed, channels on each respective platform go back to being non-synced channels.

If you are using the new Future Sync function, it will also be disabled.

3- Hover to show sync actions in Team Sync

When syncing channels in Team Sync, there is now a cleaner experience. Within your channels list, hover over any channel in your list to see actions to connect or add your channel to the other platform.

Hover to show sync options
Hover to show sync options

4- Origin and destination labels in Team Sync

When syncing channels, labels have now been added to show you the origin and destination of your channels. For example, in the below screenshot, you can see “devops” has been added to Microsoft Teams, from Slack.

Origin and destination labels for channel syncing
Origin and destination labels for channel syncing

5- New to our team

Dominic Kent

Dominic has worked as a contractor with Mio since July 2018, running the Dispatch blog. He joins Mio full time as Director of Content Marketing and Communications.

Targeted with growing the brand through all forms of content, Dominic will use his background in Unified Comms and product marketing roles, as well as his recent experience as a freelance journalist with UC Today, to curate content that relates to genuine enterprise messaging needs.

Dominic Kent
Dominic Kent

“Joining Mio full time was a no-brainer. The best marketing tactic is to have a great product. The Mio team has built a product that will dramatically improve the way businesses communicate internally. How could I not be part of this journey?”

Joe Beutler

Joe has joined as our Customer Success Manager. He was most recently co-founder of DASH, a Capital Factory Accelerator company. As a former Goldman Sachs software engineer, Joe brings technical expertise to our Customer Success team.

“The Mio team’s prior startup experience combined with a unique product has created a rare market opportunity. I am thrilled to join Mio at this exciting stage of the company.”

That’s it for the month of May! You can also visit our product release notes page to see a full history of recent releases.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn and Medium.

April

April was a big deal.

The all-new Mio Control Hub for IT admins had been in design and development phase over the last few months.

After extensive feedback, we launched the next generation of Mio.

The new UI and features in v3 will make it easier for admins to configure and sync their teams. It will also provide deeper insights into multi-vendor messaging environments across Slack, Cisco Webex Teams and Microsoft Teams.

Overview

Within the new Hub, you’ll quickly find access to all main features on the lefthand navigation:

Mio Control Hub
Mio Control Hub – Dashboard
  • Dashboard: displays overview stats
  • Manage Teams: add and authorize new teams to enable syncing
  • Team Sync: connect your individual channels across teams, or an entire team’s channels
  • People Sync: prompt people to sync their primary platform for a seamless messaging experience
  • Channelytics: monitor data for synced channels
  • My Organization: manage your organization’s profile and contact information

Let’s walk through what’s new…

Onboarding in Mio v3

Track & save your progress

The latest version of Mio introduces a new onboarding format which tracks progress as you move through each step. As you complete information in each step, you see an indicator of what you have completed, and what is left to complete. As you move along the process, Mio now autosaves progress as you go.

Simplified Mio onboarding UI
Simplified Mio onboarding UI

Add collaborators

Within the onboarding interface, you can now add a collaborator for additional admins to view and help with the onboarding process. This is ideal for teams with different owners for Slack, Webex Teams, and/or Microsoft Teams.

Once registered for Mio, admins will receive an email containing a unique URL for your Mio account.

Create Service Accounts & Platform Apps

We’ve simplified the UI to make creating your instance of Mio a swifter process.

Once you’re done filling in the details, you just need to hit review and submit to complete your onboarding. Once approved, you’ll soon have access to your Mio Control Hub.

New features for Team Sync

Sync one, many, or all channels in your team in a single interface

Within the new Team Sync section, you begin by simply selecting two teams you’d like to sync. You can then sync all channels within them in one go, or come back to select more later. Once synced, message interoperability is created across channels and spaces.

Team Sync
Team Sync

Add a channel to another platform with ➡️

When a channel exists in one messaging app, but not the other, you can now sync it easily. Simply use the ➡️ feature to add the existing channel into the other chat platform. If a name already exists, Mio even flags a query so there is no overlap.

Sync actions
Two ways to sync channels within Team sync

Connect existing channels across platforms with 🔄

When the channels you’d like to sync already exist in both platforms, Mio now enables you to connect them with the click of a button.

Let’s say you want to connect a UX channel in Teams to a Design channel in Slack, that’s the perfect time to use this new feature within Team Sync.


Add channels across platforms or connect existing channels
Add channels across platforms or connect existing channels

Future Sync

As part of the final step in Team sync, we’ve included an option called Future Sync. Rather than returning to the Mio Hub each time an employee creates a new channel, space or team, future sync automatically syncs the new channel by adding it ( ➡️) to the other platform.

Future Sync
Future Sync

Future Sync is an optional setting that can be toggled on and off for your convenience.

New Search feature

Mio v3 includes a new search feature for enterprises with lots of channels. Just type the name of the channel you are looking for, and complete your sync within search.

Searching within team sync

New features for People Sync

People Sync allows admins to prompt employees to set their preferred primary chat platform so that direct messages from secondary platforms can be routed and posted natively.

Toggle auto-prompt to turn on in People Sync
People Sync in the Mio Control Hub

The new UI displays a quick assessment of each person’s sync status. Admins can then take action to prompt individuals, a group, or an entire team in bulk. You can read more about People Sync here.

Auto-Prompt

When the new auto-prompt feature is enabled in People Sync, admins do not need to individually prompt users.

Instead, your Mio app or service user account will send a triggered prompt message to the user when they attempt to DM with a synced colleague.

Channelytics

The new Channelytics feature provides insights about your synced channel activity and engagement.

Channelytics
Channelytics

Drilling into a channel shows log-level information, in case you’re curious about active users and most recent activity. Expect to see more improvements to channelytics later this year.

Synced channel
Synched channel

That’s it for April! You can also visit our product release notes page to see a full history of recent releases.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn and Medium.

March

In the early stages of Mio, Microsoft Teams was the most requested platform. Below is a video update from our launch of Microsoft Teams working with Slack!

Mio for Microsoft Teams and Slack

Mio now fully supports cross-platform messaging for Microsoft Teams to Slack. As a recap, the Mio product for Webex Teams & Slack delivers these native cross-platform features:

  • Direct Messages
  • Channels/Spaces
  • File/Image Uploads
  • Emoji Reactions
  • Threaded Messages
  • @ Mentions
  • Editing/Deleting Messages
  • Rich Text Formatting

Below outlines all cross-platform messaging features Mio will enable for each platform:

Mio product updates for April introduced Microsoft Teams interoperability

Now let’s dive into some specifics!

Microsoft Teams & Slack Interoperability Progress:

1. Private and group chats in Microsoft Teams map to DM’s & channels in Slack

Whether you’re starting a quick conversation with a colleague, or pulling together a team in a channel to answer questions, we’re going all-in on full interoperability for Microsoft Teams conversations with Slack participants.

This end-to-end chat user experience is native, seamless, and refined by our beta testers.

2. Entity detection = native @ mention support across Slack and Microsoft Teams

We deliver native @ mentioning between Slack & Microsoft Teams users. Specifically, when a Slack user @ mentions a colleague who primarily uses Microsoft Teams, we natively mention that user within Microsoft Teams.

@ mentions from Microsoft Teams to Slack
@ mentions from Microsoft Teams to Slack

3. Edit / delete for chat between Slack & Microsoft Teams

When a Microsoft Teams user edits their message, the message will instantly update in Slack, and vice versa.

Edit / delete for chat between Slack & Microsoft Teams
3. Edit / delete for chat between Slack & Microsoft Teams

4. File Uploads from Microsoft Teams into Slack (and vice versa!)

This is a big feature that we’re very proud to offer! From XLS to CSV, PNG to PSD, multiple users receive files natively within the conversation.

File Uploads from Microsoft Teams into Slack
File Uploads from Microsoft Teams into Slack

5. SSO Integration

SSO support is built per provider, starting with Okta. We’re excited to work with our pilot customers and their iDP providers as we expand the offering.

6. Channels in Sync across Microsoft Teams & Slack

Cross-platform channels are supported across Webex, Slack, and now Microsoft Teams. This is critical for cross-department teams working on projects together.

Mio for Microsoft Teams and Slack
Mio for Microsoft Teams and Slack

That’s it for March! You can also visit our product release notes page to see a full history of recent releases.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn, and Medium.

February

In February, we shared a preview of v3. We’ll also took a moment to introduce you to our newest team members: Jacob, Frank & Brent.

Revamped admin UI & new features coming soon!

Based on customer feedback, we’ve given the Mio Control Hub a revamped user experience and interface.

Administrators will soon enjoy an easier setup process and a more intuitive sync workflow that provides deeper insight into messaging configurations across Slack, Microsoft Teams & Webex Teams.

Here’s a few highlights of what to expect:

Self-service setup process

Admins ready to get started with Mio can complete their setup via a self-service URL with guided instructions.

Mio Hub setup
Mio Hub setup

Customized channel and team syncing

Our new Team Sync feature will enable a variety of ways to view and customize how admins can keep their teams in sync across chat platforms. This will include individual and “full team” channel syncing functionality.

Also included will be the ability to rename channels and auto-add any new channels employees create in one chat platform to appear in the other.

Sync people at a glance, or automatically!

People Sync allows admins to prompt employees to set their preferred primary chat platform so that messages from secondary platforms can be routed and posted natively.

People Sync
People Sync

The new UI will display a quick assessment of each person’s sync status. Admins can then take action to prompt individuals, a group, or an entire team in bulk.

An auto-prompt feature will be available as a “set-and-forget” offering, which keeps new (or forgetful!) employees informed about how to activate syncing.

New to our Team

In addition to new product UI and features, we’d like to take a moment to introduce our newest team members:

Jacob Ross, VP of Product

Jacob Ross joined as VP of Product in December. He was previously Program Manager at Ticom Geomatics. You may have seen him at Cisco Collaboration SVET this week.

Jacob Ross
Jacob Ross

“Mio has been great. The team is fun and super smart and everybody is excited about our product.”

Frank Geck, Director of Customer Success

Frank Geck has joined as our Director of Customer Success.

He was most recently at Cisco on the Collaboration Ecosystem team, where he helped grow the program from scratch to more than forty partners generating over eighty million dollars of impact yearly.

Frank Geck at Cisco Collaboration SVET
Frank Geck at Cisco Collaboration SVET

“I joined Mio for two reasons. First, the team. Tom Hadfield has put together an exceptional team that I wanted to be a part of. Second, the need for the Mio interoperability solution. Collaboration should work and not be restricted by walled gardens. In today’s work environment, it’s impossible to mandate which tool people will use. Let them choose.”

Brent Musat, DevOps Engineer

BrentMusat also joined the Mio team as our DevOps Engineer. He also joins from Ticom Geomatics where he spent 7 years as a Test Engineer.

Brent Musat, DevOps Engineer
Brent Musat, DevOps Engineer

“I’m extremely impressed with the team of people here at Mio. Everybody is so knowledgeable and dedicated to making this product work. It’s exciting and motivating to see that level of enthusiasm from everybody.

That’s it for the month of February! You can also visit our product release notes page to see a full history of recent releases.

Don’t forget you can keep up with all the action by following Mio on TwitterLinkedIn and Medium.

November

Mio v2 was announced in November!

We also re-architected our service so it runs in a dedicated environment for each customer. Even more, the end-user experience for employees has been simplified, so adoption of cross-platform communication can happen instantly.

Read on for all the details about these updates and features in Mio version 2.0:

1. More admin controls in the Mio Hub

We’ve streamlined the M.io admin dashboard, aka “The Hub” to help IT administrators have full control over their team’s messaging interoperability across each chat platform. This means a business can log into their own Mio Hub site and configure all their settings for the following sections:

  • Organization details – determine the key contacts and access controls for Mio
  • Service accounts – link up the service accounts via auth-flow per platform
  • Channel Sync – control how channels and spaces mirror
  • People Sync – prompt users to connect accounts and show an overview of the team roster and who is fully connected to Mio

2. New dedicated Mio Hub environment

Building on the above, and based on our customers’ feedback, we’re going all-in on isolating each instance of Mio in a dedicated environment.

By incorporating the latest in container technology, there is no longer a public version of Mio in the Slack or Webex app stores.

As of Q4, we’ve moved all our technology into dedicated and virtual private clouds so each customer has complete control of their messaging interoperability.

3. Mio’s UX – more seamless than ever

Mio DM across Slack, Microsoft Teams and Cisco Webex Teams
Click to see how DMing works across Slack, Microsoft Teams and Cisco Webex Teams

With cross-platform messaging, we’ve learned it’s critical to act invisibly behind the scenes to create an end-user experience that “just works” without adding cognitive load for end users.

With this in mind, we’ve reduced a large portion of our original conversational menus to keep the experience as true to their native messaging app’s experience as possible. 

Some examples of Mio’s seamless native experience:

  • If you create a new channel or space, we’ll mirror that channel on the other platform
  • Format text in any way and we’ll match it on the other platforms
  • @mention colleagues and we’ll transcribe it automatically across corresponding platforms
  • Add guests in Slack, Cisco Webex Teams or Microsoft Teams, and we can natively invite them on the opposite apps
  • Edit or delete a message, and Mio will reciprocate the action on the other platforms
  • Add a user on one platform natively, we’ll add them on the other

After an IT admin completes Hub setup, employees can immediately start chatting and using the functionality above, without logging in or doing anything different than they did before.

Many of our end users won’t even realize they are communicating with a colleague who uses another platform! 

August

In August, our product update saw two key features that give businesses the ability to synchronize all public channels and spaces: The new Mio Hub and Channel Sync.

Based on user feedback in pilot customers, we’ve streamlined the Mio setup process to make enabling an entire organization’s cross-platform chat possible, all without requiring employees to take additional setup steps.

Let’s take a closer look at both updates.

Introducing the Mio Hub for Admins

Creating a hub in Mio
Creating a hub in Mio

What is the Mio Hub?
Mio Hub is the best way to quickly connect all Slack workspaces and Webex Teams accounts in your organization. This power feature activates team-wide interoperability across all chat accounts and it’s life for you to try it out.

Here are the simple steps you go through when setting up your Mio Hub:
.
1. Go to http://m.io and select “Create Hub”

  • Name Your Mio Hub & choose an icon
  • Authorize admin access for your primary chat platform
Allowing access in Mio
Allowing access in Mio
  • Add a second chat team account
Add a second team in Mio
Add a second team
M.io Webex Authorization
Mio Webex Authorization
  • Once you confirm all these steps, you’ve created a Mio Hub for your company at https://{companyname}.m.io!

2. New: “Channel Sync” for Slack & Webex Teams

The last step of the new Hub creation process above reveals our other new feature, Channel Sync.

What is Channel Sync?
Admins can make all public Slack channels auto-appear as spaces for Webex users, and make all Webex Teams spaces auto-appear as channels for Slack users. Create a conversation on one end and it’s live and running on the other in real-time ✊

See public Slack channels in the Webex Directory, and Webex spaces in the Slack channel directory, thanks to M.io
See public Slack channels in the Webex Directory, and Webex spaces in the Slack channel directory, thanks to Mio

Why we built it:
For companies with tens/hundreds/thousands of channels and spaces across Slack and Webex, there’s a strong need for all public conversations to be listed and available.

Once Mio Channel Sync is activated, it’s easy for any employee to natively find, join and invite members.

How Channel Sync works for admins:

During Hub setup shown above, Mio will create a real-time copy of all public channels and spaces.

  • Channels and spaces found across all team accounts that were imported into the Mio Hub will be copied and sync’d for members, and will also be automatically added to public native Slack and Webex Teams directories.
  • Private channels will not be included in Channel Sync.
  • Channel Sync also works for multiple Slack workspaces, not just Slack to Webex Teams.

How Channel Sync works for employees:

  • Employees have all spaces and channels available to join and chat in both Webex and Slack. They can instantly send messages in these channels and the entire group will receive them, no matter what platform they each use.
  • All public conversations can be discovered and joined via the native Slack & Webex Teams directories.
  • Employees can optionally decide to set one chat platform as their “primary” moving forward, so when they receive invitations to new spaces or channels, Mio knows to automatically create a new copy within their preferred platform.
    Channel and Space invitations
  • M.io lets you natively add Slack users to Webex Spaces and Webex users to Slack channels!
  • Slack & Webex Teams can seamlessly work together

You made it…

You’ve reached the beginning of this version of the Mio product updates.

If you’re after more, check out our Workplace Messaging Report where we reveal the results of current and future usage of apps like Slack, Cisco Webex Teams and Microsoft Teams.

Then make sure you’re following us on Twitter and LinkedIn to keep up to date with the latest product and industry happenings.

Request demo
Leave a comment

Leave a reply

6 Comments
  1. […] and give you more insight to your Slack and Webex Teams usage. That’s why our latest product update consists of a revamped admin UI and new features to make onboarding and management of Mio simpler […]

  2. […] Sync all the chat apps your teams use by creating your Mio Hub (read more about channel syncing here) […]

  3. Mio Release Notes

    […] private Channel Sync support for Slack, Webex Teams, and Microsoft Teams. See our product updates page for more […]

  4. […] Mio launched private channel sync for Slack, Cisco Webex Teams and Microsoft […]

  5. […] you’ll be able to send a message or prompt that encourages users to do this. You can also access the new Auto Prompt feature to automatically ask users for […]

  6. […] You can read the latest Mio product updates here. […]