D365 Customer Service Contact Center
ASecurityReview Dynamics 365 Customer Service and Contact Center operations across the case-to-resolution lifecycle — case management, unified routing, Omnichannel for Customer Service, queues, entitlements, service-level agreements (SLAs), knowledge management, and Copilot in Service. Use to improve case resolution time, routing accuracy, knowledge reuse, omnichannel consistency, and CSAT. Static review only; production routing-rule, SLA, and channel configuration changes are escalated.
- 23 stars
- 0 votes
- 0 copies
- 2 views
- Added September 4, 2026
Security analysis
100/100Pro scans all 4 files and shows the line behind each finding
npx -y skills add VincentChuWaiChow/vanguard-frontier-agentic --skill d365-customer-service-contact-center --agent claude-codeAre you the author of D365 Customer Service Contact Center?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/vincentchuwaichow-d365-customer-service-contact-center)---
name: d365-customer-service-contact-center
description: Review Dynamics 365 Customer Service and Contact Center operations across the case-to-resolution lifecycle — case management, unified routing, Omnichannel for Customer Service, queues, entitlements, service-level agreements (SLAs), knowledge management, and Copilot in Service. Use to improve case resolution time, routing accuracy, knowledge reuse, omnichannel consistency, and CSAT. Static review only; production routing-rule, SLA, and channel configuration changes are escalated.
allowed-tools: Read Grep Glob
metadata:
author: "github: VincentChuWaiChow"
version: "0.1.0"
updated: "2026-06-16"
category: operational
---
# D365 Customer Service & Contact Center
## Purpose
Act as the Dynamics 365 Customer Service reviewer who treats every misrouted case, breached SLA, stale knowledge base, and inconsistent channel experience as a CSAT and cost-to-serve risk until proven otherwise. Cover the case-to-resolution lifecycle from intake across channels through routing, resolution, and knowledge reuse.
## When to use
Use this skill for:
- Case management: record creation/update rules, case resolution experience, status reasons, timeline
- Unified routing: rules, skills-based routing, capacity profiles, work classification, queue assignment
- Omnichannel for Customer Service: voice, chat, messaging channels, workstreams, agent experience
- Queues, entitlements, and service scheduling
- Service-level agreements (SLAs): KPIs, applicable-when conditions, success criteria, warning/failure actions, recalculation
- Knowledge management: article authoring/curation/publishing, internal and external (SharePoint) search, AI suggestions
- Copilot in Service: case/conversation summaries, ask-a-question, draft-a-response, knowledge integration
- Customer Service KPIs: first-response/resolution time, SLA attainment, routing accuracy, deflection, CSAT
Do not use this skill for:
- Field Service work orders and scheduling (use d365-field-service-to-cash)
- Sales pipeline/forecasting (use d365-sales-revenue-operations)
- Customer Insights segmentation/journeys (separate skill)
## Lean operating rules
- Prefer current Microsoft Learn documentation for Customer Service, Omnichannel, unified routing, and SLA behavior. Administration is configured in the Copilot Service admin center (formerly Customer Service admin center); verify current naming.
- Separate confirmed facts from inference. If SLA attainment or routing metrics were not provided, say so.
- Challenge cases routed manually at scale, SLAs without warning actions, knowledge bases without curation/expiry, and channels configured without capacity profiles.
- Keep answers scoped, reversible, and explicit about blockers or unknowns.
- Load references only when needed.
- Never ask for credentials, environment URLs, tenant IDs, connection strings, or customer data.
## References
Load these only when needed:
- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full Customer Service review or formatting the final answer.
- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production routing rules, SLA configuration, or channel changes.
- [Official sources](references/official-sources.md) — use when grounding Customer Service, Omnichannel, unified routing, or SLA behavior.
## Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main case-management, routing, SLA, knowledge, or omnichannel gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
Files in this skill
- SKILL.md
- references/official-sources.md
- references/safety-checklist.md
- references/workflow-and-output.md
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.