Created with AI.
Most customer inquiries still come in by email. Automatically turning them into cases is usually the first step that delivers visible results — and reveals how many inquiries you actually receive.
The mailbox is registered in Dynamics 365 and must be approved by an administrator before it can synchronize. Test the connection before proceeding—errors here will result in empty queues and confusion later.
Not everything that lands in the inbox is a customer inquiry. Newsletters, automated receipts, and internal copies should not become tickets. Define rules for what should be converted; otherwise, the queue will be flooded with noise in the first week.
This is the most important step. When the customer replies to an ongoing case, the reply must be added to the existing case—not create a new one. Otherwise, you will get duplicates, negatively affecting both your statistics and the customer experience.
A ticket created without ending up in a queue is as invisible as an unread email. Set up routing based on the recipient address or content so that the ticket lands where someone is actually looking.
A brief confirmation with a case number will prevent most follow-ups. Never promise a response time you cannot meet. “We have received your inquiry” is better than “we will respond within one hour” if one hour is unrealistic.
Look for three things: issues that weren't created, noise that became an issue for no reason, and replies that created duplicates. All three are easy to fix now and difficult to clean up after three months.
Ask a question or share what helped you.

Customer Service | Article
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.

Project management | Event
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.

Automation | Article
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.

Customer Service | Article
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.

Customer Service | Article
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.

Sales | Article
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.
Do you have a question or experience to share?
Be the first to contribute.