A headset-wearing support agent works at dual monitors in a modern office with cloud communications graphics.
Luware wants Microsoft Teams Phone to keep doing the telephony without making every contact centre agent work inside the Teams app. The Swiss vendor has announced the Luware NimbusOne client, a dedicated agent workspace for its Nimbus contact centre platform. It also says Microsoft has certified Nimbus for Unify, the Teams integration model that NimbusOne depends on.

This isn't a new contact centre platform. Luware says routing, workflows, reporting, administration and governance all stay on Nimbus. What changes is where the agent works: a full-size web client, a local application, or a compact CTI panel embedded in Salesforce or Microsoft Dynamics 365.

What Luware is shipping​

Luware calls the idea "client of choice." Staff who are well served by Teams keep using Nimbus inside Teams. Agents with specialist needs move to NimbusOne. Luware gives three examples:

  • CRM-first sales and service teams that spend the day in Dynamics 365 or Salesforce and rarely open Teams. They get the compact CTI inside the CRM and still call on the company's Teams Phone numbers.
  • High-volume support or citizen-service lines that need queues, transfers that check who is free, and after-call work in a full-size client.
  • Browser- or application-based roles whose main workspace is a business app.

Luware lists these features:

  • Call controls: accept, decline, hold, resume, and blind, safe and consultation transfers.
  • Service transfers that show which agents are available.
  • Outbound calls, placed directly or on behalf of a service.
  • Access to after-call work, past sessions and incomplete sessions from the same workspace.
  • Salesforce integration through Open CTI, and Dynamics 365 integration through its embedding framework. In both cases call context appears on the customer record.
  • Other business apps can be embedded as "context apps."
  • Multiple languages, keyboard shortcuts and WCAG 2.1 accessibility. Luware doesn't say which conformance level or how it was tested.

The product page also says calls, email, SMS, WhatsApp and Luware's Interact channel can all land in one queue. Check licensing before assuming every deployment gets all of those.

Section summary: NimbusOne is a new agent interface on the existing Nimbus platform. It runs as a web client, a desktop app, or an embedded CRM panel, and Teams stays available for staff who prefer it.

Unify, Extend and Connect in brief​

Microsoft gives Teams contact centre vendors three ways to integrate:

ModelFoundationWhere agents work
UnifyTeams Phone extensibility and Azure Communication ServicesThe vendor's own app, built on ACS calling SDKs
ExtendTeams client platform and Microsoft Graph APIsInside the Teams client
ConnectCertified session border controllers (SBCs) and Direct RoutingThe vendor's platform, connected through SBCs

Luware's help documentation states the trade-off plainly. Luware Nimbus supports the two deepest of Microsoft's integration models for bringing a Contact Center as a Service (CCaaS) solution to Teams Phone: Extend and Unify. Luware pitches Unify for organizations with high-volume interactions that need dedicated customer engagement experiences, CRM-centric workflows or advanced real-time AI.

A practical guide from UK integrator SCC explains why Unify matters. With Unify, the contact centre becomes independent of the Teams client and no longer relies on Teams communication APIs but can still leverage PSTN connectivity setup in Teams through Teams Phone extensibility. In other words, you keep the phone numbers and carrier setup you already pay for, and the agent's screen no longer has to be Teams.

Microsoft's Teams Phone extensibility documentation describes four setup layers:

  • Teams provisioning: a Teams admin creates a resource account, assigns phone numbers, and adds the contact centre application to that account.
  • Contact centre provisioning: the contact centre admin creates queues, links them to the Teams Phone account, and sets up agent skills and routing groups.
  • Telephony integration: the vendor uses ACS Call Automation APIs to place and receive calls and handle mid-call controls. Microsoft notes the current release supports only Teams Phone service numbers.
  • Agent experience: the vendor builds call handling into its own app using ACS Calling SDKs.

Microsoft's general prerequisites are:

  • A Teams Phone licence for each agent
  • Enterprise voice enabled
  • A Teams Phone resource account licence
  • PSTN connectivity through Calling Plans, Operator Connect or Direct Routing

Those are Microsoft's baseline requirements for Teams Phone extensibility. Luware hasn't published NimbusOne-specific licensing or pricing, so confirm the full bill of materials with Luware or your partner.

Section summary: Unify lets a vendor run agents in its own app on top of your existing Teams Phone setup. NimbusOne is Luware's Unify client.

The certification: newer than it sounds​

Luware says it is one of ten organisations worldwide certified by Microsoft for Unify. Until recently, the public picture was Extend-only. A Swiss Luware partner, Lambert Consulting, wrote about a month ago that Nimbus is certified for the Extend model, and since 2025, Luware has offered a variant of the Unify model, which leverages the extensibility of Teams telephony to access services from Azure. Luware's own Nimbus product page has also described the company as a key Microsoft Extend certified and Teams Phone extensibility partner.

Microsoft's certified contact centre list on Microsoft Learn does include Luware. That page was last updated on April 26, 2026, months before this announcement. A snapshot taken during research for this article showed Luware ticked under Extend rather than Unify. That doesn't mean the claim is wrong; Microsoft says the list is updated as providers meet its criteria. Check the live table, or ask for written confirmation, before treating Unify certification as settled.

This matters for support. Microsoft says it supports contact centre solutions only from certified partners. Issues go to the partner first, and Microsoft may reject cases involving non-certified solutions.

Where NimbusOne fits in Luware's history​

NimbusOne didn't come from nowhere. At Enterprise Connect 2025, Microsoft announced Teams Phone Extensibility. The new model allows independent software vendors (ISVs) to leverage Azure Communication Services (ACS) with Microsoft Teams for enhanced communication. At the time, Luware said it was one of the first ISV partners on this model, through a product called Luware Nimbus Power. Luware said Nimbus Power goes beyond the Extend model and is able to offer built-in AI functions and allows the seamless integration of call controls with third-party applications.

Luware's 2025 blog also previewed the "dual persona" idea. It said Teams Phone extensibility would let contact centre vendors offer a client of choice, and that dual persona functionality enables users to receive and manage the customer calls either through the contact center agent console or the Teams client. Luware hasn't said exactly how NimbusOne relates to the Nimbus Power brand. Read NimbusOne as the dedicated client that delivers what was promised at Enterprise Connect, not as a confirmed rename.

Dual persona: customer calls separate from Teams​

For NimbusOne users, Luware says each employee gets two identities on the same phone system. Customer calls go to NimbusOne. Personal calls, meetings and chats stay in Teams. Teams presence is kept in sync across both.

That matches Microsoft's own "multi persona" documentation for Teams Phone extensibility. A few details are worth knowing before rollout:

  • Ringing is controlled by policy. Microsoft says the Teams policy decides whether an inbound call rings in Teams or the ACS-based app. There is no API to choose.
  • Call history is split. Calls appear only in the client that handled them. The Teams client doesn't show contact centre calls, and the contact centre client doesn't show Teams calls.
  • Presence sync uses Graph. Contact centre vendors subscribe to and set Teams presence through Graph APIs, the same way Extend and Connect vendors already do.
  • Emergency callbacks behave differently. If an emergency call is placed from a custom contact centre client, the emergency services callback rings both that client and Teams. If it's placed from Teams, the callback rings only Teams.

That split call history is a real training issue. An agent who checks Teams for "that customer who called earlier" won't find them.

Real-time AI and the "milliseconds" claim​

Luware says NimbusOne runs transcription and summarisation during the call, so notes are written by the time the call ends. It also lists suggested codes and tags. Luware credits this to ACS handling the call media directly. Microsoft's documentation supports the architecture: ACS audio streaming APIs and Call Automation can feed live audio into Azure AI services for features such as real-time transcription.

Luware also says calls are received "in milliseconds instead of seconds" in high-volume setups. It provides no benchmark, test conditions or comparison, so treat that as marketing until you've seen it in your own pilot. The same goes for the 99.99% SLA on the product page: ask for the contract terms.

What IT admins should weigh​

Possible benefits:

  • One Nimbus admin centre for both Teams-based and NimbusOne agents, instead of a separate system for each team
  • Existing Teams Phone numbers and carrier setup carry over
  • CRM-first staff stop switching between Teams and Dynamics 365 or Salesforce for every call
  • Live transcription built on Azure infrastructure

Open questions:

  • Is Microsoft's Unify certification for Luware reflected on the live list yet?
  • What does NimbusOne cost, and which channels are included in which licence?
  • Where is call and transcript data processed and stored? Luware's partner materials point to Swiss, German and UK hosting for Nimbus, but nothing NimbusOne-specific has been published.
  • How will helpdesk staff troubleshoot ringing that is controlled by policy and call history that is split between two clients?

For Microsoft 365 partners and resellers, Luware is pitching NimbusOne as a way to sell contact centre services to customers already on Teams Phone without starting from scratch. That may well be true, but Unify adds a new layer of ACS infrastructure that needs its own support expertise.

The bottom line​

NimbusOne is a reasonable answer to a real problem: one Teams screen doesn't suit a receptionist, a CRM-first salesperson and a high-volume support agent equally. Building on Unify lets Luware keep Teams Phone underneath while giving each role its own interface. The certification claim still needs checking against Microsoft's live list, and the performance and SLA claims need testing in a pilot. For Dynamics 365 and Salesforce shops already paying for Teams Phone, it's worth a demo. Ask about the licensing math before you sign.


Update: Additional details (October 14, 2026)​

ChannelLife UK reports that NimbusOne is available immediately to both new and existing Luware Nimbus customers. Luware CTO and co-founder Michael Jakob said the client extends the same routing, workflow and AI capabilities beyond Teams for agents working mainly in a CRM or an optimised desktop.

The report also says NimbusOne’s interface can be tailored by role, limiting agents to the tools relevant to their work.

 

References

  1. Luware launches NimbusOne after Microsoft certification - ChannelLife UK ChannelLife UK 2026-10-14T18:14:33+00:00
  2. Luware launches NimbusOne client - Comms Business Comms Business 2026-10-01T12:00:00+00:00
  3. Luware NimbusOne | Run Your Contact Center in Your Client of Choice luware.com