Preview
echo for Microsoft Teams
Administrator handbook

Installation and configuration guide

Part 1 – Initial setup for administrators

Product: echo for TeamsUpdated: June 2026Version: 1.0
💡 This guide is optimized for PDF export. Print → “Save as PDF”, enable background graphics.

1 · Initial setup

This part is aimed at administrators and describes the one-time initial setup of echo in your Microsoft 365 environment. Setup takes place in two phases: first the echo app is added to Microsoft Teams (see the separate guide, linked under the prerequisites), then the onboarding wizard is completed. Once finished, echo is ready for organization-wide use and individual users can use the app.

Prerequisites

Before you start, make sure the following prerequisites are met:

PrerequisiteDescription
Access to Microsoft TeamsA Microsoft 365 account with access to Microsoft Teams (desktop, web or mobile app).
Right to add the appEither the echo app is approved for installation in your organization (self-installation via the App Store) or you have the Teams Administrator role for central distribution via the Teams Admin Center. The exact procedure is described in the guide linked below this table.
Tenant administrationFor the onboarding wizard you need administrator rights on your Microsoft 365 tenant in order to grant the required permissions organization-wide (admin consent).
Data sourcesCredentials for the systems to be connected (e.g. CMI: API, STS and portal URL).
Windows clientA software distribution tool or access to the client computers in order to distribute the echo Windows client (required for caller identification).

First step: Add the echo app to Microsoft Teams. You can find the step-by-step guide for both ways (Teams App Store and Teams Admin Center) here:

TAdd echo to Microsoft Teams · echo-Add-to-TeamsOption A: self-installation via the Teams App Store · Option B: central distribution via the Teams Admin Center.→
NoteAdding the app alone does not complete the setup. The actual onboarding wizard (see below), including admin consent, must then be completed by a tenant administrator.

Run the onboarding

Good to knowOnboarding is built as a guided wizard (“Let’s set things up!”). The progress bar on the left always shows where you are. Completed steps are marked with a green checkmark.
1

Start onboarding

Open echo in Microsoft Teams. After adding the app, the start screen “Let’s set things up!” appears. echo points out that the application is not yet fully set up.

As an administrator, under “Are you an administrator?” click “The configuration can be completed here” to start the setup wizard.

Start screen. The administrator starts the configuration via the button.
Fig. 1: Start screen. The administrator starts the configuration via the button.
ImportantCompleting onboarding requires tenant administration rights. Without this permission, admin consent (step 3) cannot be granted.
2

Select data sources

Select the data sources you want to connect to echo. echo uses these sources to show matching contact information for incoming calls. The options include:

  • Microsoft 365 – people, emails, calendar entries and files from your Microsoft 365 account (required).
  • Directory (search.ch) – public directory for contact information of individuals and companies in Switzerland.
  • Business systems – ERP/CRM integrations such as ABACUS, Dynamics 365, bexio, Pipedrive or CMI.
  • Custom data source – connect any external data source via an HTTP API.

Activate the desired sources by clicking the respective tile.

Selecting the data sources. Microsoft 365 is mandatory; other sources are optional.
Fig. 2: Selecting the data sources. Microsoft 365 is mandatory; other sources are optional.
NoteDepending on the selected data source, additional configuration steps appear later (e.g. the connection details for CMI in step 4).
3

Grant Microsoft 365 permissions (admin consent)

In order for echo to show personalized information about callers, it needs access to certain Microsoft 365 data. Consent must be given with an administrator account and then applies to the entire organization.

echo accesses the following data:

  • Profile and contacts to identify callers
  • Calendar events to display relevant appointments and meetings
  • Files and documents related to contacts and appointments
  • Email information for the context of your communication
  • Call logs to display call information

Click “Grant Microsoft 365 permissions”.

Overview of the requested permissions before admin consent.
Fig. 3: Overview of the requested permissions before admin consent.

You are redirected to the Microsoft sign-in page. Sign in with your administrator account and review the requested permissions. echo needs this access in order to display contact information for incoming calls. Confirm with “Accept”.

Microsoft consent dialog. With “Accept”, admin consent is granted for the entire organization.
Fig. 4: Microsoft consent dialog. With “Accept”, admin consent is granted for the entire organization.
ImportantConsent applies to all users in the organization and can only be granted by an administrator. The permissions can be viewed and adjusted at any time later in the Microsoft Entra Admin Center under Enterprise Applications.
4

Configure data sources

Depending on which data sources you selected in step 2, they must now be configured with the respective connection details. The settings are available at any time later under Settings → Data sources.

For the following data sources you will find a dedicated step-by-step guide:

AConfigure Abacus · echo-Data-source-AbacusTenant connection (organization-wide) and user connection including the required API scopes.→CConfigure CMI · echo-Data-source-CMIEntering the API, STS and portal URL to connect your CMI cloud environment.→
NoteOther data sources (e.g. Microsoft 365, search.ch, Dynamics 365, bexio, Pipedrive) are configured directly during onboarding or under Settings → Data sources. Dedicated guides for these will follow.
5

Telephony integration: live caller identification & Windows client

Live caller identification shows you a caller’s contact details in an additional window – even before you answer the call. For echo to display this information before a call is answered, a client application is required that must be installed on all computers that use echo.

The “Live caller identification” step. Via “Configure now” you reach the client download.
Fig. 5: The “Live caller identification” step. Via “Configure now” you reach the client download.
Platform availabilityThe client application is currently only available for Windows. A version for macOS is in the alpha phase and in progress.

Distribute the Windows client – step by step

  1. Download the application – Download the echo Windows client via “Download echo for Windows”.
  2. Install & sign in – Start the application and sign in with your Microsoft account.
  3. Caller identification becomes active – On an incoming call, the additional window with the caller information is shown.
  4. Distribute to all clients – Distribute the application to all computers that should use echo.
Download and distribution notes for the Windows client.
Fig. 6: Download and distribution notes for the Windows client.
Distributing the applicationThe application can be rolled out via a software distribution tool or alternatively installed manually on each client. After installation, each user must sign in once with their Microsoft account. After that the application runs in the background and starts automatically when the computer restarts.

If telephony integration is not relevant at this time, you can skip the step via “Skip” and catch up later.

6

Manage administrators

In the User management step you define which users may access echo as an administrator. Administrators can configure data sources, manage the subscription and add more users.

Your own account is already entered as an administrator. Via “Add more administrators” you add additional people.

Managing administrators. Additional people with management rights can be added here.
Fig. 7: Managing administrators. Additional people with management rights can be added here.
RecommendationAdd at least two administrators so that management is guaranteed at all times, even if someone is absent or leaves.
7

Complete setup

Once all steps are completed, echo confirms the successful setup. All items in the progress bar are now marked with a green checkmark. echo is now ready for use.

Click “Start echo” to reach the dashboard.

Completion screen. The setup is complete – echo is ready for use.
Fig. 8: Completion screen. The setup is complete – echo is ready for use.

What’s next?

The organization-wide initial setup is now complete. The following parts of this documentation will cover:

These sections will follow in the next parts of the documentation.