Written with AI assistance.
What is Dynamics 365 Customer Service?
Dynamics 365 Customer Service records, routes and follows up customer enquiries. Service representatives can view customer history and work within the organisation's defined case processes.
The solution can share a platform with sales and other customer processes. Available communication channels and functions depend on configuration and licensing.
Before implementation, clarify responsibility for queues, priorities, knowledge articles and follow-up. Case volumes and handling times only become useful management information when their definitions are clear.
The original demonstration transcript is available in the Norwegian version of this FAQ.
Ask a question or share what helped you.
Customer Service | Questions and answers
The engine that automatically distributes inquiries across channels. It eliminates the need for someone to assign them manually.
Artificial intelligence | Questions and answers
Customer Service | Questions and answers
Sales | Questions and answers
What is the difference between Dynamics 365 and Microsoft 365?
Sales | Questions and answers
What is the difference between Dynamics 365 and Power Platform?
Sales | Questions and answers
An agent can handle high volumes, but it can also undermine trust. Here’s what needs to be in place before you let it loose on customers.
A shared list of issues waiting for someone. A small number of queues with clear ownership works better than many granular ones.
Microsoft 365 consists of the tools everyone uses every day. Dynamics 365 consists of the business systems. They share the same login and are closely integrated, but address different needs.
Dynamics 365 consists of ready-made applications. Power Platform provides the tools to build your own. Both are built on the same foundation.
Those who already use Microsoft, have more than one process to support, and have someone to manage the solution.
WEM MCP tools enabled time-off requests, shift swaps and shift bids in Service Agent. Administrators could enable each tool for a role, team or pilot group.
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.
Gartner found nearly five hours saved per seller each week, but many organisations did not reinvest the time. Dynamics wave 1 described connections across customer insight, sales, service and field work.
HubSpot launched AEO, Smart Deal Progression and updated prospecting and customer-service agents on 14 April. The news connects customer insight with action, while the vendor’s outcome claims still require local verification.
Share a question or reflection.
Be the first to contribute.
