Microsoft Teams and WhatsApp integration for your cloud phone system

What these integrations do, in plain terms

A cloud PBX holds your business phone numbers, extensions, call queues, IVR menus, voicemail and recordings. The Teams integration lets staff use those phone-system features from inside Microsoft Teams. The WhatsApp integration brings messages sent to your WhatsApp Business number into the same Linkus apps your staff use for calls, so the team can reply from one place instead of passing a single phone around.

Neither integration replaces planning. You still need to decide who answers which number, which staff should see which conversations, and what happens after hours. We help you map that first, then configure and test it.

Microsoft Teams: two ways to connect

Yeastar documents two different approaches for the P-Series Cloud Edition. They suit different situations, so it is worth choosing deliberately.

1. Linkus inside Teams (direct integration)

Each user installs the Yeastar Linkus for Teams app in their Teams client and signs in to the Linkus Web Client there. According to Yeastar, this method needs no middleware and no Teams calling licence. It works with common Microsoft 365 plans such as Business Basic, Business Standard, Business Premium and E3/E5, subject to the firmware and requirements Yeastar lists.

• Make and receive calls through the PBX from the Teams interface, using the Linkus web or desktop client, or a CTI-controlled desk phone.
• See call history inside Teams.
• Play and download voicemails and call recordings inside Teams.
• Single sign-on with a Microsoft account is possible when the PBX is connected to Microsoft Entra ID (Azure AD) and the hosting domain meets Yeastar's conditions; otherwise staff sign in with their extension account.

2. Yeastar for Microsoft Teams app (Teams as the phone)

In this method, Teams users are associated with PBX extensions so the Teams app itself behaves as a softphone registered to the PBX. Staff keep the PBX's IVR, queues and call routing while calling from native Teams. Yeastar lists extra requirements: a Yeastar for Microsoft Teams licence, and, for most Microsoft 365 plans, a Microsoft voice licence such as Teams Phone (Phone System), Common Area Phone or Business Voice, depending on your plan and country. Microsoft Teams dial plans also need a normalisation rule so users can call external numbers.

Because licence names and availability change, we check your current Microsoft 365 subscriptions with your IT administrator before recommending either method.

WhatsApp Business Platform: messages in the Linkus apps

Yeastar's omnichannel messaging lets agents receive and reply to WhatsApp messages in the Linkus UC clients, alongside SMS and internal team chat where configured. Messages can be routed to a message queue so the right group of staff sees them, and chat history stays with the conversation instead of on one person's phone.

This uses Meta's WhatsApp Business Platform (the API), not the standard WhatsApp Business app on a mobile phone. Based on Yeastar's setup guide, you will need:

1. A Meta Business portfolio (Business Manager) with business verification completed and a payment method added.
2. A Meta developer app with WhatsApp added, and a system user with a long-lived access token.
3. A phone number that is valid and available for WhatsApp messaging on the platform.
4. The WhatsApp channel configured on the PBX, with Meta's webhook pointed at it.
5. Approved message templates if you want to send business-initiated messages or campaigns.

We guide you through the Meta side and configure the PBX side. Meta account ownership stays with your business.

About Meta conversation fees

Meta charges for certain WhatsApp Business Platform messages, and its pricing rules change from time to time. Meta fees are separate from your LinkusPBX plan and are billed under your Meta account. We estimate them with you and include the assumptions in a written quotation after scoping your expected message types and volumes.

Which plan includes what?

Teams integration and WhatsApp messaging are available depending on plan. Yeastar's own marketplace lists WhatsApp integration for P-Series Enterprise plan or higher. LinkusPBX office packages start at SGD 39 per month for CP10 on an annual commitment, and call-centre packages (CPSC Enterprise and Ultimate) are priced by concurrent conversations. See prices and packages. We confirm in your quotation exactly which integrations are included, which need an add-on licence, and any setup work, which is quoted case by case.

A typical rollout

1. Scoping call. Which teams use Teams today, who answers WhatsApp, which numbers are involved, and your Microsoft 365 licences.
2. Design. Choose the Teams method, define message queues and after-hours handling, and agree a test list.
3. Meta and Microsoft preparation. Your administrators complete business verification, app permissions and any licence purchases.
4. Configuration and pilot. We configure the PBX, test with a small group, and adjust routing.
5. Rollout and handover. Short user guides, admin handover and a review after the first weeks.

Good questions to ask any provider

• Which Teams method are you proposing, and which Microsoft licences does it need?
• Who owns the Meta Business account and the WhatsApp number?
• Which staff or queues will see WhatsApp conversations, and how is history kept?
• Are Meta fees, add-on licences and setup shown separately in the quotation?

Switching from an existing phone system? We can review your current setup and show how Yeastar LinkusPBX would meet the same Teams and messaging requirement.