I

in macron nr

Understanding the Dynamics 365 Service Module

What it is:
• The Service Module in Dynamics 365 Customer Engagement is our specialized tool for managing all customer
interactions related to support, inquiries, and issues.
• It's designed to help us deliver excellent customer service by centralizing all customer-related information and
streamlining our support processes.

Key Goals of the Service Module:

• Respond Faster: Get to customer issues quickly.
• Resolve Efficiently: Find solutions and fix problems effectively.
• Improve Customer Satisfaction: Make our customers happy and loyal.
• Gain Insights: Understand common issues and improve our service over time.
Think of it as: Our digital helpdesk, where every customer's need is tracked and managed professionally.

The Core of Our Work: The "Case"

What is a "Case"?
• In the Service Module, a "Case" is our official record for a single customer issue, question, complaint, or request that
requires a resolution.
• It's like a digital ticket or incident report for every customer interaction where they need our assistance.

Purpose of a Case:
• Tracking: We use it to track the entire lifecycle of a customer's problem, from when it's first reported until it's fully
resolved.
• History: It records all communication (phone calls, emails) and actions taken to solve the problem.
• Collaboration: Allows different team members to see the status and contribute to solving the issue.
• Accountability: Ensures no customer issue falls through the cracks.
Think of it as: The central file for a customer's problem - everything about that specific problem goes into its case.

Training Agenda
 Core Navigation & Case Creation Managing &

Working a Case

Advanced Topics & Best Practices

• Working with Queues

• Understanding Service Level Agreements (SLAs)

• Exploring Service Dashboards

• Key Best Practices & Q&A

Dynamics 365 Service Module: Your Daily Navigator

Key Takeaways:
• Left Navigation Pane: Your primary tool for moving between Cases, Accounts, Contacts.
• Quick Create ('+ New'): Fastest way to create new records from anywhere.
• Global Search Bar: Quickly find any record (cases, customers).
• Views: Pre-filtered lists to organize your work (e.g., "My Active Cases").
• Timeline: Chronological history of all activities on a record.

Hands-on Exercise: Navigating & Finding

1. Navigate: Go to Service -> Cases.
2. Change View: Change 'My Active Cases' to 'All Active Cases'.
3. Search: Use the search bar to find an existing Account (e.g., 'Contoso Ltd.').
4. Explore Timeline: Open the found Account and observe its 'Timeline'.

Understanding and Creating a Case Key Case Form Fields:

• Customer (Critical): Link to the Account/Contact who reported the issue.
• Subject: Categorizes the type of problem.
• Origin: How the customer contacted us (Phone, Email, etc.).
• Priority: Urgency of the issue.
• Description: Detailed explanation of the customer's problem.
• Business Process Flow (BPF): Guided stages for resolution (Identify, Research, Resolve).

Hands-on Exercise: Create Account, Contact, and Case

Scenario: Alice Johnson from "Northern Lights Design" calls with an order issue.

1. Create Account: Use '+ New' -> 'Account'. Name: "Northern Lights Design". 'Save & Close'.
2. Create Contact: Use '+ New' -> 'Contact'. Name: "Alice Johnson", link to "Northern Lights Design". 'Save &
Close'.
3. Create Case: Go to 'Service' -> 'Cases' -> '+ New Case'.
• Customer: Select "Alice Johnson".
• Subject: Choose "Order Issue".
• Origin: Select "Phone".
• Priority: Select "Normal".
• Description: "Customer reports missing items from order #NL2025-001. Package arrived damaged."
• Save the case.
%_J

Updating Cases & Logging Interactions Why Log Activities?

• Creates a complete, chronological history of customer interactions.
• Helps other agents quickly understand the case context.
• Crucial for auditing and tracking resolution steps.

Common Activity Types (on the Timeline):

• Phone Call: Record incoming/outgoing calls.
• Email: Track emails sent to or received from the customer.
• Task: Assign follow-up actions to yourself or others.
• Note: Add internal comments or important context.

Hands-on Exercise: Log Customer Interactions

1. Open Case: Ensure Alice Johnson's case is open.
2. Log Phone Call: On 'Timeline', '+' -> 'Phone Call'. Desc: "Customer provided photos of damaged packaging." Dir:
"Incoming". 'Save'.
3. Log Email: On 'Timeline', '+' -> 'Email'. Subject: "Regarding your damaged order". Desc: "Sent apology and initiated
reshipment process." Dir: "Outgoing". 'Save'.
4. Create Task: On 'Timeline', '+' -> 'Task'. Subject: "Confirm re-shipment for Alice Johnson". Set 'Due Date'. 'Save'.
5. Add Note: On 'Timeline', '+' -> 'Note'. Text: "Customer was very understanding. Good resolution needed." 'Add Note'.
6. Review: Scroll through the timeline to see all your new activities.

Resolution & Self-Service Tools

Resolving a Case:
• Marks the case as completed and closed.
• Removes it from your active workload.
• Case becomes read-only (for historical reference).
• Requires Resolution Type and Resolution Description.

The Knowledge Base (KB):

• A central library of solutions, FAQs, and troubleshooting guides.
• Helps you find quick answers and ensure consistent responses.
• Can be linked to cases or emailed to customers.

Hands-on Exercise: Resolve & Use KB

Scenario: Alice's re-shipment is confirmed, issue resolved.

1. Find KB Article: On Alice Johnson's case, use 'Knowledge Base Search' (right pane). Search: "Missing Order
Items".
2. Link KB: Click on a relevant article and 'Link to Case'.
3. Resolve Case: Click 'Resolve Case' (top command bar).
• Resolution Type: Select "Problem Solved".
• Resolution Description: "Missing items re-shipped and received by customer. Issue fully resolved."
Click 'Resolve'.

4. Verify: Try to edit a field on the now resolved case. Observe it's read-only.
I

Queues and Dashboards Queues:

• Shared "inboxes" for incoming cases.
• Cases land here (e.g., from email, portal) until an agent Picks them.
• Ensures fair distribution of work.

Picking a Case:
Assigning a case from a queue to yourself.

Dashboards:
• Visual summaries of your workload and team performance.
• Quick insights into case volume, priority, origin, etc.
• Helps prioritize and manage your daily tasks.

Hands-on Exercise: Practice Queues & Dashboards

1. Access Queues: Go to 'Service' -> 'Queues'.
2. Pick a Case (Simulated/Actual): If available, click a general queue, select a case, and click 'Pick'. If not, your trainer will
simulate this action.
3. Go to Dashboards: Navigate to 'Dashboards'.
4. Review Dashboard: Ensure you are on 'Customer Service Agent Dashboard'. Observe 'My Active Cases' and other
charts.
5. Explore Other Dashboards: Briefly click the dropdown next to the dashboard name and select another service-related
dashboard if available.

Meeting Expectations: Service Level Agreements (SLAs)

What is an SLA?
• An agreement defining the timeframes for responding to and resolving customer cases.
• Helps ensure we meet customer expectations and organizational standards.

SLA Components:
• KPI (Key Performance Indicator): What is being measured (e.g., 'First Response By', 'Resolve By').
• Applicable When: Conditions for when the SLA starts/stops.
• Success Condition: When the KPI is considered met.
• Failure After: The time limit before the SLA is breached.
• Warning After: When a warning is triggered (e.g., 75% of time elapsed).
• Business Hours: Excludes non-working hours from SLA calculation.

Where you see SLAs on a Case:

• Look for the 'SLA Timer' widget directly on the Case form. It shows remaining time and status.

SLA Creation (Admin View) - Step-by-Step:

1. Switch App: From App picker (top left), select 'Customer Service admin center'.
2. Navigate to SLAs: In left nav, 'Operations' -> 'Service terms' -> 'Manage' (next to SLAs).
 3. Create New SLA: On 'Service Level Agreements' page, '+ New'.
4. Fill Details:
'Name': Descriptive name (e.g., "Standard Case SLA").
'Entity': Select 'Case'.
'Applicable From': (e.g., 'Case Created On').
'Business Hours': Select your organization's business calendar.
'SLA Type': Select 'Standard'.
'Save'.
5. Add SLA Item (e.g., First Response): Scroll to 'SLA Items', '+ New SLA Item'.
'Name': "First Response KPI".
'KPI': 'First Response By'.
'Applicable When': e.g., 'Case Status Equals Active'.
'Success Condition': e.g., 'First Response Sent Equals Yes'.
'Failure After': e.g., '4 Hours'.
'Save & Close'.
6. Add Another SLA Item (e.g., Resolve By): '+ New SLA Item'.
'Name': "Resolve By KPI".
'KPI': 'Resolve By'.
'Applicable When': e.g., 'Case Status Equals Active'.
'Success Condition': e.g., 'Case Status Equals Resolved'.
'Failure After': e.g., '8 Hours'.
'Save & Close'.
7. Activate SLA: On the main SLA form, Click 'Activate'. Confirm 'Activate'.

Keys to Success: Best Practices & Your Questions

Essential Best Practices:

• Data Accuracy is Paramount: Accurate info = better reports & service.
• Professional Communication: Clear, empathetic interactions & notes.
• Leverage the Knowledge Base First: Save time, ensure consistent answers.
• Keep the Timeline Updated: Builds a complete, transparent case history.
• Ask Questions! No question is too silly.

References for Dynamics 365 Customer Service Module Learning:

1. Microsoft Learn (Official, Free, Self-Paced Training):

• Explore Dynamics 365 Customer Service: Link

• Work with cases in Dynamics 365 Customer Service: Link

• Get started with Dynamics 365 Customer Service: Link

• Training for Dynamics 365 Customer Service (Overview Page): Link

2. Microsoft Dynamics 365 Documentation:

 • Dynamics 365 Customer Service Documentation Home: Link

• Configure service-level agreements (SLAs): Link

3. Community and Forums:

• Dynamics 365 Community: Link (Look for the "Dynamics 365 Customer Service" section)

Tips for Freshers when using these resources:

• Start with Learning Paths: Microsoft Learn's structured learning paths are ideal for beginners.
• Hands-on Practice: Encourage them to have a trial or sandbox environment to practice alongside the learning
materials.
• Search Function: Both Microsoft Learn and the documentation have excellent search functions.
• Community for Specific Questions: If they encounter a specific problem or error, the community forums are a
great place to search for existing answers or post a new question.

Open Q&A