Yeastar CRM and Microsoft Teams integration: what is possible

The short answer: a Yeastar P-Series phone system can talk to the main CRMs on the market and to Microsoft Teams, provided you have the right feature plan. Yeastar publishes official integrations for many CRMs, including HubSpot, Salesforce, Zoho, Odoo, Bitrix24 and Microsoft Dynamics 365, for several helpdesk tools, and for Microsoft Teams without a Teams Phone licence. These integrations generally require the Enterprise or Ultimate plan. The most common trap is not on the phone system side but on the CRM side: each integration has its own edition and hosting prerequisites.

As a Yeastar certified partner and Microsoft partner in Casablanca, we set up these integrations across Morocco. This guide only lists what Yeastar documents on yeastar.com and help.yeastar.com. For models and plans in general, see Yeastar P-Series: which model to choose.

What a CRM integration brings

Connecting the phone system to the CRM means every call is linked to the right customer without manual entry. Depending on the CRM, Yeastar documents the following features:

• Click to call: one click on a number in the CRM places the call from the user’s extension. For some web integrations, this goes through the Linkus Chrome extension paired with the Linkus web client.
• Contact pop-up on inbound calls: the CRM opens the caller’s record. Yeastar states that the user must be signed in to the Linkus desktop or web client.
• Call journal: inbound, outbound and missed calls logged automatically in the CRM, with subject and description templates set in the phone system portal.
• Contact synchronisation and automatic creation of contacts for unknown numbers.

For a sales or customer service team, the value is twofold: the interaction history is complete, and the manager has reliable data on handled and missed calls. These features complement the reception design described in queues, IVR and statistics.

Official integrations listed by Yeastar

Family	Yeastar-built integrations
CRM	Zoho CRM, Zoho Bigin, Pipedrive, Bullhorn, HaloCRM, Maximizer, SugarCRM, Teamleader, HubSpot, Salesforce, Bitrix24, Odoo, Microsoft Dynamics 365
Helpdesk	Zendesk, Zoho Desk, ConnectWise, HaloPSA
Microsoft	Microsoft Teams, Yeastar for Teams Desktop plugin, Outlook, Microsoft 365, Microsoft Exchange, Microsoft Entra ID (Azure AD), Active Directory
Google	Linkus extension for Chrome, Google Calendar, Google Workspace, Google SSO sign-in
Messaging	WhatsApp, SMS, Facebook Messenger
Other CRMs	Custom CRM Integration Template

Source: App Marketplace and P-Series page on yeastar.com. The marketplace also lists third-party partner apps, including Call2Teams for Microsoft Teams and several call billing tools.

The custom integration template deserves a mention: it can connect a CRM missing from the list, including one developed in-house, provided it exposes a compatible API. That is a project in its own right, which we scope after reviewing your tool’s API.

Which plan for which integration?

Integration	Required Yeastar plan	Source
HubSpot, Salesforce, Zoho CRM (Appliance)	Enterprise or Ultimate	Each CRM’s integration guide, help.yeastar.com
Odoo (Appliance)	Enterprise or Ultimate	Odoo integration guide
Microsoft Teams, direct integration (Appliance)	Enterprise or Ultimate	Yeastar for Microsoft Teams page
CRM, helpdesk and Microsoft 365 integrations	Enterprise and above	P-Series plan comparison
Active Directory	Ultimate	P-Series plan comparison
Call2Teams (third-party app)	All plans, plus a Call2Teams licence	Yeastar App Marketplace

A useful reminder: the Software and Cloud editions only offer the Enterprise and Ultimate plans, which settles the question. On the Appliance edition, the Standard plan covers telephony and Linkus, but not these integrations. Each guide also sets a minimum firmware version: we check it before starting.

CRM-side prerequisites: the Odoo example

Odoo is widely used by Moroccan SMBs, and it is the example that best shows why prerequisites matter. Yeastar’s official Odoo integration guide requires:

• Odoo Online hosting;
• Odoo Enterprise edition;
• version 14.0 or later;
• an administrator account for the Odoo database.

In practice, a business running Odoo Community, or Odoo installed on its own servers, falls outside the documented scope of the official integration. Better to know that before buying the Enterprise plan for that reason alone. If your Odoo project is under way, see our guide Odoo for Moroccan SMBs to factor this into the choice of edition and hosting.

Other CRMs also have conditions, published in each Yeastar guide: for example Salesforce Enterprise, Unlimited, Developer or Performance editions; for HubSpot, a Super Admin account for authorisation; for Zoho, an administrator to enable the integration and a phone system reachable by domain name. Remote Access Service and the Yeastar FQDN are often needed, since a cloud-hosted CRM must be able to talk to the phone system.

Microsoft Teams: three approaches not to confuse

Approach	Principle	Licences
Direct integration, Linkus for Teams	The Linkus app is embedded in Teams; users call and access history, voicemail and recordings without leaving Teams	Eligible Microsoft 365, no Teams Phone licence; Enterprise or Ultimate plan on Appliance
Call2Teams	Third-party service that makes Teams a phone registered to the phone system	Call2Teams licence plus a Microsoft telephony licence (Teams Phone, Common Area Phone or E5)
Direct Routing on your own	SBC and Microsoft configuration handled by the business	Teams Phone licences, an SBC to run

The direct integration is the one Yeastar promotes. Eligible Microsoft 365 subscriptions are Business Basic, Business Standard, Business Premium, E3, E5 and Office E1, E3, E5; we help you choose in Microsoft 365 Business Basic, Standard or Premium. Each user installs Linkus for Teams from the Microsoft store and signs in with their extension or Microsoft account. Calls then go through the Yeastar for Teams Desktop plugin or a controlled endpoint: Linkus web or desktop client, or desk phone.

Going further, the Microsoft Entra ID integration syncs users and groups, can create extensions automatically, and syncs Teams contacts and presence with the phone system. The Outlook integration adds click to call and call logs in Outlook.

If your business is torn between keeping a Yeastar system integrated with Teams and moving fully to Teams Phone, our comparison 3CX, Yeastar or Teams Phone sets out the criteria.

Helpdesk and customer service: a separate case

For a support team, the point is not only to find the customer record: it is to link the call to the ticket. Yeastar documents integrations with Zendesk and Zoho Desk, as well as ConnectWise and HaloPSA, two tools widely used by IT service providers. Depending on the tool, the call can open the requester’s record and be logged in their history.

These integrations make the most sense alongside the Enterprise plan’s call centre features: supervised queues, wallboard, callback. If your need extends to a multichannel contact centre with high call volumes, also compare with the approach described in call centre with 3CX in Morocco: we recommend the solution that fits your processes, not a brand on principle.

An integration project in practice

1. Map the flows: which teams call out, which receive calls, what information must be visible on answer and recorded after the call.
2. Check prerequisites on both sides: CRM edition and hosting, Yeastar plan, firmware version, administrator access, Remote Access Service.
3. Clean the data: international number format, duplicates, contacts without a company.
4. Configure for a pilot group: a few users, with Linkus desktop or web and the Chrome extension where needed.
5. Test real cases: inbound call from a known customer, from an unknown number, missed call in a queue, transfer between colleagues, outbound call from the CRM.
6. Roll out and train: every user should know where to find the call journal and what to do when a record does not open.

Mistakes we fix

1. Buying the Standard plan while counting on CRM integration: it requires Enterprise or Ultimate.
2. Promising the Odoo integration to a business on Odoo Community or self-hosted, outside the official scope.
3. Confusing direct integration with Call2Teams, and budgeting unnecessary Microsoft telephony licences, or the reverse.
4. Forgetting that the contact pop-up works through Linkus: a user who closes the web client no longer gets pop-ups.
5. Opening the phone system to the internet so the cloud CRM can reach it, instead of using Remote Access Service.
6. Starting the integration without cleaning the CRM: badly formatted numbers, duplicates, contacts without country code, and calls do not match the right customer.

Checklist before buying a plan for an integration

• The CRM or helpdesk is on Yeastar’s official list, or its API is compatible with the custom integration template.
• The CRM edition and hosting match the prerequisites in Yeastar’s guide (typical case: Odoo Online, Enterprise edition).
• A CRM administrator account is available to authorise the integration.
• The Yeastar plan is Enterprise or Ultimate, and the firmware meets the stated minimum version.
• Remote Access Service and the Yeastar FQDN are active if the CRM is cloud-hosted.
• The users concerned have Linkus desktop or web, plus the Chrome extension if click to call depends on it.
• For Teams: an eligible Microsoft 365 subscription for each user, and a firm choice between direct integration and Call2Teams.
• CRM data is clean: numbers in international format, duplicates merged.

How we work

We start from your processes: who calls whom, which information must flow into the CRM, which indicators to track. We check prerequisites on both sides, phone system and CRM, before any plan purchase, then configure the integration, test inbound, outbound and missed calls, and train the teams. The phone system and its integrations are then monitored 24/7, and a critical incident is handled in under 15 minutes.

See our IP telephony in Morocco offering and our guide to Yeastar Linkus, the foundation for most of these integrations. Want to connect your phone system to your CRM or to Teams? Request your free phone system audit: we reply within 24 business hours with prerequisites validated for your case.