WorkinSync is an emerging leader in Flexible workspace management. Given our “Employee First” approach of building products, we wanted to make features such as desk booking available to employees in a smooth workflow, regardless of their location. Microsoft Teams emerged as the central communication tool for remote and hybrid teams for many enterprise clients. So we worked hard on developing a top-quality WorkinSync app for Teams.
Bonus Tip: 5 Features for Hybrid Workplace Tools
A Teams bot is one of the key capabilities we want to leverage to give a Teams user a unique experience. We didn’t want to restrict ourselves to a simple command-based menu for our bot since users expect a basic natural language understanding from ‘bots.’
The default option to power the NLU layer was to go with Microsoft LUIS. However, we had already done the hard work of training a bot for our Google Assistant App. It would make more sense to reuse the same agent for the Microsoft Teams App as we wouldn’t have to create, train, test, and maintain our conversation flows on two different platforms.
This is how the tech team at MoveinSync went about building the bot.
[Disclaimer: This is just a preview to illustrate the plumbing and not the actual application code]
The backend service for our Teams App is written entirely in java. The bot exposed to Microsoft Teams is created using the Azure bot framework. We are using the Bot Framework SDK for Java from Microsoft.
Let’s take an example of a user sending a command such as “Book a seat for me for 9 am tomorrow”. Once the command lands on our backend, we use the Google “Dialogflow client library” for intent detection, as shown below.
In turn, the intent detection also calls our fulfillment webhook (originally written for the Google Assistant app). So the actual call for ‘Seat booking’ to the internal booking service happens via the Dialogflow fulfillment endpoint.
This is how the final interaction looks like for the end-user.
We can also pass additional metadata to the Dialogflow intent detection API, such as the logged-in user’s context ( shown in the example above), or indicate that the request is from ‘Teams backend’ if separate handling is required.
Another popular employee query to our Teams bot is “Where is John doe sitting?”, using the ‘@’ to mention the user.
In this case, we find out the users mentioned before we pass the command to Dialogflow. We use a ‘Microsoft Graphs’ API call to find more details about the user and map the user to the corresponding WorkInSync internal user.