Full Teams Client API including Call Control
Microsoft Teams should have completed Client APIs so that third party apps can be created to fill specific needs.
This API should allow call control of the Microsoft Teams application. Necessary call control features include:
• dial/call
• call answer
• hang-up
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• mute/unmute
• park/unpark
• call as a delegate
Some general features include:
• search contacts
• get contact presence
• get contact list folders/contacts
• setup contact list folders/contacts
• get/set my presence
• get/set my note
• get/set my delegates
• get/set my Calling Groups
• Get/set my call forwarding
• get/set audio device
• get/set voicemail settings
Messaging
• get/send chat messages
• get/send voice/audio message
The above lists are not comprehensive but are to give an idea of the necessary features.
Also
The Teams Client API should be able to be used inside the Microsoft Teams client canvas or from a standalone application. Ideally, the application developer could decide if they want to access the above functionality by controlling the Microsoft Teams application, with the Teams app running alongside, or as a standalone application, without the Microsoft Teams application running.
We see this as part of achieving Skype for Business parity so ISV's can write applications like Attendant Consoles so organizations can move to Microsoft Teams.
Matt Landis
shared this idea
The team is reviewing possibilities in this space but does not yet have a date on this. We will update when there is news to share.
134 comments
-
SP
commented
This is a must for all third party integration especially Landis Attendant Pro
-
W M
commented
Reading through the comments below. It shows a very acute need for this, it seems to be blocking a lot of projects from moving forward.
-
Jiří Zídek commented
If MSFT want to gradually replace classical PBX, full CTI roadmap is absolutely necessary for business customers!
-
Anonymous
commented
Customers are asking for MS Business Voice but basic telephony features like CTI with CRM/ERP systems are missing.
Customers clearly say: Teams is no option if essentials still not available
This seems to be one of them...
Please allow third party ISVs to build at least a TAPI driver to make CTI work as with any other Cloud PBX -
Timothy Meredith
commented
In other words, MS's official response is that this functionality isn't important (to them).
-
Jason Emery
commented
This would be extremely helpful for on premise phone systems.
-
Jack Stephenson
commented
Microsoft > Please respond
You competition has comprehensive API's
Skype For Business had comprehensive API'sCan you explain why MS is now so hesitant to create an API for Teams?
Engage with the dev community.
Simply ignoring us is not a winning strategy.Help us understand your pint of view.
-
Herbert Dirry
commented
Please release API asap!!!
As support of SfB will end by end of 2020, we need an Attendant Console based on Teams to manage calls! -
Ben
commented
We are also waiting for 'Voicemail on Busy' which seems a pretty basic function!
-
Anonymous commented
We recently starting using Teams as our phone system for some of our associates and these are some of the pain points when working with 3rd party integration.
-
Lovey Kohler
commented
Today, in my office, we are about 350 users using Skype for Business On-Prem Telephony and are using a 3rd party app for the attendant console, which we would like to migrate to Teams telephony, so this would certainly help us.
-
Don Cameron
commented
I am very interested in this. Zoom, S4B, Accession, Bluejeans all have APIs. Teams only has bots & deeplinks - nothing for call control.
If we had a Teams API, we could get way more customers using Teams and Azure. However without the API, we are going with Zoom and Bluejeans.
-
Jack Stephenson
commented
Zoom has a full API, even more comprehensive from the list above.
Ironically, they even has a Dotnet version of the API.
This does not seem like it has hurt Zoom in the marketplace.MS also has a comprehensive API for Skype For Business.
This was actually a real reason many enterprises adopted Skype For Business.
Now we feel let down on the time we invested.Can you explain why MS is now so hesitant to create an API for Teams?
-
Timothy Meredith commented
This is why uservoice is a joke. MS Deflects all suggestions to uservoice, then when an idea makes it to top voted and goes unresponded to for 9 months, it finally gets a "eh we're reviewing possibilities we might do it eventually". FRUSTRATING
-
G
commented
Please add video to the Client API solution, not only voice
-
Frank Carius
commented
It would also open a way to enhance the usage of additional Keyboards (like elgato streamdeck and others) Looking forward an interface to talk to the electron teams client on the client.
-
Paul Martin
commented
Thank You @Alex. It is good to see an update, however the fact that this was not 'Under Review' a year and a half ago is absolutely mind blowing.
As our world faces this pandemic, thousands of companies are in desperate need of solutions that allow them to establish safe, WFH environments for all users. Frontline workers are in need of tools to allow them to manage communication efficiently, and manage hotlines well. Microsoft's relaxed and unhurried approach to addressing this is completely unacceptable. Do the right thing, and make this API release the #1 priority. -
Pascal
commented
Thank you @Alex for taking this "Under Review" this is very importat for our company. Take also a look at this tool: http://www.lyncwizard.com/products.html#TeamsWizard
-
Osman Sharif
commented
MS Teams to be a true enterprise solution for organisations then APIs being mentioned need to be released ASAP without delays.
-
Dieter Härle
commented
It is ridiculous that there is no reasonable CTI API available after such a long time. Have a look at Amazon Connect and you know what kind of API you should deliver.