D365 CRM Terminology Kit
aka Jargon Jab for Relationship Wranglers
Get your dose of clarity with the Jargon Jab, the fast-acting antidote to CRM buzzwords, tailored for revenue surgeons and relationship specialists.
Table of Content
Get Free eBook
Join the clinic rounds — we’ll send you expert-approved remedies straight to your inbox.
D365 CRM Terminology Kit
aka Jargon Jab for Relationship Wranglers
Understanding the terminology of Microsoft Dynamics 365 (D365) CRM is your first triage before the complexity of customer engagement hits the ER. Whether you’re routing leads through Sales, triaging cases in Customer Service, dispatching technicians in Field Service, or orchestrating journeys in Customer Insights, a solid grasp of key terms is critical to avoid cross-departmental misdiagnoses.
Without it, teams may mislabel pipeline stages, misroute service queues, or confuse a Work Order with a Case, leading to configuration inflammation, reporting fevers, and full-scale adoption meltdowns. This Jargon Jab delivers targeted immunization against the most confusing and mission-critical D365 CRM terms. It won’t waste your time on general vocabulary like “Accounts” or “Contacts.” Instead, it zeroes in on the terms that are uniquely D365 CRM the kind that cause implementation migraines when misunderstood.
So roll up your sleeve, it’s time for your CRM terminology shot.
What Is Included in D365 CRM?
D365 CRM is not a single application. It is a family of customer engagement applications built on Microsoft Dataverse. All applications share core tables such as Accounts, Contacts, and Activities, as well as a common security and reporting framework. However, each application serves a distinct operational purpose.
Think of Dataverse as the hospital’s central records system, every department (Sales, Service, Field Service, Marketing) writes to the same patient chart. That’s powerful, but it also means a misconfiguration in one department can send the wrong vitals to another.
Failure to understand this structure often leads to misaligned expectations, incorrect licensing decisions, overlapping configuration, and ineffective training.
Application | Primary Focus | Core Capabilities | Primary Users |
D365 Sales | Revenue generation and opportunity management | Lead qualification, opportunity management, forecasting, quote management, activity tracking | Sales reps, sales managers, revenue operations |
D365 Customer Service | Case resolution and service operations | Case management, queue management, SLAs, entitlements, knowledge articles, omnichannel routing | Support agents, service managers, contact center teams |
D365 Field Service | Onsite service delivery and logistics | Work orders, scheduling, resource optimization, mobile execution, inventory tracking | Dispatchers, technicians, service operations teams |
D365 Customer Insights — Journeys | Marketing automation and engagement orchestration | Multi-step journeys, email/SMS automation, real-time triggers, lead scoring, event management | Marketing and demand generation teams |
D365 Customer Insights — Data | Customer data unification and 360-degree profiling | Data ingestion, identity resolution, segmentation, predictive insights | Data teams, marketing ops, strategic leadership |
Key Clarifications:
- Sales manages the sales lifecycle, not post-sale service execution or marketing automation.
- Customer Service manages customer issues but does not handle technician scheduling, that’s Field Service.
- Field Service connects to Customer Service but operates with its own scheduling and logistics logic.
- Journeys execute engagement flows, they are not simply email campaign tools.
- Customer Insights — Data prepares unified customer data; it does not execute campaigns.
Implementation Diagnostic Questions:
- Which CRM apps are in scope for your project?
- Who owns each application operationally?
- Where do workflows overlap between departments?
- How does data flow between your CRM apps and other systems?
D365 Sales — Commonly Confused Terms
The sales floor has its own dialect, and D365 adds a few plot twists. These are the terms that trip up even seasoned sellers, and when they get confused, your pipeline goes from healthy to critical.
Term | What People Think | What D365 Actually Means | Where It Bites |
Lead | Any potential customer | An unqualified potential customer. Leads exist in a pre-qualification state and must be explicitly qualified before they become Opportunities. | Conversion metrics, forecasting accuracy, pipeline governance |
Opportunity | Same as a Lead | A qualified deal with defined revenue potential. Opportunities represent real sales pursuits with estimated close dates and revenue amounts. | Revenue forecasting, pipeline reporting, win/loss analysis |
Pipeline Stage | Same as Forecast Category | Indicates progress in the sales process (e.g., Qualify, Propose, Negotiate, Close). Tracks where a deal sits in your methodology. | Sales process governance, deal progression tracking |
Forecast Category | Same as Pipeline Stage | Classifies revenue likelihood: Pipeline, Best Case, Commit, Closed. Used for executive revenue projections — different from process stage. | Executive forecasting, revenue planning |
Activity | A Task | The parent entity for all tracked interactions: Tasks, Appointments, Emails, Phone Calls. It is the umbrella, not a specific type. | Outlook sync, productivity reporting |
Task | Any Activity | A specific to-do item with a due date. One type of Activity — not the only type. | Work management, follow-up tracking |
Appointment | A Task with a date | A calendar-based meeting with start/end times, attendees, and location. Syncs bidirectionally with Outlook calendars. | Outlook sync, scheduling accuracy |
Sales Hub | A license tier | The model-driven application interface — the app users open and work in. It is an experience layer, not a license. | Licensing discussions, user experience planning |
Sales Enterprise | The app you open | A licensing tier that determines which features are available. Enterprise unlocks forecasting, sequences, and relationship intelligence. | Budget planning, feature availability |
Relationship Assistant | Copilot | AI-driven insights and reminders within Sales that surface relevant actions. Predates Copilot and is a distinct feature. | User expectations, feature training |
Lead vs Opportunity: The Great Pipeline Mix-Up
This is the single most common terminology confusion in D365 Sales. Both represent potential revenue, so users often skip the qualification step entirely, creating Opportunities from thin air, or leaving qualified deals stuck in Lead limbo. Here’s the clinical rule: a Lead is a name and a maybe. An Opportunity is a qualified pursuit with budget, timeline, and decision-makers identified. If your pipeline is full of “Opportunities” that have never been qualified, your forecast has a fever, and it’s not going down without intervention.
Forecast Category vs Pipeline Stage: Two Different Vital Signs
Pipeline Stage tells you where a deal is in your process. Forecast Category tells you how likely it is to close. A deal can be in the “Negotiate” stage (Pipeline Stage) but classified as “Best Case” (Forecast Category) because the buyer is still evaluating alternatives. When users confuse these, executives get unreliable revenue projections. Stage progression looks healthy, but the revenue commitment doesn’t match reality. Treat them as separate vital signs, both matter, and they measure different things.
Activity vs Task vs Appointment: The Classification Headache
Users log everything as a Task. Phone calls? Task. Meetings? Task. Emails? Task. But D365 has distinct Activity types for a reason: Tasks are to-do items, Appointments are calendar events that sync with Outlook, and Phone Calls track call details. When everything is a Task, your Outlook sync breaks and productivity reports become useless.
D365 Customer Service — Commonly Confused Terms
Customer Service has its own set of terminology traps — and when your support team misreads the chart, cases pile up, SLAs breach, and customers don’t get the care they need.
Term | What People Think | What D365 Actually Means | Where It Bites |
Case | Different from Incident | The business-facing label for a customer issue. In D365, Cases and Incidents are the same thing — Incident is the underlying system table name. | Customization, reporting queries, integration mapping |
Incident | Different from Case | The system/technical table name for what business users call a Case. Important to know during development, Power Automate flows, and API work. | Developer handoffs, data integration, custom reporting |
Queue | Where routing happens | A container that holds work items (Cases, Activities, etc.) waiting for assignment. Queues store work — they don’t decide where it goes. | Work distribution, workload visibility |
Routing Rule | Same as a Queue | Logic that determines which Queue or agent receives a work item based on criteria like priority, category, or customer tier. | Prevents idle work, ensures proper assignment |
SLA | Same as Entitlement | A Service Level Agreement, a performance target defining response and resolution time commitments (e.g., respond within 4 hours). | Compliance tracking, performance measurement |
Entitlement | Same as SLA | A contractual support agreement that defines what support a customer is entitled to (e.g., 20 support hours, phone + email channels). | Contract management, support scope |
Escalation | Reassigning a case | A rule-based, automated trigger that elevates a case when specific conditions are met (e.g., SLA breach approaching, VIP customer). | Governance, automated response |
Reassignment | Same as escalation | A manual ownership change, a human decision to move a case from one agent to another. | Workload balancing, agent availability |
Knowledge Article | Published once, done | Articles follow a lifecycle: Draft → Review → Publish → Expire. Only published articles are visible to agents and customers. | Content governance, self-service accuracy |
Case vs Incident: Same Patient, Two Names
This one catches people during customization and reporting. In the D365 interface, your support team works with Cases. But behind the scenes, the system table is called Incident. When a developer says “Incident entity,” they mean the same thing your agent calls a “Case.” If this isn’t clear during workshops, you’ll get requirements documents that reference two things that are actually one, and that’s a recipe for configuration confusion.
Queue vs Routing Rule vs Workstream: The Traffic Control Trio
Think of it this way: a Queue is the waiting room. A Routing Rule is the triage nurse who decides which waiting room you go to. A Workstream is the hospital’s operational policy that defines how many patients each department can handle, which channels they accept, and how work gets distributed. When teams confuse these three, work items sit idle, capacity limits get ignored, and omnichannel routing breaks down.
SLA vs Entitlement: Performance Target vs Support Contract
An SLA says “we will respond within 4 hours.” An Entitlement says “this customer gets 20 hours of phone support per quarter.” One measures your speed; the other tracks what the customer has paid for. Confusing them leads to either over-promising service levels or failing to track contractual obligations.
D365 Field Service — Commonly Confused Terms
Field Service is where the digital world meets the physical one — and terminology mix-ups here don’t just cause reporting errors. They send the wrong technician to the wrong site with the wrong tools. Let’s make sure your dispatch board is reading the right chart.
Term | What People Think | What D365 Actually Means | Where It Bites |
Work Order | Same as a Case | An onsite execution record that defines the job to be performed, including tasks, products, and services required. Created when physical service delivery is needed. | Service-to-field handoff, job execution tracking |
Case | Same as Work Order | A customer issue logged in Customer Service. A Case may or may not result in a Work Order — only when onsite service is required. | Workflow design, cross-app handoffs |
Booking | Same as Assignment | A calendar reservation that blocks a specific time slot for a resource. Bookings have start/end times and appear on the Schedule Board. | Schedule accuracy, resource capacity |
Assignment | Same as Booking | The act of selecting which technician or resource will handle a Work Order. Assignment comes first; Booking locks the calendar. | Resource selection, dispatch logic |
Resource | Same as User | A schedulable entity — can be a person, a piece of equipment, a vehicle, or a facility. Not all Resources are Users, and not all Users are Resources. | Scheduling configuration, capacity planning |
User | Same as Resource | A security identity in the system with login credentials and role-based permissions. Users become Resources only when explicitly configured for scheduling. | Security model, access control |
Requirement | Same as Work Order | Defines the needed skills, time window, and location for a job. Requirements drive the scheduling engine — they tell the system what kind of resource is needed. | Booking automation, skill matching |
Incident Type | Just a category label | A template that pre-populates a Work Order with standard tasks, products, services, and duration estimates. Think of it as a prescription template for common procedures. | Standardization, work order consistency |
Schedule Board | A simple calendar | A visual dispatch tool that shows resources, bookings, work orders, routes, and real-time map views. Used by dispatchers to manage and optimize daily operations. | Operational efficiency, real-time dispatch |
Work Order vs Case: The Handoff That Trips Everyone Up
A Case lives in Customer Service, it’s the record of a customer’s problem. A Work Order lives in Field Service, it’s the job ticket for physical work. Not every Case becomes a Work Order (some issues are resolved remotely), and Work Orders can also be created independently for preventive maintenance. The confusion happens at the handoff: when should a Case generate a Work Order? Getting this workflow wrong means either sending technicians to issues that could have been resolved over the phone or leaving customers waiting for onsite help that was never dispatched.
Booking vs Assignment: Calendar Slot vs Resource Selection
Assignment is the who, picking the right technician based on skills, location, and availability. Booking is the when and who, locking a specific time slot on the calendar for a specific resource. You can assign a resource without booking a time (it’s on their list but not scheduled), or you can book a time slot that drives the assignment. When teams conflate these, schedules become unreliable and dispatch accuracy drops.
Resource vs User: Not Everyone Who Logs In Can Be Scheduled
A User is anyone with a login. A Resource is anything the scheduling engine can book — people, equipment, rooms, vehicles. Your finance director is a User but not a Resource. Your crane is a Resource but not a User. When these get mixed up during configuration, the Schedule Board either shows people who shouldn’t be there, or hides assets that need to be dispatched.
D365 Customer Insights — Commonly Confused Terms
Customer Insights is where marketing meets data science — and the terminology reflects that duality. These terms trip up marketing teams and data teams alike, often because the same word means different things depending on which side of the house you’re on.
Term | What People Think | What D365 Actually Means | Where It Bites |
Journey | Same as Campaign | An automated, multi-step engagement flow triggered by customer actions or attributes. Journeys react to behavior in real time and can span multiple channels. | Execution clarity, marketing automation design |
Campaign | Same as Journey | A marketing initiative container used to organize and track related activities. Campaigns group efforts; Journeys execute the actual customer engagement. | Budget tracking, initiative organization |
Real-Time Journey | Same as Outbound Journey | An event-triggered engagement that responds immediately when a customer takes an action (e.g., opens an email, visits a page, submits a form). | Architecture decisions, response time expectations |
Outbound Journey | Same as Real-Time Journey | A batch-scheduled journey that sends communications to a predefined audience at a set time. Think mass email campaigns vs triggered responses. | Campaign planning, send timing |
Segment | Same as Dynamic Segment | A static or rule-based group of customers used for targeting. Static segments are manually defined; dynamic segments auto-update based on criteria. | Targeting accuracy, list management |
Dynamic Segment | A regular list | An auto-updating, rule-based group that continuously recalculates membership based on live data. Customers enter and exit the segment as their data changes. | Real-time targeting, personalization |
Profile | Same as Contact | A unified, multi-source customer record created by Customer Insights — Data. Profiles merge data from CRM, web analytics, POS, and other systems into one view. | Data unification, 360-degree customer view |
Contact | Same as Profile | A CRM record representing an individual person. Contacts are one data source that feeds into a unified Profile, but a Profile contains much more. | Data architecture, integration planning |
Data Unification | Just importing data | The process of matching and merging records from multiple sources into a single customer profile using AI-powered identity resolution. | Accurate segmentation, deduplication |
Consent Management | Email opt-out tracking | A comprehensive system for tracking communication permissions across all channels (email, SMS, push, custom) in compliance with GDPR, CCPA, and other regulations. | Regulatory compliance, multi-channel permissions |
Journey vs Campaign: Execution vs Organization
A Campaign is the umbrella; it’s how you organize, budget, and track a marketing initiative. A Journey is the engine; it’s the automated sequence of touchpoints that actually reaches the customer. You can have multiple Journeys running under one Campaign, but a Journey can also exist independently. When marketing teams think “Campaign” means “automated email sequence,” they miss the orchestration power of Journeys entirely.
Real-Time vs Outbound: Event-Driven vs Batch-Scheduled
Real-Time Journeys fire the moment something happens: a form submission, a purchase, a page visit. Outbound Journeys send to a predefined list at a scheduled time. Choosing the wrong type means either bombarding customers with delayed batch sends when they expect instant responses, or wasting real-time triggers on communications that don’t need immediacy. Note: Microsoft is phasing out the legacy Outbound Marketing module, so all new work should use Real-Time Journeys.
Profile vs Contact: The Unified View vs the CRM Record
A Contact in D365 CRM is a single record about a person. A Profile in Customer Insights — Data is a unified, enriched view that merges data from CRM, web analytics, loyalty programs, POS systems, and more into one comprehensive customer identity. Profiles are created through data unification and identity resolution — they represent everything you know about a person, not just what’s in CRM.
How to Use This Guide
This guide is your terminology first-aid kit. Keep it handy for:
- Pre-implementation workshops, align stakeholders on vocabulary before configuration begins
- Training sessions, give users the right mental models before they touch the system
- Executive alignment meetings, ensure leadership understands what each CRM app does (and doesn’t do)
- Reporting discrepancies, when the numbers don’t add up, check if the terms were understood correctly
- Cross-department handoffs, Sales to Service, Service to Field Service, terminology alignment prevents dropped balls
- Licensing discussion, knowing the difference between an app, a hub, and a license tier saves costly mistakes
Remember: terminology confusion is the silent saboteur of D365 projects. It doesn’t announce itself with error messages — it shows up as misaligned requirements, broken reports, and frustrated users. This guide is your preventive care.
