The first three chapters of this course looked at Marketing, Sales, and Customer Service as if they were separate applications: one turns contacts into Leads, one turns a Lead into an Invoice, one turns a support request into a resolved Case. In practice, Sales and Service aren't separate at all — they're two views into the exact same underlying customer data, and this chapter is about seeing that connection clearly. It's the single most useful thing to understand about how Dynamics 365 CE is put together.
- Sales and Service both read and write the same Account and Contact records
- Those records live in Dataverse, the shared database underneath every D365 CE app
- A Case opened by Service can sit on the same Account a rep closed a deal on months earlier
- Who can see what across these shared records is a matter of security access, not data structure
One patient chart, two departments
Picture a medical clinic where the front desk and billing sit in different rooms, doing very different jobs. They could feel like two unrelated operations. But both work from the same patient chart — when billing opens a file, they can see which doctor the patient saw last month, because it was never two separate record sets, just two reasons to open the same one.
Sales and Customer Service in Dynamics 365 CE work exactly the same way. They feel like two different apps with two different jobs, but underneath, they both read from and write to the same Account and Contact records, stored in Dataverse — the shared database platform first introduced in the Get Started course's "What Is Dynamics 365 CE?" chapter. There was never a separate "Sales database" and "Service database."
Marketing hands off, then steps back
It's worth placing this alongside the full pipeline. As Chapter 2 covered, a Lead often starts life as a contact inside a Marketing Segment, worked through a Customer Journey until it becomes a Marketing Qualified Lead. Marketing's job ends at that handoff. This chapter's focus is on what happens next — how Sales and Service go on sharing the resulting Account and Contact records long after Marketing has moved on to the next campaign.
A worked example: from won deal to support call
Recall the sales pipeline from Chapter 1. A rep qualifies a Lead, creating an Account for the company and a Contact for the person, then works the resulting Opportunity through to a signed Order and a paid Invoice. The deal is won, the rep moves to the next prospect — from their point of view, that's the end of the story.
Six months later, that same company calls in with a support issue. A service rep creates a new Case for the problem — exactly as covered in Chapter 3 — and links it to an Account. But it isn't a new, empty Account. It's the very same Account record the sales rep worked six months earlier. The service rep isn't starting from zero: they can see the company's Contacts, and, with the right security access in place, the purchase history from the original deal, all sitting right there on the record they're already looking at.
| Record | Touched by Sales | Touched by Service |
|---|---|---|
| Account | Company behind a won Opportunity | Company a Case is linked to |
| Contact | Person who signed the Order | Person who reported the issue |
Why this matters, and where access fits in
This shared foundation is what makes a "360-degree view of the customer" more than a marketing phrase — it's a direct result of Sales and Service pointing at the same Account and Contact tables rather than keeping private copies. It raises a fair question: should every support rep see every past deal's financial details?
That's a matter of security access, not data structure. It's covered in its own dedicated course — Security & Access — which explains who can see what across these shared records, including cases where a rep might see a deal exists without seeing its full financial detail.
Where to go from here
You've now covered the three modules an end user interacts with most — Marketing, Sales, and Customer Service — and how they connect underneath. For a deeper dive into the sales and service process, see the existing tutorial D365 CRM Fundamentals & Configuration. And if you want to understand exactly who can see which of these shared records — and why — the Security & Access course picks up right where this one leaves off.