Your CRM is not for talking to your team

One of the most common mistakes we see in Dynamics 365 implementations is using the CRM as if it were an internal chat. Internal notes, activities between colleagues, calls logged between agents, timeline comments directed at another team member… The result: a client timeline polluted with internal noise that adds nothing when you need to review an account’s history.

A contact’s or account’s timeline should tell the story of your relationship with that client. If you fill it with internal messages, that story becomes unreadable.

There’s a better way to organize this. And it’s not complicated.

The principle: each tool for what it does best

The rule is simple:

Dynamics 365 = external communications. Emails to the client, calls with the client, meetings with the client. Everything the client sees or should see.
Microsoft Teams = internal communications. Discussions about a case, asking a colleague for help, coordinating with another department.
Dynamics 365 queues = routing and assignment. Cases arrive, get classified automatically, and are assigned to the right team or person without anyone having to distribute work manually.
Self-service portal = first filter. The client describes their problem, picks a category and priority, and the system does the grunt work before a human has to step in.

When each tool does its job, the result is a team that works asynchronously, without constant interruptions, and with a clean CRM.

Blueprint 1: Goodbye internal calls — Teams as your operations hub

The problem

An agent receives a case they can’t solve. They call a colleague. The colleague is on another call. They leave a message. The colleague calls back half an hour later. The agent is already working on something else. They play phone tag for half a day.

Meanwhile, the client waits.

The solution

Set up a Teams channel per team or functional area (Tier 1 Support, Tier 2 Support, Billing, etc.). When an agent needs help with a case:

Go to the relevant Teams channel
Write a message with context: case number, client, problem summary
Any available colleague responds when they can — without interrupting anyone
The conversation is documented in Teams, not in the client’s timeline

Why it works

You don’t interrupt anyone. Each person responds when they have a gap.
The conversation has context from the start. You don’t begin by explaining everything from scratch like on a call.
If the colleague who responded goes on holiday, someone else can read the thread and continue.
The client’s timeline stays clean: only real interactions with the client are recorded.

Configuration in Dynamics 365

You can integrate Teams with Dynamics 365 natively. From a case record, the agent can open a Teams chat linked directly to the record. The conversation is associated with the case in Teams but doesn’t clutter the Dynamics timeline.

Enable the integration from Advanced Settings > Microsoft Teams Integration in the Dynamics 365 admin centre.

Blueprint 2: Automatic queues — let the system distribute the work

The problem

A new case arrives. Someone on the team (usually a manager) has to read it, decide who should handle it, and assign it manually. This works with 10 cases a day. With 50, it’s a bottleneck. With 100, it’s unsustainable.

The solution

Set up queues in Dynamics 365 and routing rules so cases are assigned automatically based on criteria you define:

By issue type: billing cases go to the Billing queue, technical cases to Technical Support.
By priority: urgent cases go to a High Priority queue with more aggressive SLAs.
By product: if you sell multiple products, each can have its own queue with specialized agents.
By language: if your team supports multiple languages, cases are routed by the client’s language.
By client: VIP clients go to a dedicated queue with priority handling.

How to set it up

Create the queues in Dynamics 365: go to Settings > Service Management > Queues. Create one queue per team or category.
Add members to each queue: the agents who can work cases in that queue.
Configure routing rules: in Settings > Service Management > Routing Rules, create rules that evaluate case fields (type, priority, product, etc.) and assign to the correct queue.
Enable automatic routing: when a case is created (whether manually, by email, or from the portal), the rules fire and the case lands in the right queue.

The result

Nobody distributes work by hand. Agents open their queue, pick up the next available case, and work. No waiting, no depending on a manager being available to assign.

Blueprint 3: The sacred timeline — external communications only

The problem

You open a client record and the timeline has 200 activities. Of those 200, maybe 40 are real interactions with the client. The rest are internal notes, calls between colleagues, forwarded emails, and comments like “I’ve passed this to John”. To find the last email you sent the client, you have to wade through noise.

The solution

Establish a clear rule for your team:

In Dynamics 365, only log activities that involve the client.

Email sent to or received from the client: yes.
Call with the client: yes.
Meeting with the client: yes.
“I asked Pedro on Teams”: no. That goes in Teams.
Internal note about how to resolve the case: no. That goes in Teams or in an internal notes field on the case that doesn’t show in the main timeline.

How to implement it

Use the internal notes field on the case for comments that shouldn’t appear in the timeline. Dynamics 365 Customer Service has an “Internal Notes” field visible to agents but not logged as a timeline activity.
Set up Teams integration so agents discuss cases there. Each case can have a linked Teams chat.
Train your team on this distinction. It’s a cultural shift more than a technical one: the timeline belongs to the client, not the team.

Why it matters

When a new agent picks up an old case, they can read the timeline and in 2 minutes know everything that’s happened with that client. Without filtering through noise. That translates to better service, fewer mistakes, and faster resolutions.

Blueprint 4: Self-service portal — the smart first filter

The problem

A client has a problem. They call. An agent picks up, listens to the explanation, asks for details (“What’s your customer number?”, “Which product?”, “When did it happen?”), and spends 10 minutes creating a case with the basic information. Multiply this by 50 calls a day.

The solution

Set up a self-service portal with Power Pages (formerly Power Apps Portals) connected to Dynamics 365. The client logs in and creates their own case:

Guided form: the client picks a category (Technical issue, Billing, General enquiry, etc.), product, and describes the problem.
Required fields: the system forces the client to provide the minimum information an agent needs before they start working.
Automatic priority: based on the category and client type, the system assigns a priority automatically.
Knowledge base: before creating the case, the portal shows help articles related to what the client has described. If the client finds the answer, they don’t even create a case.
Confirmation and tracking: the client gets a case number and can check the status at any time from the portal.

What happens behind the scenes

When the client submits the form:

A case is created in Dynamics 365 with all fields already filled in.
Routing rules evaluate the case and send it to the correct queue.
The agent who picks up the case already has everything they need. No 10-minute calls to gather information.

The numbers

A well-configured self-service portal reduces incoming calls by 20% to 40%. For calls that become cases, creation time drops from 10 minutes (with a phone call) to 0 minutes (the client already did it). The agent can spend those 10 minutes solving the problem instead of documenting it.

Blueprint 5: Full flow — from portal to resolved case, without a single call

Let’s put it all together. Here’s the complete flow of a case from the moment the client has a problem to resolution, without anyone picking up the phone:

1. The client creates the case from the portal

The client logs into the self-service portal, selects “Technical issue”, chooses the product “Dynamics 365 Sales”, describes the problem (“Reports haven’t loaded since Monday”) and submits the form.

2. The system classifies and routes

Dynamics 365 receives the case with category = Technical, product = Sales, priority = Medium (automatic based on rules). Routing rules send it to the “Technical Support — Sales” queue.

3. The agent picks up the case from the queue

An agent on the Technical Support queue sees the new case, opens it and reads the full context without needing to call the client.

4. The agent needs help — goes to Teams

The agent isn’t sure about the cause. They open the Teams chat linked to the case and write in the Tier 2 Support channel: “Case #12345 — client reports Sales reports not loading since Monday. Has anyone seen something similar?”

A colleague responds 15 minutes later: “Yes, we looked at a similar case last week. It was a permissions issue on the dashboard. Check the user’s security roles.”

5. The agent resolves and communicates by email

The agent checks the permissions, finds the problem, fixes it, and sends an email to the client from Dynamics 365: “We’ve identified and fixed the issue with your reports. It was a permissions issue that got misconfigured. You should be able to access them now. Please confirm.”

That email appears in the case and contact timeline. Clean.

6. The client confirms from the portal

The client gets the email, verifies it works, and confirms from the portal that the issue is resolved. The case is closed.

Result

The client never had to call.
The agent was never interrupted by a phone call.
The case timeline has exactly what it needs: the resolution email and the client’s confirmation.
The internal conversation stayed in Teams, where it belongs.
The entire flow was asynchronous. Each person worked on their own time, without blocking anyone.

This is Dynamics 365 done right

It’s not about having the most expensive CRM or the prettiest portal. It’s about each piece doing what it’s supposed to do:

The portal collects the information.
Queues distribute the work.
Teams handles internal coordination.
Dynamics 365 records the relationship with the client.

When you set this up properly, your team stops putting out fires and starts doing real work. Asynchronous, organized, and with a clean timeline.

Want to set up these workflows in your Dynamics 365? Get in touch and we’ll help you design the architecture your team needs.