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:
• call answer
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• 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
• 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.
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.
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.
@Alex any update on this?
Padraig McTiernan commented
@alex, we are partners or we are not. We just need some small crumb of a response. We deserve that. We all put in a lot of hard work making solutions compatible with your solutions, to our mutual benefit. Is the team still "reviewing possibilities", for example?
when can we expect any kind of feedback?
Is there any update on this?
As demonstrated by the number of comments below, a lot of companies require this to be released in order to meet the deadline imposed by Microsoft. The situation and silence on this thread by MS is farcical.
Alex - as noted in comments below - it has been 7-months since you last posted. Can we please get an update for this project at Microsoft - or if they have decided not to create API's for Teams at all. We need to plan for migrating from Skype to Teams in the very near future since Skype is due to EOL very soon. Please Advise - we're all waiting...
This really unacceptable.
A lot of third party tools "complete" Skype for Business because of the lack of an Attendant Console and other features that enterprise needs.
We also are using Landis Attendant Pro and we were planning on migrating towards Teams.
Seems that will be a no-go !!!
Paul C. commented
The lack of this functionality is causing many issues for us with many customers and is holding up major projects and causing financial implications as a result.
Please provide an update.
Paul Healy commented
30 weeks without an update - is there any news on this? Any update? Less than 6 months to SfB EOL and still no visibility of when this important API will become available.. if at all. This is basic, out of the box functionaility for pretty much every other voice platform. C'mon MS!
Our Unified Support Customers are requesting an urgent response on this topic. Skype for business online is being discontinued with a fixed date, and still no confirmed date for the Teams API that would allow third party apps to work natively with Teams. Many customers have their core calling systems depending on this technology and this is a serious risk.
Is this the API folks are waiting on to allow Teams and Salesforce to do call pop?
Is this the API folks are waiting on to allow Teams to do a Salesforce call pop?
Tommy Sciano commented
Almost a year later and still nothing ?
Rob van de Velde commented
We also use Attendant Console from Landis in the Netherlands but we can't integrate the attendant console with Teams client until you release the client API. Any updates?
Rory Donnelly commented
Alex, no update in over 6 months??? Given how critical this is, and because there is no guarantee that Microsoft can provide an API to 3rd party attendant console providers in time to implement it by July 31st, we now have to look at moving off the MS UC platform altogether. 8x8 (or actually just about any other provider) would give us everything we need here in the absence of a Teams Attendant Console. They can guarantee a migration from Teams by July 31st, but Microsoft can't provide ANY information to ANYONE on this. Doesn't bode well for the future of Teams at all. Sure, you can have emojis and pop-out windows, but forget about an attendant - the first point of contact for customers for a lot of companies. And don't even get me started on the lack of access to the Global Address Book in Teams...
But we'll save a fortune on downgrading all our Microsoft 365 licences from E5 and dumping all our MS calling plan licences.
Actually, maybe this is a blessing in disguise, forcing us to jump ship.
My organization has completed the migration to 'Teams Only' tenant mode. The current Teams compatible desktop telephones are not appropriate as Reception Consoles as the simple transfer process takes 7 steps and lots of manual dialing on a touch pad interface of names and numbers. We are currently using the Teams desktop client instead, which is a better user experience. Waiting on console options.
Hi, any update. With SfB nearing EOL. Would appreciate an estimated delivery date
Cosmin Leferman commented
We're also looking into this and it's weird it's not yet available. Any update?
Christian Zentgraf commented
an official update on this topic would be very much appreciated!
is there any progress Microsoft? This is currently a show stopper....... the barrier to entry for lots of opportunities!
Andre Hagmann commented
is there any progress from Microsoft for the Call Control API, as this is a key deployment blocker for customer, migrating from Cisco with Customer Date Integration.