• Tangible vs. Intangible (e.g., machinery vs. patents)
• Current vs. Non-current (e.g., inventory vs. buildings)
• IT assets, Facilities, Vehicles, etc.
• Depreciation categories for accounting purposes

• Fixed Asset Management: Allows classification by asset group, location, department, and responsible employee. Supports tagging assets with custom attributes for more granular classification.
• Hierarchical Structures: Assets can be grouped into parent-child relationships (e.g., a vehicle fleet with individual cars).
• Lifecycle Tracking: Tracks assets from acquisition to disposal, with classification updates at each stage.
• Reporting and Analytics: Enables filtering and reporting based on asset classifications for audits, budgeting, and compliance.

Steps to Analyze Case Patterns in D365 Customer Service

Analyzing case patterns in Microsoft Dynamics 365 Customer Service helps identify recurring issues, optimize resource allocation, and improve service efficiency. This guide outlines how to use Customer Service Historical Analytics to uncover case trends and patterns.

1. Accessing Case Analytics in D365

Step 1: Open Customer Service Historical Analytics

1. Navigate to Customer Service Workspace or Customer Service Hub.
2. Click Customer Service Historical Analytics from the left-hand navigation panel.
3. Open the Case Insights Dashboard.

2. Identifying Case Trends & Recurring Issues

Step 2: Review Case Volume Trends

Metrics to Analyze:

• Total Cases Created Over Time – Identify seasonal or recurring spikes.
• Case Volume by Type – Determine which types of issues occur most often.
• Case Volume by Channel – Compare issues reported via email, chat, phone, or self-service portal.
• Top Customers by Case Count – Identify customers submitting frequent cases.

Best Practice: Apply date range filters (weekly, monthly, quarterly) to spot long-term trends.

Step 3: Analyze Case Resolution & Escalations

Key Metrics:

• Average Resolution Time – Identify case types taking longer to resolve.
• Escalation Rate by Case Type – Find case categories that frequently require higher-level intervention.
• Case Reopen Rate – Detect cases that were closed but needed follow-up.

Best Practice: If certain case types have high escalation or reopen rates, they may require process improvements or updated Knowledge Articles.

3. Analyzing Agent & Team Case Handling Patterns

Step 4: Evaluate Agent & Team Performance

1. In Customer Service Historical Analytics, open the Agent Insights dashboard.
2. Filter by Agent Name or Team.
3. Analyze the following KPIs:
   • Average Case Handling Time Per Agent – Identify efficiency gaps.
   • Number of Cases Assigned vs. Resolved – Compare workload vs. output.
   • Escalation Rate Per Agent – Find agents frequently escalating cases.

Best Practice: Compare case resolution trends across different teams or shifts to optimize staffing.

4. Detecting SLA Violations & Resolution Delays

Step 5: Identify SLA Compliance Trends

Key Metrics:

• Total SLA Breaches – Cases exceeding response or resolution deadlines.
• Cases Nearing SLA Deadline – Identify cases at risk of violating SLAs.
• Case Resolution Time vs. SLA Goal – Compare actual vs. expected resolution performance.

Best Practice: Use Power Automate to notify managers when cases are approaching SLA limits.

5. Leveraging Customer Feedback for Pattern Analysis

Step 6: Review Customer Satisfaction (CSAT) Scores

1. Navigate to the CSAT (Customer Satisfaction) Dashboard.
2. Analyze feedback on resolved cases.
3. Identify recurring themes in low-rated cases (e.g., long wait times, incomplete resolutions).

Best Practice: If certain case types consistently get low ratings, investigate process bottlenecks or training needs.

6. Best Practices for Case Pattern Analysis

Monitor trends weekly/monthly to detect emerging issues early.
Use AI-powered insights (Copilot) to recommend case resolutions.
Optimize Knowledge Articles based on case trends.
Automate alerts for SLA risks and escalation trends with Power Automate.

Steps to Analyze Knowledge Base Usage in D365 Customer Service

Analyzing Knowledge Base (KB) usage in Microsoft Dynamics 365 Customer Service helps organizations evaluate how effectively agents and customers are using articles to resolve cases. This guide outlines the steps to track, review, and optimize KB usage.

1. Why Analyze Knowledge Base Usage?

Identify the most frequently used articles.
Assess whether KB articles are resolving cases.
Determine gaps in knowledge content.
Improve article quality and relevance.

2. Steps to Analyze Knowledge Base Usage in D365

Step 1: Access Knowledge Base Insights

1. Navigate to Customer Service Hub or Customer Service Workspace.
2. Click on Knowledge Articles in the left-hand navigation panel.
3. Select Knowledge Search Analytics under Insights (if enabled).

Step 2: Review Knowledge Search Analytics

Metrics to Analyze:

• Top-searched keywords: Identify what agents and customers search for.
• Most-viewed articles: See which articles are frequently accessed.
• Article success rate: Review how often an article is linked to resolved cases.
• Unused or low-performing articles: Identify articles that need updates or removal.

How to View Data:

• Open Dashboards > Knowledge Search Analytics for graphical reports.
• Use Power BI Reports if custom analytics are set up.

Step 3: Track Knowledge Base Usage in Cases

1. Open Service > Cases.
2. Use the Knowledge Search panel to see linked articles.
3. Filter cases by Knowledge Article Associations to check:
   • How often articles are attached to cases.
   • Whether articles contribute to case resolution.
   • Feedback on article effectiveness.

Step 4: Analyze Agent Engagement with KB Articles

Navigate to Settings > Service Management > Knowledge Search Analytics.
Review:

• Which agents use KB articles the most.
• Article attachment trends per agent/team.
• Cases where no KB article was used (indicating potential content gaps).

Step 5: Gather Customer Feedback on KB Articles

1. Enable Knowledge Article Ratings & Feedback

   • Go to Settings > Service Management > Knowledge Settings.
   • Enable Ratings & Comments for KB articles.

2. Review Customer Feedback

   • Open Knowledge Articles > Select an article.
   • View Ratings, Comments, and Helpful/Not Helpful votes.
   • Identify articles with poor feedback and update them.

Step 6: Use Reports & Dashboards for KB Insights

Standard Reports:

• Open Reports > Knowledge Base Usage Report.
• Export data to Excel for further analysis.

Power BI Dashboards (If Enabled):

• Track Knowledge Base adoption trends.
• Visualize article effectiveness per category or product.

Process for Assigning a Case to a Team, Individual, or Queue in D365 Customer Service

Assigning cases correctly in D365 Customer Service ensures that the right team, individual, or queue handles the case efficiently, improving response times and resolution rates.

1. Steps to Assign a Case to a Team, Individual, or Queue

Step 1: Open the Case Record

1. Navigate to Customer Service Workspace.
2. In the left navigation, go to Cases.
3. Open the case that needs to be assigned.

Step 2: Choose Assignment Method

A. Assign to an Individual

1. Click on the Assign button in the top action bar.
2. In the Assign To window, select User.
3. Search for and select the User to assign the case to.
4. Click Assign.
   The case is now owned by the selected individual.

B. Assign to a Team

1. Click Assign.
2. In the Assign To window, select Team.
3. Search for and select the Team.
4. Click Assign.
   The case is now owned by the selected team, and any team member can work on it.

C. Assign to a Queue (For Automatic or Shared Work Handling)

1. Open the Case Record.
2. Locate the Queue field.
3. Click Change Queue and select the appropriate queue.
4. Click Save & Close.
   ✅ The case is now assigned to a queue, and available agents can pick it up.

Step 3: Automate Assignment Using Routing Rules (Optional)

If cases should be assigned automatically, configure Routing Rules:

1. Navigate to Customer Service Admin Center.
2. Go to Work Distribution & Routing → Routing Rule Sets.
3. Define rules based on case priority, type, or customer.
4. Assign cases directly to a queue, team, or user.
   Cases are now automatically routed based on predefined rules.

Steps for Capturing Details About a Case in D365 Customer Service

Capturing detailed and accurate information about a Case in D365 Customer Service is essential for effective resolution, tracking, and reporting.

1. Steps to Capture Case Details

Step 1: Open the Customer Service Workspace

1. Navigate to Customer Service Workspace.
2. Click on Cases from the left navigation panel.
3. Click New Case to create a new record.

Step 2: Enter Case Information

1. Customer Information

   • Select Customer (Account or Contact).
   • Add Primary Contact (if applicable).

2. Case Classification

   • Enter Case Title (e.g., "Billing Discrepancy Issue").
   • Select Case Type (e.g., Inquiry, Complaint, Service Request).
   • Choose a Case Subject from the defined hierarchy.
   • Assign Priority (Low, Normal, High, Critical).

3. Case Origin

   • Select Case Source (e.g., Phone, Email, Web, Chat, Social Media).
   • If the case was automatically created, review auto-filled details.

4. Description of the Issue

   • Provide a detailed description of the customer's issue.
   • Attach screenshots, documents, or videos if applicable.

5. Assign the Case (Optional)

   • Assign to a specific agent, team, or queue for handling.
   • Use routing rules if automatic assignment is enabled.

Step 3: Capture Additional Case Details

1. Related Cases or Similar Issues

   • Use AI-based Similar Case Detection to find related cases.
   • Link relevant knowledge articles if available.

2. Service-Level Agreements (SLAs)

   • Verify response time requirements based on customer SLAs.
   • Ensure SLA timers are tracking appropriately.

3. Customer Entitlements (If Applicable)

   • Check entitlements to see the level of support the customer is eligible for.

4. Case Timeline & Notes

   • Log agent interactions, customer follow-ups, and status updates.
   • Record any internal comments for reference.

Step 4: Save & Track Case Progress

1. Click Save & Close or Save & Continue.
2. The case is now available for agents to update, resolve, or escalate.
3. Use Dashboards & Reports to track case resolution times and trends.

Steps to Create a Case from Different Channels in D365 Customer Service

Cases can be created manually by agents or automatically when customer interactions come from various channels like chat, phone calls, portal requests, emails, and product returns.

Steps to Create a Case from Different Channels

A. Create a Case from a Chat (Omnichannel for Customer Service)

1. Enable Omnichannel for Customer Service in Customer Service Admin Center.
2. Customer starts a chat session via Live Chat, SMS, or WhatsApp.
3. Agent receives the chat in the Omnichannel Agent Dashboard.
4. Click Create Case directly from the chat window.
5. The system auto-fills:
   • Customer Name (if authenticated).
   • Case Origin = Chat.
   • Conversation Details from the chat.
6. Agent enters additional details and clicks Save & Close.
   The case is now linked to the chat conversation.

B. Create a Case from a Live Phone Call in Omnichannel

1. Open Omnichannel for Customer Service.
2. Navigate to the Omnichannel Agent Dashboard.
3. When a phone call request arrives, click Accept.
4. The call session will open in the conversation panel.
5. Click More Actions (⋮) → Create Case.
6. A new Case Form will open with the following auto-filled details:
   • Customer Name
   • Case Origin = Phone Call
   • Call Transcript or Notes (if enabled)
7. Enter additional details:
   • Case Title (brief issue summary).
   • Case Type (Inquiry, Complaint, Service Request, etc.).
   • Priority (Low, Normal, High, Critical).
   • Detailed Description of the issue.
8. Assign the case to a specific agent, team, or queue (or let Routing Rules assign it automatically).
9. Click Save & Close to link the case to the phone call session.
   The phone call is logged, and the case is linked for further resolution.

C. Create a Case from a Portal Request

1. Customer submits a request via the Customer Self-Service Portal.
2. The system automatically creates a case when the request is submitted.
3. The Case Record is auto-populated with:
   • Customer Name & Contact Info.
   • Case Title & Description (from the form submission).
   • Case Origin = Portal.
4. Case routing rules assign the case to a team or queue.
5. Customer receives an automated email confirmation.
   The case is now in the system and ready for an agent to process.

D. Create a Case from an Email

1. Enable Email-to-Case Automation in Customer Service Admin Center.
2. Customer sends an email to a designated support email address.
3. The system automatically:
   • Creates a Case Record.
   • Links the email conversation to the case.
   • Sets Case Origin = Email.
4. The case is placed in the Email Queue, ready for assignment.
   Agents can now respond directly from the case record.

Steps to Manually Create a Case in D365 Customer Service

Creating a case manually ensures that customer issues are properly tracked and assigned, especially for cases such as customer complaints, product returns, and disputed invoices.

1. Steps to Manually Create a Case

Step 1: Open Customer Service Workspace

1. Navigate to Customer Service Workspace in Dynamics 365.
2. Click on Cases from the left navigation panel.
3. Click New Case to open the case creation form.

Step 2: Enter General Case Information

1. Customer Information

   • Select Customer Name (Contact or Account).
   • Add Primary Contact (if applicable).

2. Case Classification

   • Case Title → Briefly describe the issue (e.g., "Damaged Product Received").
   • Case Type → Select from predefined categories (e.g., Complaint, Product Return, Billing Issue).
   • Case Subject → Select a relevant subject (e.g., "Shipping Issues", "Billing Disputes").
   • Priority → Set based on urgency (Low, Normal, High, Critical).

3. Case Origin

   • Choose how the issue was reported (Phone, Email, Chat, Web, In-Person).

Step 3: Capture Specific Case Details Based on Type

A. Example based on customer complaint

1. Case Type: Complaint
2. Description: Document the customer’s concern in detail.
3. Attachments: Upload any supporting files (screenshots, email evidence).
4. Resolution Expectations: Document what the customer expects as a resolution.
5. Assign Case:
   • Assign to Customer Relations Team or a specific agent.
   • Use Routing Rules if automated assignment is enabled.
6. Click Save & Close or Save & Continue.
   The customer complaint case is logged and ready for resolution.

B. Example based on Product Return Case

1. Case Type: Product Return
2. Order Number: Link the case to the corresponding order.
3. Reason for Return: Select from predefined options (Defective, Wrong Item, Not Needed).
4. Return Process:
   • Attach return documents (receipts, images of the product).
   • Provide shipping instructions if necessary.
5. Assign Case:
   • Assign to Returns Processing Team.
   • Move the case to a Product Return Queue.
6. Click Save & Close.
   The product return case is created and linked to the order.

C. Example based on Disputed Invoice Case

1. Case Type: Billing Issue
2. Invoice Number: Enter or search for the disputed invoice.
3. Dispute Reason: Select from predefined options (Incorrect Amount, Duplicate Charge, Unauthorized Charge).
4. Supporting Evidence: Attach relevant documents (invoice copy, payment receipt, customer email).
5. Resolution Process:
   • Specify the next steps (review invoice, credit/refund processing).
   • Assign case to Billing/Accounts Team.
6. Click Save & Close.
   The disputed invoice case is logged and ready for financial review.

Step 4: Follow Up & Track Case Progress

1. Use Case Timeline to document updates and customer follow-ups.
2. Attach relevant Knowledge Base Articles for agent reference.
3. Set up SLA tracking to ensure timely resolution.
4. If needed, escalate the case to a higher-priority team.

Defining Agent Skill Set in D365 Case Management is part of Omnichannel for Customer Service and Unified Routing. It plays a crucial role in intelligent case routing but is not a mandatory prerequisite for basic case creation. However, if you're implementing automated case routing and queue management, agent skill definitions should be configured.

Where to Define Agent Skill Sets?

Agent skills are primarily set up in the Customer Service Admin Center or Omnichannel for Customer Service under the Work Distribution and Routing settings.

Steps to Define Agent Skill Set for Case Routing

1. Enable Unified Routing (If Not Already Enabled)

   • Go to Customer Service Admin Center > Work Distribution > Unified Routing.
   • Enable Unified Routing to allow intelligent case assignments.

2. Define Skills

   • Navigate to Customer Service Admin Center > Agent Experiences > Skills.
   • Click New Skill and define:
     • Skill Name (e.g., "Warranty Claims Processing").
     • Skill Category (Optional for grouping).
     • Skill Proficiency Levels (Optional: Beginner, Intermediate, Advanced).

3. Assign Skills to Agents

   • Go to Customer Service Admin Center > Agent Experiences > Agent Profiles.
   • Select an Agent Profile or create a new one.
   • Assign skills based on expertise.

4. Configure Skill-Based Routing Rules

   • Navigate to Work Distribution & Routing > Routing Rulesets.
   • Define a new Routing Rule for cases based on attributes like:
     • Case Type
     • Case Subject
     • Customer Priority
     • Entitlement
   • Assign the rule to a queue with agents who have the required skills.

5. Assign Agents to Queues

   • Go to Workstreams > Create a Workstream (or modify an existing one).
   • Add Skill Matching Criteria to route cases based on agent skills.
   • Assign Agents to queues based on their defined skills.

6. Enable Auto-Assignment of Cases to Agents

   • Ensure auto-assignment is enabled within Routing & Work Distribution.
   • Cases will now be assigned to the best-matched agent based on skill proficiency.

How It Works in Case Management?

• When a case is created, unified routing checks agent availability, assigned skills, and proficiency.
• The system intelligently routes the case to the best-qualified agent.
• If no skilled agent is available, fallback rules (such as routing to a general queue) apply.

Where Does This Fit in the Case Creation Process?

Agent skill set definition fits under Step 4 (Queues & Routing) in case management setup. While not mandatory for case creation, it is essential for intelligent case assignment.

Would you like help configuring this in your D365 environment?

Defining Queues and Teams in D365 Customer Service

Queues and Teams are essential components in D365 Customer Service for managing and routing cases efficiently. Queues help organize and distribute work items, while Teams group users together based on roles, expertise, or business functions.

1. Defining Queues in D365 Customer Service

A Queue is a collection of work items (Cases, Activities, Emails, etc.) that can be assigned to users or teams for resolution.

Steps to Create a Queue

1. Go to the Power Platform Admin Center → Select your D365 Customer Service App.
2. Navigate to Customer Service Hub → Service Management → Queues.
3. Click New to create a new queue.
4. Fill in the details:
   • Name: E.g., "Warranty Claims Queue"
   • Type:
     • Public: Any user can work on queue items.
     • Private: Only assigned users can access the queue.
   • Incoming Email (if using email-to-case routing).
   • Associated Team (Optional): Links the queue to a team for better work distribution.
5. Save and Close.

Types of Queues

• Default Queue: Assigned automatically to each user and team.
• Custom Queues: Specific to business processes (e.g., "High Priority Cases").
• Routing Queues: Used in Omnichannel for automated case routing.

2. Defining Teams in D365 Customer Service

A Team is a group of users who share ownership of records and work collaboratively.

Steps to Create a Team

1. Go to Power Platform Admin Center → Advanced Settings.
2. Navigate to Settings → Security → Teams.
3. Click New and enter:
   • Team Name: E.g., "Warranty Support Team"
   • Business Unit: Assign to the correct unit.
   • Team Type:
     • Owner Team (Default) – Can own records.
     • Access Team – Can only collaborate but not own records.
   • Queue Association: (Optional) Assign a default queue for the team.
4. Add Users to the Team.
5. Save and Close.

Steps to Define a Business Process Flow (BPF) in D365 Customer Service

A Business Process Flow (BPF) in Dynamics 365 Customer Service guides users through a structured sequence of stages to ensure consistent case resolution.

1. Access the Business Process Flow Designer

1. Navigate to Power Apps (https://make.powerapps.com).
2. Select the Environment where you want to create the BPF.
3. Go to Solutions (or create a new solution to store the BPF).
4. Click New → Select Process.
5. In the Create Process dialog:
   • Process Name: e.g., "Case Resolution Process"
   • Category: Business Process Flow
   • Entity: Case
   • Click Create.

2. Define Stages & Steps in the Business Process Flow

A BPF consists of Stages (phases) and Steps (fields to be filled in each stage).

Example Stages for Case Management:

1. Identify Issue

   • Step 1: Enter Case Title (Required).
   • Step 2: Select Case Type (Problem, Request, Inquiry).

2. Investigate

   • Step 1: Assign to an Agent or Queue.
   • Step 2: Capture Customer Notes or Attachments.
   • Step 3: Set Case Priority.

3. Resolve

   • Step 1: Enter Resolution Details.
   • Step 2: Confirm Customer Satisfaction.

4. Close Case

   • Step 1: Mark Case as Resolved or Escalated.
   • Step 2: Generate Closure Summary Report.

3. Configure Conditional Branching (If Needed)

• If Case Type = "High Priority", route it to a Supervisor Review stage.
• If Case Resolution Time > 24 hours, escalate the case automatically.

To configure branching:

1. Click the Stage where you want a decision point.
2. Click Add Condition.
3. Define logic (e.g., "If Case Priority = High, move to Escalation Stage").
4. Apply conditions and save.

4. Set Required Fields & Permissions

• Mark important fields as Required to ensure data entry before moving to the next stage.
• Assign security roles to control who can modify the BPF.

5. Activate and Publish the BPF

1. Click Validate to check for errors.
2. Click Save and then Activate.
3. Publish the BPF so users can see it in Case Records.

Bonus: Tracking & Reporting on BPF Progress

• Use Dashboards to track how long cases stay in each stage.
• Create Power BI reports to analyze case resolution efficiency.

Determining Operating Hours in D365 Customer Service

Operating hours in Dynamics 365 Customer Service define the availability of support teams, queues, and service-level agreements (SLAs). They ensure that case escalations, response times, and agent availability are aligned with business hours.

1. Steps to Define Operating Hours in D365

Step 1: Navigate to the Customer Service Admin Center

1. Sign in to Power Platform Admin Center (https://admin.powerplatform.microsoft.com).
2. Select your D365 environment.
3. Open the Customer Service Admin Center or Omnichannel Admin Center.

Step 2: Create Operating Hours

1. Navigate to Work Distribution & Routing → Operating Hours.
2. Click New and enter:
   • Name: (e.g., "Standard Business Hours" or "24/7 Support Hours").
   • Time Zone: Select the applicable time zone.
3. Under Weekly Schedule, define working hours for each day:
   • Example:
     • Monday - Friday: 8:00 AM - 6:00 PM
     • Saturday - Sunday: Closed
4. If 24/7 Support is required, select Always Open.
5. Click Save.

Step 3: Define Holiday Schedules (If Applicable)

1. In the Operating Hours record, navigate to Holidays.
2. Click New Holiday and define:
   • Holiday Name (e.g., "New Year's Day").
   • Date & Time when support is unavailable.
3. Save and repeat for other holidays.

Step 4: Assign Operating Hours to Entities

• Queues: Ensure that case routing respects working hours.
• SLAs: Define business hours for response time tracking.
• Omnichannel Workstreams: Control when live chat and phone support are available.

Step 5: Validate and Publish

1. Check that queues and SLAs reference the correct Operating Hours.
2. Test by creating a Case or Work Item outside business hours to verify behavior.