Voice · Add-on to PBX Connector

Calling in Teams. No Phone System licenses.

A brandable add-on to PBX Connector, built on Microsoft Azure Communication Services. It brings your PBX, UCaaS or CCaaS into Teams.

Book a demo → Start a proof of concept

Free 30-day proof of concept for service providers.

500+ partners in 25+ countriesMicrosoft ISV Partner · Microsoft Certified for Co-sell100% Microsoft Azure based, 9 geographic regions

Illustration: the Acme Voice calling app open in its own Microsoft Teams window, with dial pad, call history and call details, next to the Acme Voice mobile dialer on a phone.

Your brand in Teams

Built on Azure Communication Services.

Fully brandable, and built on Microsoft's ACS Calling SDK for voice and video calls federated with Teams.

No Phone System licenses

Calls run on Azure Communication Services APIs, so users don't need Microsoft Phone System licenses.

PBX, UCaaS or CCaaS

Connect systems such as Avaya, Mitel or Dialpad to Teams in minutes.

Chat and SMS in one app

TeamMate chat and SMS connectors are unified in the ACS Call App.

Federated meetings

External PBX, UCaaS and CCaaS users join Teams meetings with video, audio and chat.

External call control

Server-side call queues, transfers and IVR, built for contact centers.

No Direct Routing needed

No Direct Routing or Teams Phone resource accounts, so there's less to set up and maintain.

Scales on Azure

Global scale on Azure, with Microsoft Entra authentication, encryption and data residency compliance.

In step with Microsoft

Built on ACS APIs in line with Microsoft's Graph API rules, and kept current through ACS SDK updates.

Mobile app

Calls follow your users to their phone.

A companion app to the Microsoft Teams mobile client, for iOS and Android.

Companion to Teams mobile

Works alongside the Microsoft Teams app on iOS and Android.

Built on the ACS Calling SDK

Users sign in with their Microsoft 365 account, so your customers' security policies, including multi-factor sign-in and conditional access, apply automatically.

Carried by Azure Communication Services

Voice and signaling run on Microsoft Azure Communication Services, so calls benefit from the infrastructure behind Teams call quality and ease of use.

Your business number, anywhere

Make and receive work calls on Wi-Fi or mobile data, with your business number as caller ID. No Microsoft Phone System license needed.

ACS Call App on a phone: the dialer with keypad, work number, and Contacts, History, SMS and Settings tabs

Value

More for your customers. Less work for you.

What your customers get

Calling inside Teams, with no Microsoft Phone System licenses.
Inbound call alerts as Teams notifications.
Chat and SMS with non-Teams colleagues from one app.
External callers joining Teams meetings as native participants.

What you get

A fully brandable Teams app, as an add-on to your PBX Connector service.
No Direct Routing or resource accounts to manage.
PBX, UCaaS and CCaaS platforms connected to Teams.
Global scale on Microsoft Azure.

FAQ

ACS Call App questions.

Do I need PBX Connector?

Yes. ACS Call App is an add-on to PBX Connector. About PBX Connector →

Do users need Microsoft Phone System licenses?

No. The ACS Call App uses Azure Communication Services APIs, not Phone System licenses.

Is Direct Routing required?

No. Direct Routing and Teams Phone resource accounts aren't needed.

Which systems can it connect?

External PBX (for example Avaya or Mitel), UCaaS (for example Dialpad) and CCaaS platforms.

Can I brand it?

Yes. The ACS Call App is fully brandable.

What changed from the earlier call app?

Released in TeamMate version 2.18, it runs on ACS APIs only, so it no longer relies on Microsoft Graph API transfer bots.

Add calling to Teams, with your brand.

See the ACS Call App in a live demo, or start a proof of concept.

Book a demo →Start a proof of concept

Free 30-day proof of concept for service providers.