# Introduction to Dynamics 365 Customer Engagement Apps

> Chapter 1 of the Courseiva MB-910 curriculum — https://courseiva.com/learn/mb-910/introduction-to-dynamics-365-customer-engagement-apps

**Official objective:** none — Understand the core concepts and common features of Dynamics 365 customer engagement apps (Sales, Customer Service, Field Service) and their integration with Microsoft 365.

## Introduction

Customer engagement apps are the digital tools businesses use to manage every interaction they have with a customer, from the first hello to the final follow-up. For someone studying for the MB-910 exam, understanding these apps is essential because they form the core of how modern companies sell, support, and service their products. This chapter will explain exactly what Dynamics 365 Sales, Customer Service, and Field Service do, how they work together, and why they matter for the exam.

## The Office Building Maintenance Team Analogy

A customer relationship management (CRM) system like Dynamics 365 Customer Engagement is the central operations desk for a large office building. Before that desk existed, each department – sales, maintenance, and guest services – worked from separate notebooks. The sales team kept their own list of tenants and their lease renewal dates on a whiteboard. The maintenance crew had a folder of work orders, updated by hand whenever a lightbulb needed changing or a leaky tap was reported. Guest services used a pile of sticky notes to track visitor requests for conference room bookings or extra chairs.

Whenever a tenant called to say, 'The heating in conference room 3A isn't working,' the receptionist had to shout across the hall to find the right maintenance worker, then check the whiteboard to see if that room was even booked for an important client meeting that afternoon. Information was scattered and slow. Now, the central operations desk runs a single digital system. When the tenant calls about the heating, the operator logs a service ticket in one shared application. That ticket instantly appears on the maintenance team's screen, showing the room number, the problem, and the priority. The same ticket automatically checks the sales team's calendar for upcoming meetings in that room, so maintenance knows it must fix the heat before the 2pm client presentation. All departments see the same real-time picture. That is what Dynamics 365 Customer Engagement does for a business: it connects sales, customer service, and field service into one unified system of record.

## Core explanation

Dynamics 365 Customer Engagement apps are a collection of software tools from Microsoft that help a business manage its relationships with customers. The term 'customer engagement' covers every single touchpoint a company has with a person or another company who buys from them. This includes the initial marketing that attracts a buyer, the sales process that convinces them to purchase, the customer service they receive after buying, and any on-site technical support or repairs they might need.

Before these apps existed, businesses typically kept customer information in many different places. A salesperson might have a spreadsheet on their laptop with their own list of leads. The customer service team might use a separate email inbox to track complaints. The field service technicians might write work orders on paper forms. When a customer called to ask about the status of a repair, the person on the phone often had to call or email several colleagues to find an answer. This was slow, frustrating, and prone to errors.

Dynamics 365 fixes this by putting all customer information into a single, shared database that every employee can access. This database is called the Common Data Model, and it is the foundation underneath all the customer engagement apps. It stores things like customer names, addresses, contact details, past purchases, open support tickets, and scheduled service visits in a consistent way. Because every app draws from the same pool of data, a salesperson, a support agent, and a field technician all see the exact same information about any given customer. This shared view is often called a '360-degree view of the customer.'

The three main apps you must know for MB-910 are:

- Sales: This app helps businesses manage the process of finding new customers, turning them into paying customers, and keeping them happy. It includes tools for tracking leads (potential customers), managing opportunities (deals that are likely to close), creating quotes, and managing sales orders. It also includes features like email integration and AI-powered insights that suggest which deals are most valuable.
- Customer Service: This app manages everything that happens after a sale, when a customer has a question, a problem, or needs help. It includes a case management system where every customer request becomes a 'case' that is tracked from creation to resolution. It also includes tools for creating a self-service knowledge base (articles customers can read on their own) and a service scheduling feature for booking appointments.
- Field Service: This app handles work that happens at a customer's physical location, such as repairs, installations, or inspections. It includes tools for scheduling technicians, dispatching them to jobs, tracking inventory of spare parts, and capturing the technician's work and signatures on a mobile device. It often integrates with Internet of Things (IoT) sensors that can alert the system when a machine is about to break down, so a technician can be sent before the customer even notices a problem.

These three apps are not separate islands. They work together. For example, a salesperson might close a deal for a new piece of equipment. That sale automatically creates a customer record. If the equipment breaks a year later and the customer calls for service, the customer service agent can immediately see the original sales order, the warranty terms, and the equipment model without asking the customer. If a field technician needs to go on-site, the Field Service app can see the case details from Customer Service and the equipment purchase history from Sales, all in one place.

The apps also integrate deeply with Microsoft 365, which includes tools like Outlook, Teams, and SharePoint. For example, when a salesperson receives an email in Outlook from a potential customer, Dynamics 365 can automatically link that email to the correct lead record. When a customer service agent uses Microsoft Teams to chat with a colleague about a tricky support case, a record of that conversation can be saved to the case file. This integration saves time and keeps all information connected.

For the MB-910 exam, you do not need to know how to configure these apps. You do need to understand what each app does, how they work together, and the core concept of the shared customer database. Think of it as learning the roles of different departments in a company, not how to manage the company itself.

## Real-world context

Imagine a medium-sized company called 'BrightHome Appliances' that sells and services household heating systems. Before using Dynamics 365, BrightHome operated like this:

- The sales team used a shared spreadsheet on a network drive to track potential customers who had enquired about new boilers. The spreadsheet was often a mess because two salespeople might update the same row at the same time, overwriting each other's notes.
- The customer service team handled phone calls from homeowners whose boilers had broken down. They wrote down the problem on a paper form and then physically walked the form to the dispatcher, who scheduled a technician.
- The field service technicians carried paper work orders. When they finished a job, they wrote down what parts they used and handed the paper back to the office. The office staff then typed the information into a separate accounting system to generate invoices.

This system was slow. A homeowner might call for a repair on Monday, but the service agent could not tell them when the technician would arrive because the dispatcher had to manually check the technicians' paper schedules. When a technician arrived and found they needed a spare part not on their van, they had to call the office, who had to check a stock list on another spreadsheet. A simple repair could take three days and multiple phone calls.

Now BrightHome implements Dynamics 365 Customer Engagement. Here is what happens step by step:

1. A homeowner calls to enquire about a new boiler. The sales agent enters their details into Dynamics 365 Sales. The system creates a 'lead' record with the homeowner's name, address, phone number, and notes about the conversation. The agent sends a quote from within the same screen.

2. The homeowner agrees to the quote. The sales agent converts the lead into an 'opportunity' and then into a 'won opportunity', which automatically generates a customer record for the homeowner and an order for the new boiler. The system also creates a 'case' in Customer Service for the installation appointment.

3. A year later, the boiler starts making a strange noise. The homeowner calls for service. The customer service agent opens Dynamics 365 Customer Service and searches for the homeowner's phone number. The system displays the full customer record, including the boiler model, installation date, and warranty details. The agent creates a new 'case' describing the noise.

4. The dispatcher sees the new case in Field Service. The system suggests available technicians based on their skills and location. The dispatcher schedules the appointment, and the system automatically sends the homeowner a text message with the technician's name and expected arrival time. The technician receives the work order on their mobile phone app.

5. The technician arrives, diagnoses the problem, and sees that a specific part is needed. They check the 'Service Asset Management' section in their Field Service mobile app, which shows the full parts inventory on their van and at the warehouse. They replace the part and record the work, including the part used and the time spent, directly on their tablet. The system automatically sends the homeowner an invoice via email and updates the boiler's service history.

This entire process happens without anyone writing down information more than once. The data flows seamlessly between Sales, Customer Service, and Field Service. The homeowner gets fast, accurate service, and BrightHome avoids the costs of lost sticky notes and duplicate data entry.

## Exam focus

The MB-910 exam will test your understanding of the purpose and high-level capabilities of the three main customer engagement apps. You do not need to memorise every feature, but you must know which app is used for which scenario. The exam loves to present a short business problem and ask which app solves it.

Here are the specific topics you must be prepared for:

- The core purpose of each app: Sales manages the sales pipeline (leads to orders), Customer Service manages cases and support, Field Service manages on-site work orders and technicians.
- The concept of a 'customer engagement app' as part of the larger Dynamics 365 ecosystem. Be able to distinguish it from the finance and operations apps (like Dynamics 365 Finance) which the exam also covers but is not the focus of this chapter.
- Integration with Microsoft 365: The exam frequently asks how Dynamics 365 connects with Outlook (email tracking, contact sync) and Teams (conversation linking). Know that this integration is built-in and automatic once configured.
- The Common Data Model (now called Microsoft Dataverse): Understand that it is the shared database underneath all the apps. The exam may not use the name 'Dataverse' but will describe a 'centralised data store' or 'common data platform'. Any time the exam mentions a single source of truth for customer data, that is Dataverse.
- Security roles and permissions: Know that access to records is controlled by roles like 'Salesperson' or 'Customer Service Representative', and that you can limit what someone sees based on their role. The exam might ask who can edit a quote (a salesperson) vs who can close a service case (a customer service agent).

Common traps the exam sets:

- Confusing Sales and Customer Service: The exam might describe a scenario where a customer calls to complain. Many beginners default to 'Sales'. The correct answer is 'Customer Service' because the issue is a post-sale problem, not a new purchase.
- Mixing Field Service with Customer Service: A scenario involving a repair at a customer's house is Field Service, not the call centre Customer Service app. Customer Service is the app that handles the phone call; Field Service manages the technician's dispatch. Sometimes the correct answer is both together, but the question usually asks for the primary app.
- Thinking Customer Service and Field Service are the same: They are separate apps. Customer Service is for call centre agents. Field Service is for mobile workers. Know the distinction.

Specific terms to memorise for the exam:

- Lead: A potential customer who has shown interest but has not been qualified.
- Opportunity: A qualified lead that has a high chance of becoming a sale, with a potential dollar value.
- Case: A single customer service issue, such as a complaint, a question, or a request for help. It is tracked from creation to resolution.
- Work Order: A task assigned to a field technician for a specific job at a specific location.
- Knowledge Base: A collection of articles that customers and agents can search to find answers to common questions without calling.

The exam also expects you to know the value proposition: why would a business use these apps instead of spreadsheets? The answer is always about efficiency, accuracy, a single source of truth, and improved customer experience. Phrase your answers in those terms when taking the test.

## Step by step

1. **Step 1: A customer makes contact** — A potential customer visits the company website and submits a form asking about a product. This action automatically creates a 'lead' record in Dynamics 365 Sales. The lead stores the customer's name, email, phone number, and the product they are interested in. This is the first moment the system captures data.
2. **Step 2: The sales team qualifies the lead** — A salesperson reviews the lead, calls the customer, and determines if they are ready to buy. If yes, they 'qualify' the lead in Dynamics 365 Sales, which automatically converts the lead record into an 'opportunity' and creates an 'account' for the customer company. The opportunity now has a budget, timeline, and expected revenue value. This step moves the customer from 'interested' to 'active negotiation'.
3. **Step 3: The sale is closed** — The salesperson sends a quote from within Dynamics 365. The customer agrees to the price. The salesperson marks the opportunity as 'won'. The system automatically creates an 'order' record and a 'customer record' if one does not already exist. It also triggers any downstream actions, such as creating a service contract or sending a welcome email. This step formalises the customer relationship.
4. **Step 4: The customer needs support** — Six months later, the customer calls with a problem. The customer service agent opens Dynamics 365 Customer Service and searches for the customer. They see the order history, warranty dates, and previous service interactions. They create a new 'case' describing the issue. The case is assigned a priority and a queue. This step shows how shared data makes support faster.
5. **Step 5: A field technician is dispatched** — If the case requires an on-site visit, the agent transfers the case to the Field Service dispatcher. The dispatcher sees the customer's location, the required skills, and available technician schedules. They schedule a 'work order' and assign a technician. The technician receives the work order on a mobile app, including directions, parts needed, and the customer's history. This step demonstrates the hand-off between Customer Service and Field Service within the same system.

## Comparisons

### Dynamics 365 Sales vs Dynamics 365 Customer Service

**Dynamics 365 Sales:**
- Focuses on pre-sale activities: lead generation, opportunity management, and quoting.
- End goal is to convert a prospect into a paying customer and close a deal.
- Tools include pipeline views, quote creation, and sales analytics.

**Dynamics 365 Customer Service:**
- Focuses on post-sale activities: case management, issue resolution, and support.
- End goal is to resolve a customer's problem or answer their question.
- Tools include case queues, knowledge base articles, and service-level agreements (SLAs).

### Customer Service (App) vs Field Service (App)

**Customer Service (App):**
- Designed for call centre agents who handle phone, email, or chat requests.
- Work is done remotely, typically from an office desk.
- Primary record type is a 'case' that tracks a customer issue.

**Field Service (App):**
- Designed for mobile technicians who travel to customer locations.
- Work is done physically on-site (repairs, installations, inspections).
- Primary record type is a 'work order' that schedules and tracks a job.

### Lead vs Opportunity

**Lead:**
- An unqualified potential customer who has shown interest (e.g., filled a form).
- No revenue value is assigned yet; it is just a suspect.
- Conversion to opportunity is not guaranteed; many leads are discarded.

**Opportunity:**
- A qualified lead that has been vetted and is likely to buy.
- Has an estimated revenue value and a close date.
- Represents a real deal in the sales pipeline that is actively being worked.

### Common Data Model (Dataverse) vs Separate Spreadsheets

**Common Data Model (Dataverse):**
- A single, shared database that all apps use, ensuring data consistency.
- Data is entered once and is immediately available to all users.
- Supports security roles to control who can see what.

**Separate Spreadsheets:**
- Each department maintains its own file, leading to duplication and errors.
- Data must be manually copied or emailed between teams.
- No inherent security or version control; overwrites are common.

## Diagram

_This flowchart shows the customer journey from initial contact through sales, support, and field service, all connected by a single shared database (Dataverse)._

```mermaid
flowchart TD
    A[Customer Makes Contact] --> B[Lead created in Dynamics 365 Sales]
    B --> C[Sales qualifies lead -> Opportunity]
    C --> D[Deal won -> Order created]
    D --> E[Customer Record created in Dataverse]
    E --> F[Customer calls for support]
    F --> G[Case created in Dynamics 365 Customer Service]
    G --> H[On-site repair needed?]
    H -- Yes --> I[Work Order in Dynamics 365 Field Service]
    I --> J[Technician dispatched via mobile app]
    H -- No --> K[Resolved via knowledge base or phone]
    J --> L[Job completed - record updated]
    K --> L
```

## Common misconceptions

- **Misconception:** Dynamics 365 Customer Engagement is just a fancy contact list. **Reality:** It is a full suite of applications that manage the entire lifecycle of a customer relationship, from marketing and sales to service and field operations, all built on a shared database. (Beginners often see CRM as 'an electronic rolodex' because the most visible feature is storing contact details. They miss the complex workflow automation and integration capabilities.)
- **Misconception:** Field Service and Customer Service are the same app and can be used interchangeably. **Reality:** Customer Service handles interactions over the phone or web (call centre activities), while Field Service handles physical, on-site work like repairs and installations. They are separate apps that often work together but have different primary functions. (Both words contain 'service', so beginners lump them together. The exam tests the distinction carefully.)
- **Misconception:** You must be a programmer or IT expert to use Dynamics 365. **Reality:** The apps are designed for business users like salespeople, service agents, and dispatchers. No coding is required for everyday use. Configuration is done by a low-code or no-code administrator, not by end users. (Many beginners assume any enterprise software requires programming skills because they hear terms like 'customisation' and 'integration'. In reality, most daily tasks are point-and-click.)
- **Misconception:** Dynamics 365 Customer Engagement apps replace Microsoft Outlook and Teams. **Reality:** They integrate with Outlook and Teams, not replace them. You can send emails from within Dynamics 365, but they still go through your Outlook account. Teams conversations can be linked to records, but Teams itself remains separate. (Students often assume Microsoft would want to replace old tools with new ones. In fact, the strategy is deep integration so that users do not have to switch between applications.)
- **Misconception:** The Sales app is only for making phone calls to prospects. **Reality:** It manages the entire sales process, including lead qualification, opportunity management, quote creation, order processing, and post-sale relationship management. Cold calling is a tiny part of what Sales does. (Popular media often portrays sales as only telemarketing. The exam expects you to understand the broader pipeline management capabilities.)
- **Misconception:** All three customer engagement apps require separate databases that must be synchronised manually. **Reality:** They all share one underlying database called Microsoft Dataverse. Any data entered in Sales is instantly available in Customer Service and Field Service without any manual sync. (Older software systems really did have separate databases. Beginners carry that expectation to Dynamics 365, not realising the entire point is to eliminate silos.)

## Key takeaways

- Dynamics 365 Customer Engagement includes three primary apps: Sales, Customer Service, and Field Service, each serving a distinct part of the customer lifecycle.
- All customer engagement apps share a single underlying database called Microsoft Dataverse, which provides a single source of truth for all customer data.
- Sales manages the process of finding and converting leads into paying customers, including opportunity tracking and quote generation.
- Customer Service handles post-sale support by tracking every customer issue as a 'case' from creation to resolution.
- Field Service dispatches and manages on-site work orders for technicians who perform repairs, installations, or inspections at a customer's location.
- The apps integrate natively with Microsoft 365 tools like Outlook and Teams, allowing users to link emails and conversations directly to customer records.
- You do not need programming skills to use these apps; they are designed for business users and configured by low-code administrators.
- On the MB-910 exam, expect scenario-based questions that ask you to identify which app solves a given business problem.

## FAQ

**What is the difference between Dynamics 365 Sales and Dynamics 365 Customer Service?**

Sales is for the buying journey: finding leads, closing deals, and managing orders. Customer Service is for after the sale: handling support requests, complaints, and questions through case management.

**Do I need to know how to code to use Dynamics 365 Customer Engagement apps?**

No. The apps are designed for business users like salespeople and service agents. You use buttons, forms, and views — no programming is needed to perform your daily job. Customisation can be done by an administrator using point-and-click tools.

**How do Dynamics 365 and Microsoft 365 work together?**

They integrate natively. For example, you can track emails from Outlook in Dynamics 365, link Teams chats to customer records, and share documents from SharePoint. The integration means you rarely have to leave one system to use the other.

**What is a 'case' in Dynamics 365 Customer Service?**

A case is a digital record of a single customer service issue, such as a complaint, a question, or a request for technical help. It includes all details of the interaction and is tracked until it is resolved or closed.

**Can I use Dynamics 365 Customer Engagement on a mobile phone?**

Yes. Microsoft provides a mobile app for Dynamics 365 that works on iOS and Android. Field Service technicians especially rely on the mobile app to receive work orders, capture signatures, and update job status while on site.

**What is the Common Data Model (Dataverse) in simple terms?**

It is one shared database that all Dynamics 365 apps use. Instead of each app having its own storage, they all read from and write to the same place, so everyone sees the same customer information.

## Check your understanding

1. **Which Dynamics 365 app would a business use to manage the process of sending a technician to a customer's house to repair a broken washing machine?**

   Answer: Dynamics 365 Field Service, because it manages on-site work orders and technician dispatch.

2. **What is the name of the shared database that underlies all Dynamics 365 Customer Engagement apps?**

   Answer: Microsoft Dataverse (formerly known as the Common Data Model).

3. **A customer calls to complain about a faulty product they bought last week. Which app should the person who answers the phone use to track this issue?**

   Answer: Dynamics 365 Customer Service, using a 'case' record to track the complaint from creation to resolution.

4. **What is the difference between a 'lead' and an 'opportunity' in Dynamics 365 Sales?**

   Answer: A lead is an unqualified potential customer who has shown initial interest, while an opportunity is a qualified lead that has a high likelihood of resulting in a sale and has an estimated revenue value.

5. **How does Dynamics 365 integrate with Microsoft Outlook?**

   Answer: Emails and appointments in Outlook can be automatically linked to the appropriate customer record (lead, contact, or account) in Dynamics 365, so the communication history is stored in one place without manual copy-pasting.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/mb-910/introduction-to-dynamics-365-customer-engagement-apps