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.
151 comments
-
Dejan
commented
Unfortunately I do not understand that microsoft does not have such essential features in mind and is working on them." Microsoft wants all Skype for Business customers to migrate to teams. However, without these functions, it will be difficult. "backlog" or "product group evaluates it" is also everywhere - also no meaningful feedback . I also dont understand that there is a working on features, which are not important for the business
-
Anonymous
commented
Direct integration to a Dynamics 365 based CRM would be nice as well. Screen pops, click to dial, automatically call logging, etc.
-
Timothy Meredith
commented
Very disappointing this is just now given even a “maybe we’ll think about it and do it in a few years if we feel like it” response. MS may as well tell people looking to replace skype for advanced calling situations to just look elsewhere.
-
Alex
commented
We are now shutting down Skype for Business integration (via Lync) and also looking forward for migration to Teams
-
Anonymous
commented
Please release the API asap!!! Many customers are looking to use Attendant Console to manage the calls better.
-
Joel Coash-Johnson
commented
Need and attendant console. Perhaps need to leave Teams voice if this cannot be implemented
-
David Bowen commented
One other thing which I hope has been suggested. Permissions should be delegate based and NOT application. Users decide if they can give their permission and not admins.
-
piqueora
commented
How is this even possible that a system considered as "advanced" and "rich" does not propose a full API for its access by applications ?
-
Mike Welch
commented
Our organization would find this very valuable. Please continue to develop and release as soon as possible! We have a new Salesforce implementation and would love to integrate with Teams as our inbound/outbound calling tool.
-
Anonymous
commented
It is very important to have this API for Teams.
-
Anonymous
commented
The ability to send digits post call establishment is needed along with audio recording and speech recognition as is available for UCMA today.
-
Wendell Martin
commented
Replying to Peter an Anonymous below. The Communication APIs will include call recording and are slowly being released, many features are in preview at this time. They do not include any call controls so far. the Client APIs are not in preview at this point yet. Ideal would be something to match the power of the Lync 2013 SDK.
-
Anonymous
commented
My understanding is that the API is ready but just not moving from Preview to Available for some reason (I guess priorities).
We have a lot of customers waiting for the compliant call recording
-
Peter Longley
commented
They have an API in Beta at the moment is my understanding as we use a call reporting system which is using it and the reports are getting better. I believe it is due by End of May but not sure what it is going to include.
-
Fabio
commented
A client side API like the the Lync 2013 SDK is really needed by our customers. Some are waiting with their migration until it can be delivered. Should also include subscribing to events (ringing, connected, terminated, directCall or Meeting).
Also a Web SDK would highly be appreciated, something similar like the UCWA, this would allow deeper integrations with Teams.
Thanks -
W M
commented
Lots of good comments here, I hope whoever controls the budget on development realizes how critical this is.
-
Michel van den Brink
commented
A full client API like Skype for Business is essential for our company and many of the customers we service. Without such an API we'd unable to log all calls incoming/outgoing, who's calling and route calls efficiently within the service departments.
We've been using the Lync 2013 SDK combined with Skype for Business for many years, switching to Teams is not an option without these features!
-
Don Cameron
commented
Zoom, Webex Teams, BLueJeans and Skype for Business all have a full client control API. If Micrusoft want to continue selling Azure and MS Teams bandwidth, a client API is needed, otherwise there will be other options.
-
Anonymous
commented
Efficiencies will improve tremendously in our company once this is released. We've been ready for months to move forward with greater Teams integration internally and this is the missing link! Can't happen soon enough from our user perspective.
-
Anonymous
commented
Efficiencies will improve tremendously in our company once this is released. We've been ready for months to move forward with greater Teams integration internally and this is the missing link! Can't happen soon enough from our user perspective.