It’s no secret that I think Microsoft Teams is an awesome product. I’ve written in the past about how I believe Teams is a great enabler for making people more productive and brings the right tools together in a place that makes a lot of sense.
What are messaging extensions?
Message extensions are available when you are creating a chat message (either a new conversation, or when replying to an existing message). Message extensions assist you by inserting content into the chat message you are composing.
Below is the Giphy messaging extension that allows you to search for an animated image and insert it into your message.
Why develop a messaging extension?
One of the resounding benefits of the Microsoft Teams client is being able to extend the out-of-the-box capabilities and integrate with your existing line of business (LOB) applications. Usually the benefit gain in integrating LOB applications into Teams is that it reduces the context switching for users and they spend more time actually getting work done, and less time moving between application, copying/pasting data or links.
Take a CRM application as an example, if you are discussing a customer in a conversation in Teams and needed to explain where that customer was located, or what the contact details were. The steps you would normally go through would be to open your CRM application, search for the customer, find the relevant details, then cut and paste multiple fields of text switching back and forth between the customer details in the CRM app and the conversation in Teams.
By extending Teams with Messaging Extensions, it is possible to provide an integration into your CRM system that would allow a user to search for a customer in Teams while composing a chat message, select the customer and have the details formatted nicely and inserted in the chat message all without having to leave Teams or even open the CRM application.
When you look at the core LOB applications within your organisation there are some key integrations such as this that can bring about real productivity gains.
Where to start with messaging extension development?
Microsoft Teams is the hub for teamwork in Office 365. The vision Microsoft has with Teams, of bringing existing products and services together into a central hub and minimising context switching, is a vision I share in and have been fostering for over a decade. Before Teams came along I’d spent over a decade of my career working primarily within Outlook and integrating/surfacing other applications and services within Outlook to provide that hub. Outlook was (and still is in most organisations) the first application opened in the morning and the last to be closed at the end of the day. To me it has been blindingly obvious that we can help make users more efficient and productive by bringing the data and information they work with into core applications that they live inside of already, and prevent them having a plethora of applications open on the desktop and constantly switching between them. Outlook was that hub application for me.
Enter Microsoft Teams, a client built from the ground up to bring existing services, applications and product features into a central hub in the context of teams of people working together on a common goal or purpose. Finally Microsoft was no longer thinking in individual products isolated from each other and starting to realise the benefit of combining the power of all of those products for a focused purpose. In essence that is what we have all been doing for many many years, we select a mix of products that allow us to get our job done and where possible we try to integrate them because products that are integrated just make our lives easier!
It’s easy to see why Microsoft Teams has been getting some seriously good traction since it’s introduction and is set to overtake Slack.
I’m sure this uptick in usage was also helped by the fact that Microsoft Teams in now a free offering.
As with any product, it won’t magically fix your business problems simply by being installed and present on users machines. To make any product successful you will need a plan and to execute on it. To this end Microsoft has released an excellent resource in the Microsoft Teams Adoption Guide. This flipbook packs a lot of valuable information into a very polished and concise package. I highly recommend it as your starting point to a successful implementation of Microsoft Teams.
What I particularly like about Microsoft Teams is that it already has a rich extensibility story with developers being able to bring existing line of business application into the Teams client and allowing Teams to be the hub not only of Microsoft products and services but also non-Microsoft products and your own custom applications.