Preview · This help is still growing and will be extended over time.
How integrations work
Which systems echo can search and how echo looks up a caller
An integration connects echo to a system that holds information about your contacts: your Microsoft 365 tenant, a public directory, your ERP or CRM, or your own system. When a call comes in, echo searches all active integrations for the caller's phone number and shows the result in the contact cockpit. The same integrations are used when you search for a contact in echo by name or email address.
This page is for administrators. It explains which integrations exist, what each one contributes, how the search works and how you add or remove integrations. The setup of each integration is described on its own page (see All integration guides).
Available integrations
Microsoft 365 is the base integration and is always active. All others are optional and can be combined.
Organization-wide means an administrator enters the connection once and it applies to all users. With a personal connection, each user signs in with their own account for that system under Settings → My accounts; until they do, echo does not search that integration for them. Each user then sees only the data their own account may access.
How echo looks up a caller
- The phone number is normalized. echo reads the caller's number in international format. Numbers without a country code are interpreted with your organization's region (see Default phone number region).
- All active integrations are searched in parallel. An integration takes part only if it has been added, is configured and – for personal connections – the user is connected. Integrations that do not meet these conditions are skipped without an error.
- Matches are merged. If several integrations return the same person or company – a similar name and the same phone number or email address – echo shows them as one contact with the details from all integrations. People are only merged with people, companies with companies.
- Results are sorted. Contacts found in more integrations come first, then people before companies, then alphabetically.
When an integration does not respond
- An expired personal connection (e.g. the user's Bexio or Pipedrive sign-in is no longer valid) is skipped. The caller is still looked up in all other integrations. The user reconnects under Settings → My accounts.
- Other errors – for example an unreachable server, an invalid API key or an endpoint that answers with an error – can make the whole lookup fail instead of returning results from the remaining integrations. If callers are suddenly no longer recognized, first check the integrations you added or changed most recently.
The activity timeline of a contact works differently: an integration that denies access (missing permissions or licenses) is left out, and the other integrations still contribute their entries.
Add or remove integrations
Integrations are managed under Settings → Integrations, in the Organization group of the settings menu. Only administrators see this group. Other users find the names of their administrators at the bottom of Settings → My accounts.
The list shows the integrations you added. Click an integration 1 to open its settings. The hint 2 Not configured shows that required settings are still missing; echo does not search this integration until they are filled in.
Add an integration
Click 3 Add integration. A catalog opens, grouped into Directory, Business Systems and Custom Integration. Use Search integrations to filter it, then click the integration you want. echo adds it and opens its settings page right away.
Configure it
Enter the connection details on the integration's settings page and save. The guide for each integration describes the fields. You can open the settings again at any time from the list.
For integrations with a personal connection, tell your users to connect their own account under Settings → My accounts. The integration's settings page shows the same hint under Personal settings.
Remove an integration
Open the integration's settings page and scroll to Remove integration. Click the button with the integration's name (e.g. Remove Abacus) and confirm with Remove. echo stops searching this integration immediately; you can add it again at any time. Microsoft 365 is required and cannot be removed.
Availability
- Activated per organization: Dynamics 365, Bexio, Pipedrive, CMI, ActiveCampaign, Exxas and the Custom Integration appear in the catalog only when they are activated for your organization. If you miss one, contact echo support (opens in a new tab).
- Plans: the Basic plan covers contact resolution and caller identification. The Advanced plan adds further insights from your CRM/ERP and more. See Subscription.
- Administrators only: adding, configuring and removing integrations, and every organization-wide connection. Personal connections are made by each user under Settings → My accounts.