Created with AI.
Use this routine from the first enquiry until the customer has an understandable resolution or an agreed handover. It suits new agents and experienced colleagues who want cases to be easier to take over.
Continue in the business-area learning path
Let the customer explain the problem and what it prevents. Summarise in your own words and confirm understanding. Separate symptoms from assumed causes. Check whether an existing case already covers the enquiry.
Record who is affected, what fails, when it started and what the customer needs now. Follow the organisation's identity-verification procedure where applicable.
Assess priority using the team's impact and urgency rules. Explain what you will do, what you need from the customer and when they will receive an update. Do not promise an unconfirmed resolution time.
Write an update distinguishing the next contact from expected resolution. Assign an owner and a dated activity.
Use approved knowledge and record relevant attempts and outcomes. Avoid asking the customer to repeat tests without a reason. Seek specialist help when uncertain and explain what you have already checked.
Use: observation / hypothesis / attempt / result / next decision. A negative result can help by narrowing the problem.
When another role must contribute, provide context and a specific question. Agree who owns communication during specialist work. Internal forwarding is not an acknowledged transfer.
Practice case: The technician is busy and has not accepted the case. Keep the customer-contact commitment, alert the team leader and agree an update. Do not tell the customer that the technician has taken over.
Explain what changed, what the customer should expect and what to do if the problem returns. Close according to organisational criteria. Consider a reusable knowledge article without customer-specific information.
Check that a colleague can understand the case without calling you. Write a short resolution note covering symptom, prerequisite, action and outcome verification.
The working routines and fictional examples above are ProsessPilotene learning material. Use the official product documentation below for product context; availability depends on your organisation's setup.
Ask a question or share what helped you.
Use this routine from the first enquiry until the customer has an understandable resolution or an agreed handover. It suits new agents and experienced colleagues who want cases to be easier to take over.

Published 9/9/2026
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.
Read more
Published 9/5/2026 · Event 6/2/2026
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.
Read more
Published 8/25/2026
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.
Read more
Published 7/23/2026
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.
Read more
Published 6/30/2026
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.
Read more
Published 5/29/2026
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.
Read more