Preview · This help is still growing and will be extended over time.

Settings · Administrator

Telephony integration

Live caller recognition, the calling extension and the telephony options for your organization

Updated: November 2026

The telephony integration connects echo with phone calls in Teams. It covers two ways of showing caller information and a few options that decide when echo opens by itself.

The settings menu has a Telephony Integration page in each group: one under Personal for every user, and one under Organization for administrators.

Fig. 1: The two Telephony Integration pages in the settings menu, as an administrator sees it.
PagePanelsApplies to
1 Personal → Telephony IntegrationLive caller recognition (download of the echo desktop app) and User Settings (whether echo opens automatically on calls)The signed-in user and their computer
2 Organization → Telephony IntegrationInformation in calling window (registers echo as a calling extension in your Teams tenant) and Tenant Settings (organization defaults for opening echo, and the default phone number region)The whole organization

Only echo administrators see the Organization page. The calling extension also needs the Teams Administrator role in Microsoft 365, because it changes your Teams tenant.

During the setup wizard, live caller recognition and the calling extension appear as the wizard steps 2.1 and 2.2, see Initial setup.

Live caller recognition

With live caller recognition, echo shows a popup with the caller's contact details next to the Teams call notification, before the call is answered, and opens echo as soon as the call is accepted. It works for calls from and to regular phone numbers (PSTN), not for calls between Teams users.

Fig. 2: Live caller recognition with the echo desktop app.

This requires the echo desktop app for Windows or macOS on every computer that uses echo. The Live caller recognition panel under Settings → Personal → Telephony Integration offers Download echo for both. After the installation, every user signs in once with their Microsoft account; the app then runs in the background and starts automatically.

Calling extension (information in the calling window)

echo can also show caller information inside the Teams calling window. For this, echo must be pinned on an app setup policy of your Teams tenant. This is done once and applies to everyone the policy is assigned to.

Open Settings → Organization → Telephony Integration. In the Information in calling window panel, click Setup now and choose one of the two tabs:

Automatic setup – echo pins itself on the policies you choose.

  1. If echo has not been granted the setup permission yet, click Grant permission and confirm in the Microsoft window. The permission is only needed for this configuration.
  2. echo lists the app setup policies of your tenant with their Status. Click Register echo on this policy for each policy echo should be pinned on (Remove echo from this policy undoes it).

You need the Teams Administrator role in Microsoft 365. Without it, echo shows Teams Administrator Role Required. echo can be pinned on the Global policy and on custom policies, not on Microsoft's other built-in policies.

Manual setup – you make the change in Microsoft Teams yourself:

  1. Open the Microsoft Teams admin center (opens in a new tab) and go to Teams apps → Setup policies.
  2. Select the policy you want to change.
  3. Add echo to the pinned apps and save.
Good to knowChanges to app setup policies are applied by Microsoft Teams and can take some time to reach all users.

Open echo automatically on calls

When a call is accepted (incoming) or started (outgoing), the echo desktop app can open echo in Teams with the other party's number, so the contact cockpit is ready right away. Two settings control this, one for incoming and one for outgoing calls. They only have an effect on computers with the echo desktop app, and only for calls to and from phone numbers. The macOS app currently only opens echo for incoming calls.

Tenant Settings (administrators)

In the Tenant Settings panel under Settings → Organization → Telephony Integration you decide for the whole organization:

Fig. 3: The Tenant Settings panel. Only administrators see it.

Click Save to apply the changes.

How the two settings work together:

Allow users to change this settingWhat applies to a user
OnThe user's own choice in User Settings. Users who never changed it have it switched on.
OffThe organization setting. In User Settings the option is greyed out with This setting is managed by your administrator.

Until an administrator saves the panel for the first time, all four options are switched on.

Default phone number region tells echo how to read numbers without a country code. It applies to the whole organization and is explained in Default phone number region.

User Settings (every user)

In the User Settings panel under Settings → Personal → Telephony Integration, each user switches Open echo automatically on incoming calls and on outgoing calls on or off for themselves and clicks Save, as long as the administrator allows it. More on the personal options in Personal settings.

Troubleshooting

No popup appears on incoming calls. Check that the echo desktop app is installed and signed in on that computer, and that the call comes from a phone number, not from a Teams user. On a Mac, check that echo is allowed under Privacy & Security → Accessibility. For the Windows app, see Deploy the Windows client.

echo does not open when a call is accepted. Check User Settings under Personal → Telephony Integration on that user's account. If the option is greyed out, it is set in Tenant Settings under Organization → Telephony Integration.

A user's option is greyed out. Allow users to change this setting is switched off in Tenant Settings. Only an administrator can change it.

Automatic setup shows “Teams Administrator Role Required”. Your Microsoft 365 account lacks the Teams Administrator role. Ask your Microsoft 365 administrator to assign it, or use Manual setup.

A policy can't be switched on. echo can't be pinned on Microsoft's built-in policies other than Global. Use Global or a custom policy.

Saving a policy fails. Try again, or make the change with Manual setup in the Microsoft Teams admin center.