D365 customer service contact center
Skill Raishin/vanguard-frontier-agentic/skills/microsoft/d365-customer-service-contact-center
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.From its SKILL.md
npx -y skills add Raishin/vanguard-frontier-agentic --skill d365-customer-service-contact-centerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.6 KB, 606 tokens by cl100k_base, as published. Nobody here has run it
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 — use when executing the full Customer Service review or formatting the final answer.
- Safety checklist — use before any recommendation involving production routing rules, SLA configuration, or channel changes.
- Official sources — 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.
What ships with it: 4 files
9.3 KB alongside SKILL.md
references/
- official-sources.md2.5 KB
- safety-checklist.md2.1 KB
- workflow-and-output.md3.0 KB
- metadata.json1.8 KB
Gives 0 of the 12 instructions most customer support skills give in 606 tokens
Counted across 123 of the 124 authors here whose files we hold, read 2026-08-07
- Call RUBE_SEARCH_TOOLS first to get current schemasin 12 of 123, across 4 files
- Confirm connection status is ACTIVE before running workflowsin 12 of 123, across 4 files
- Stop and ask for clarification if required inputs are missingin 9 of 123, across 2 files
- Call RUBE_MANAGE_CONNECTIONS with the helpdesk toolkitin 9 of 123, across 2 files
- Use both timestamp and ID for cursor navigationin 8 of 123, across 1 file
- Implement backoff on 429 responsesin 8 of 123, across 1 file
- Parse response data defensively with fallback patternsin 8 of 123, across 1 file
- Use this skill only when the task clearly matches the scopein 8 of 123, across 1 file
- Pass a JSON file as the positional argumentin 7 of 123, across 1 file
- Specify output format with the --format flagin 7 of 123, across 1 file
- Run health, churn, and expansion scripts togetherin 7 of 123, across 1 file
- Verify output files contain expected records before continuingin 7 of 123, across 1 file
Said here and by no other author read
- Separate confirmed facts from inference
- State when metrics are not provided
- Challenge cases routed manually at scale
- Challenge SLAs without warning actions
- Challenge knowledge bases without curation or expiry
- Challenge channels configured without capacity profiles
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.