Extend Customer Service across the organization

Completed

Dynamics 365 Customer Service connects the customer, case, activities, knowledge, and resolution at the center of the appliance story. That foundation supports the service team, but some needs extend beyond case management. The customer might contact the company through voice or messaging, require a technician at home, or depend on a process designed for that organization.

Other Dynamics 365 applications and Microsoft Power Platform can extend the service experience while preserving useful context. The appropriate extension depends on the work that needs to happen next.

Keep Customer Service at the center

Customer Service provides the durable record of the issue. In the appliance scenario, the case captures the reported error, troubleshooting history, related activities, service commitments, and resolution. Knowledge articles support consistent answers, and the Customer Service agents help the organization understand intent, manage the case, and improve knowledge.

An extension adds capabilities around that foundation. It doesn't require the organization to treat each channel, visit, or automated process as a separate customer story. Instead, the organization determines which information needs to pass between applications and which record owns each part of the work.

For example, the case can remain the record of the customer's issue while another application manages a live conversation or an on-site repair. Microsoft Dataverse provides the underlying data platform for Dynamics 365 customer engagement applications and Power Platform. Organizations still need to design relationships, permissions, processes, and governance for their requirements.

Add engagement with Dynamics 365 Contact Center

Dynamics 365 Contact Center adds voice and digital engagement, self-service, unified routing, and operational capabilities. When an organization uses Contact Center with Customer Service, a conversation can carry customer and interaction context into the case process. The representative can continue the service journey instead of asking the customer to repeat information.

Contact Center also includes three autonomous agents that focus on engagement and contact center operations:

• Customer Assist Agent combines autonomous self-service, real-time representative assistance, and proactive engagement. In the appliance story, it can help the customer explain the issue, present relevant information, or transfer the conversation with context.
• Quality Assurance Agent monitors and evaluates conversations for quality and compliance concerns. It provides alerts and coaching insights that help supervisors respond to issues and improve interactions.
• Service Operations Agent supports conversational setup, configuration validation, operational management, and troubleshooting for contact center components.

These agents have a different scope from the Customer Service agents in the previous unit. Customer Service agents focus on intent, cases, and knowledge. Contact Center agents focus on customer interactions, conversation quality, and contact center operations. Human oversight, security, privacy, compliance, and licensing considerations apply across both groups. For current details, see Contact center agents in Dynamics 365 Contact Center.

Coordinate on-site work with Dynamics 365 Field Service

Some cases can't be resolved through guidance or a remote conversation. If the washing machine needs a physical repair, Dynamics 365 Field Service can manage the work performed at the customer's location.

A case can be converted into a linked work order by using the Case to Work Order Business Process. Relevant case information, such as the incident type, description, and functional location, can carry into the work order. The organization can then define the required service tasks, schedule an appropriate technician, track products and services, and record the completed work.

The case and work order serve related but distinct purposes. The case tracks the customer issue and service history. The work order manages the field work required to address that issue. Linking them helps a representative understand what happens after dispatch and helps a technician receive the context needed for the visit. For current requirements and mappings, see Create a work order from a case.

In the appliance story, the representative determines that a failed component requires replacement. The case becomes the source for a work order, a dispatcher schedules a technician, and the technician records the repair. The resulting information supports case resolution and future service analysis.

Adapt service with Microsoft Power Platform

Microsoft Power Platform helps organizations extend Customer Service for processes that aren't fully addressed by standard application behavior. Because Customer Service uses Dataverse, organizations can build apps, automations, analytics, websites, and agents that work with approved business data and security controls.

Different Power Platform products address different needs:

• Power Apps creates focused applications for specialized roles or processes. The appliance company might provide a quality team with an app for reviewing recurring product issues.
• Power Automate connects events and actions across systems. A flow might notify a service manager when repeated appliance failures reach a defined threshold or route an approval before a replacement is authorized.
• Power BI analyzes service data and presents trends. Reports can help managers compare case volume, resolution outcomes, knowledge use, and repeat issues.
• Power Pages creates external-facing business websites. An organization can provide customers or partners with access to appropriate service information and processes.
• Microsoft Copilot Studio creates and extends agents that use configured knowledge, topics, tools, and connected data to support organization-specific scenarios.

These options can work together, but an organization doesn't need every extension. The service requirement guides the choice:

• Use Contact Center when the need centers on voice or digital engagement, routing, conversation quality, or contact center operations.
• Use Field Service when resolving the case requires work at a customer location.
• Use Power Platform when the organization needs a tailored app, automation, analysis, website, or agent.

Extensions are most useful when they preserve the service context instead of creating another disconnected process. Organizations define data ownership, permissions, monitoring, and escalation before expanding a solution. To continue exploring low-code extensions, see Extend Dynamics 365 Customer Service.