Put your NetSapiens calling on the Teams dial pad, under your own brand. Teams users register to NetSapiens, sign in to the NetSapiens portal from Teams, and stay in sync.
Free 30-day proof of concept for service providers.
It connects NetSapiens to Microsoft Teams so your customers can handle their NetSapiens calls without leaving Teams. TeamMate does this with PBX Connector: each Teams user registers to NetSapiens, and TeamMate uses the NetSapiens API to set up users and devices, automates the Direct Routing link and supplies the session border controllers. It works with NetSapiens-based services such as Crexendo, RingLogix, United Cloud and Viirtue.
Teams Calls becomes a softphone on NetSapiens, using the user’s NetSapiens number or extension, on desktop, browser and mobile.
Hold, transfer and voicemail still run on NetSapiens. Custom soft keys put the NetSapiens functions you choose one tap away.
New NetSapiens voicemail notifications arrive in Teams, so messages are not missed away from the desk phone.
On a NetSapiens call, Teams shows On a Call automatically. Presence Pause stops calls ringing through to Teams during meetings.
Transfer a NetSapiens call to anyone in Teams, with the transfer reported back to NetSapiens. How Pro Transfer works
Show caller details from your CRM or other systems as a card in Teams before the call is answered.
Users open the NetSapiens portal from Teams without signing in again.
Pre-fill and lock the NetSapiens API settings for your customers, so their admins have nothing technical to enter.
When a user is unavailable in Teams, NetSapiens can treat their Teams device as busy, or set the user to Do Not Disturb.
Keep NetSapiens contacts in step with Teams. About Contact Sync
Add an AI agent that lives in the NetSapiens portal. AI Voice Agents for NetSapiens
Take users’ SIP details from your provisioning server, tested with NetSapiens and Crexendo.
Add your branding and, if you like, an API credential template so customers do not have to enter NetSapiens settings.
Enter the NetSapiens API and single sign-on details, then add users one by one or in bulk. TeamMate builds the Direct Routing link.
NetSapiens calls ring in Teams on desktop, browser and mobile, with the NetSapiens portal one click away.
Most NetSapiens and Teams integrations use one of three approaches. They differ in where the call is answered and how many NetSapiens features come along.
A Teams app opens a separate NetSapiens softphone. Calls move out of Teams, and you support a second client on every desktop.
NetSapiens also rings a separate Teams number. Calls are answered in Teams, but NetSapiens features are lost and each user needs an extra number or trunk.
Each Teams user registers to NetSapiens like any SIP phone. Calls are answered in Teams with NetSapiens features kept and no extra number per user.
TeamMate also connects Mitel, 3CX, BroadWorks, Metaswitch, Avaya, Cisco to Microsoft Teams, along with 80+ PBX types and variants tested with PBX Connector.
Yes. TeamMate PBX Connector registers each Teams user to NetSapiens, so NetSapiens calls ring on the Teams dial pad on desktop, browser and mobile, with NetSapiens features and voicemail.
Yes. These services run on NetSapiens, and TeamMate supports them with the same integration.
An API client ID and secret with a NetSapiens user of at least Office Manager scope, used to set up users and devices. A second set is used for single sign-on to the NetSapiens portal. Service providers can supply both in a template.
Yes. Single sign-on opens the NetSapiens portal from Teams without a second sign-in.
Yes. When a user is unavailable in Teams, NetSapiens can treat their Teams device as busy, which affects only Teams, or set the user to Do Not Disturb on all their devices.
With PBX Connector, yes, as with any Direct Routing setup. If you would rather not buy Teams Phone licenses, the ACS Call App add-on lets users make and take calls in Teams without them.
Yes. Service providers get a white-label portal and a Teams app with their own name and logo, and can provision customers in the portal or through a REST API. With Bespoke Access, customers can even complete Microsoft setup inside your own portal.
It is priced per user, per month. Service providers can start with a free 30-day proof of concept on their own system.
See it in a live demo, or start a proof of concept on your own NetSapiens system.
Free 30-day proof of concept for service providers.