Microsoft published a customer story on July 7, 2026, detailing how Sirva—a U.S.-based global mobility company—successfully migrated its post-merger relocation operations onto Dynamics 365 Contact Center. The move turns the spotlight on a growing enterprise push to embed AI agents and copilots directly into customer service workflows.

The Concrete Details of Sirva’s Shift

Sirva helps corporations move employees around the world, handling everything from home sales and visa sponsorship to temporary housing and expense management. After a merger, the company faced the classic challenge: unifying disjointed systems and processes while maintaining high-touch service for people in the middle of life-changing relocations. Its answer was to re-platform on Dynamics 365 Contact Center, a cloud-based solution that natively integrates voice, chat, SMS, and Microsoft Teams.

Microsoft’s story positions the implementation as “AI-first,” meaning artificial intelligence is not bolted on but woven through every step of the customer journey. While the exact configuration is not public, such deployments typically leverage:

  • Copilot Studio to build custom copilots that can converse naturally with relocating employees, answer policy questions, and escalate to human agents when needed.
  • Power Platform tools like Power Automate and Power Apps to connect backend systems—HR databases, property portals, travel providers—and orchestrate multi-step processes without manual handoffs.
  • AI-driven routing and case classification within Dynamics 365 to instantly categorize inquiries (e.g., “visa delay,” “lease breach”) and push relevant knowledge to both bots and live agents.
  • Sentiment analysis and agent assist that proactively prompt contact center staff when a caller’s frustration is rising.

Sirva did not publicly disclose metric improvements, but its very willingness to share the story suggests gains in customer satisfaction, agent efficiency, or cost reduction.

What It Means for Your Business

Sirva’s decision is far from unique, but its industry makes it an instructive bellwether. Relocation services combine high emotional stakes, regulatory complexity, and a fragmented vendor ecosystem—the kind of terrain where AI either dramatically simplifies operations or fails spectacularly. Here’s what three audiences should take away:

For Business Leaders and Service Owners

If your organization handles complex, multi-touch service journeys (insurance claims, mortgage applications, patient onboarding), the Sirva example validates that AI copilots can now handle more than simple FAQ deflection. They can become the initial point of contact for confidential, emotionally charged interactions—provided the underlying platform gives agents full context when escalation is needed. It also underscores a post-merger or digital-transformation moment as a forcing function: unifying on one contact center platform can finally break data silos that prevent a single view of the customer.

For IT Administrators and Architects

Dynamics 365 Contact Center lives inside the broader Microsoft ecosystem, meaning it can plug into Azure Active Directory, Teams, Power BI, and the Microsoft 365 compliance center. For firms already committed to that stack, adding a contact center module can reduce integration tax. But admins should prepare for new permissions models, channel configurations, and voice telephony decisions (Microsoft often partners with operators like AT&T and T-Mobile for calling plans). Sirva’s success suggests the platform is mature enough for global, multi-lingual operations, but your mileage will depend on thoroughly mapping existing telephony and CRM connections.

For Developers and Citizen Makers

Copilot Studio allows professional developers and business power users to jointly create AI assistants using natural language or low-code tools. Sirva’s use case hints at a model where HR policy documents become grounding data for copilots, and the same workflows surface in the contact center agent’s dashboard and the employee’s self-service portal. If you’re evaluating similar projects, start by identifying one high-volume, well-documented service process—like a relocation expense submission—and build a copilot for it in a sandbox environment. The learning will inform broader rollouts.

The Road to AI-First Customer Service

Dynamics 365 Contact Center emerged from Microsoft’s recognition that customer service technology had to move beyond basic screen pops and call scripts. The product, first announced in 2024, combined the company’s existing omnichannel capabilities with a new composable architecture and deep hooks into Copilot Studio.

Copilot Studio itself is the successor to Power Virtual Agents, and it lets organizations create their own autonomous agents, plug in Azure OpenAI models, and publish bots to channels ranging from websites to Microsoft Teams. The underlying Power Platform provides the connective tissue, with hundreds of prebuilt connectors to SAP, Salesforce, Workday, and other systems.

Sirva’s story lands amid a wave of contact center modernization. Competitors like NICE, Genesys, and Amazon Connect have also pushed AI features, but Microsoft’s angle is integration with the productivity tools workers already use. An agent handling a relocation case can, for instance, open a Teams chat with a real estate partner, pull the expense policy from SharePoint, and have a copilot summarize the last three interactions—all without leaving the contact center interface.

For customers, the payoff is fewer transfers, shorter hold times, and more accurate answers. For businesses, it means being able to handle growing inquiry volumes without a linear increase in headcount.

Action Steps to Consider

If Sirva’s journey intrigues you, here are practical moves to start your own assessment:

  1. Audit your most complex service journeys. Map out every system, manual step, and decision point for your most expensive customer scenario. Look for places where a copilot could safely answer questions or auto-populate fields.
  2. Run a pilot with Copilot Studio. The licensing is often included in Dynamics 365 or Power Platform subscriptions. Build a bot for a single, contained task—say, checking the status of a relocation expense report—and track how many queries it resolves versus how many escalate.
  3. Bring your telephony team in early. Contact center AI fails when call quality is poor. Understand your existing phone infrastructure and how it would connect to Dynamics 365’s voice channel before you commit to a timeline.
  4. Build a business case using industry analogs. Microsoft’s customer stories page (where Sirva appears) often includes quantified outcomes. Use those benchmarks to model potential savings in your environment, even if you must extrapolate.
  5. Prepare your agents. AI assistance changes the agent experience from reactive call-taking to nuanced case management. Training and change management are critical; agents need to trust the AI’s recommendations.

What to Watch Next

Expect Microsoft to follow Sirva’s story with more vertical spotlights as its fiscal year 2027 approaches. Health care, financial services, and government contact centers are likely next, given strict compliance needs and the chance to demonstrate data residency controls. Technologically, the rapid evolution of autonomous agents—bots that can not only answer questions but trigger refunds or amend contracts—will blur the line between self-service and full-service. For businesses, the near-term challenge is picking the right processes to automate without alienating the customers who still need a human touch. Sirva’s bet suggests that line just moved further than many realized.