Microsoft Dynamics 365

Dynamics 365 Customer Service

What Dynamics 365 Customer Service does Microsoft Dynamics 365 Customer Service is the service application in Microsoft Dynamics 365. Every enquiry that reaches your service team, whether by email, phone, chat or through a customer portal, becomes a case with a clear owner, a priority and a deadline. The case stays open until the problem is solved, and nothing gets lost in a shared inbox or a spreadsheet along the way.

Service staff see everything they need on one screen: earlier cases, orders, contracts, the products the customer uses and what sales last discussed with them. Microsoft Copilot drafts replies, summarises long email threads and suggests matching articles from your knowledge base, so your team spends less time searching and more time solving.

40% shorter
processing time
Microsoft Solutions Partner

Certified Microsoft Solutions Partner in six areas

As a Microsoft Solutions Partner, we have extensive experience and proven expertise in six key areas

40% shorter handling time

Where AI takes over routine service work

Copilot supports service staff directly in the case: it summarises what has happened so far, writes a first draft of the reply, suggests knowledge articles and sums up a chat or call once it ends. New team members can pick up a case without reading through weeks of history first.

On top of that, Microsoft provides AI agents that work in the background. The Case Management Agent creates and updates cases from incoming emails and chats, fills in the details and follows up with customers. The Customer Intent Agent learns from past conversations what customers typically ask about, which improves routing and self-service. The Customer Knowledge Management Agent turns solved cases into draft knowledge articles for your team to review. And the Quality Evaluation Agent checks conversations against the standards you define and shows where coaching would help. The agents are paid for by use rather than per user.

40 %
shorter processing time
20 %
more enquiries resolved on first contact
15 %
fewer enquiries routed to the wrong person

In a Forrester-study from March 2024, commissioned by Microsoft, companies using Dynamics 365 Customer Service cut the average handling time of a request by 40 percent, solved 20 percent more requests on first contact and routed 15 percent fewer requests to the wrong person.

Two solutions working together

Customer Service or Contact Center: which one do you need?

Microsoft offers two products for customer service, and the difference matters when you plan a project. Dynamics 365 Customer Service is about the request itself: cases, deadlines, service contracts, the knowledge base and the customer portal. Dynamics 365 Contact Center is about the conversation channels: phone, live chat, messaging apps, voicebots and the routing of live conversations to available staff.

If most requests reach you by email or through a portal, Customer Service on its own is usually enough. If your team spends a large part of the day on the phone or in live chats, you add Contact Center, or choose Customer Service Premium, which includes both.

Customer Service

Handles cases and follow-up work.

Contact Center

Manages the conversation and the enquiry.

Microsoft Dynamics 365

Customer Service Premium includes both solutions

Bring Customer Service and Contact Center together in one solution to deliver seamless service across all channels.

Service processes first

Good service starts before the first case is created

Who handles which request? Which response times have you promised which customers? When does a case go to second-level support? collana, a certified Microsoft Solutions Partner, answers these questions with you first and then sets up Dynamics 365 Customer Service to match – followed by training and support once the system is live.
01

Areas of responsibility

Who handles which enquiry?

02

Response times

What response times have you agreed with each customer?

03

Second-level support

When is a case escalated to second-level support?

An overview of the features

What Customer Service handles day to day

Cases & service level agreements

Emails to your service address, portal submissions and calls turn into cases automatically, with category, priority and the customer already filled in. Service level agreements define how quickly each type of request must be answered and solved; the system warns before a deadline is missed and escalates if needed. Entitlements record how many support hours or cases a customer's contract covers.

Getting requests to the right person

Unified routing assigns each case based on rules you set: topic, language, product, customer status, the skills of your staff and their current workload. Urgent requests from key customers go to the front of the queue, and if a team is overloaded, cases move on to a backup group instead of waiting.

Knowledge base

Solutions to recurring problems are written down once as knowledge articles, reviewed and approved, and then suggested automatically in matching cases. The same articles can be published in your customer portal. With the Customer Knowledge Management Agent, new articles are drafted from solved cases, so the knowledge base keeps growing without extra effort.
Other key features

More services. For your customers and your team.

Customer portal & self-service

With a portal built on Microsoft Power Pages, customers submit requests, upload photos or documents and check the status of their cases themselves. A chat agent built with Copilot Studio answers common questions around the clock and hands over to a person, with the conversation so far, when it can't help.

Solving difficult cases together

Some problems can't be solved by one person. Swarming brings the right experts together in a Microsoft Teams chat linked to the case, so service staff don't have to pass the customer from department to department. Everything discussed stays documented on the case.

Reporting & service quality

Dashboards show open cases, backlog, response times and how well you are keeping to your service level agreements, by team, product or customer. Power BI adds deeper analysis, and the Quality Evaluation Agent checks conversations against your own quality criteria, so team leads know where to step in.

7 reasons to choose Dynamics Customer Service

Why Dynamics 365 Customer service is impressive

01

Every request has an owner and a deadline

No more emails that everybody reads and nobody answers. Each case is assigned, tracked and closed, and you can see at any time what is still open.

02

The whole customer on one screen

Earlier cases, orders, contracts and installed products are right next to the request. Your team doesn't have to ask the customer for information you already have.

03

Answers get faster over time

Every solved problem can become a knowledge article. The next person with the same question gets the answer sooner, whether from your team or from the portal.

04

Copilot and agents do the typing

Summaries, reply drafts, case updates and knowledge articles are prepared by AI. Your staff check and send, instead of writing everything from scratch.

05

Service and sales share one customer

Customer Service and Dynamics 365 Sales work on the same customer records. Service sees open deals, sales sees open complaints, and a request for an upgrade goes straight to the right seller.

06

Connected to your ERP

Thanks to the integration with Business Central or Dynamics 365 Finance & Supply Chain, service staff can view orders, deliveries, serial numbers and warranty details without having to switch between systems. This is where collana’s ERP expertise really comes into its own.

07

Start with email, add channels later

Many companies begin with email and a portal. Phone, chat and messaging can be added with Dynamics 365 Contact Center whenever you are ready, without replacing anything.
References

Customer Service Projects with collana

Most of these teams had the same starting point: a shared mailbox, a ticket tool that didn't talk to anything else and customer information spread across several systems. Today every request is tracked from the first email to the solution, and management can see how the service team is doing at a glance. Here are some of them.
Modernising customer service

Moving from shared inboxes and old ticket tools

A shared service inbox works while the volume is small. As requests grow, emails get answered twice or not at all, nobody knows how long customers are waiting and the knowledge of experienced staff leaves with them. Older ticket tools often solve part of the problem, but they don't know anything about orders, contracts or sales.

When you move to Dynamics 365 Customer Service, we carry over open cases, case history and existing knowledge articles. It is also a good moment to set clear response times, agree on categories and decide which requests can be answered by self-service.

If you already use Dynamics 365 Sales or Business Central, Customer Service completes the picture: sales, service and ERP work with the same customer data, from the first quote to the last warranty claim.

Shared mailboxes
and older ticketing systems
  • Emails are answered twice or not at all
  • No visibility into customer waiting times
  • Valuable knowledge is lost when staff leave
  • No connection to orders, contracts or sales
DYNAMICS 365 CUSTOMER SERVICE
  • Transfer open cases
  • Migrate existing case history
  • Use existing knowledge articles
Shared customer data
Dynamics 365 Sales
Dynamics 365 Customer Service
Dynamics 365 Business Central
Expertise for your customer service

What collana brings to a Customer Service project

The quality of customer service depends on processes and people as much as on software. collana combines Microsoft product expertise with years of experience in service organisations in different industries.

Certified across the Microsoft platform

collana is a Microsoft Solutions Partner in the areas of Business Applications, Data & AI, Digital & App Innovation, Infrastructure, Security and Modern Work. This means that customer service, integration with Teams and Outlook, portals, Power BI reports and security are all delivered by a single team.

Service processes first, configuration second

We start with how requests reach you today, who handles them and what you have promised your customers. From that, we define categories, routing rules and service level agreements, and only then configure the system.

Rolled out step by step

We usually start with one team or one channel, learn from the first weeks in live operation and then expand. Service staff are trained on real cases from their own daily work, not on generic examples.

Not sure where to begin?

In a short first conversation we look at how your service team works today and where Dynamics 365 Customer Service would help most. You get a clear recommendation for the next step.
FAQ

Questions we often hear about Dynamics 365 Customer Service

What is Dynamics 365 Customer Service and who is it for?

Dynamics 365 Customer Service is Microsoft's application for handling customer requests as cases, from the first contact to the solution. It suits any company with a service or support team, from a handful of people answering emails to large service organisations with several levels of support.

What is the difference between Customer Service and Contact Center?

Customer Service manages the request: cases, deadlines, contracts, knowledge base and portal. Contact Center manages the conversation channels: phone, live chat, messaging and voicebots, including routing and supervisor tools. Customer Service Premium combines both. Contact Center can also be used without Customer Service, together with another CRM.

What does Dynamics 365 Customer Service cost?

You pay a monthly fee per user. The main editions are Customer Service Professional for smaller teams with standard processes, Customer Service Enterprise with advanced routing, service level agreements and more room for customisation, and Customer Service Premium, which also includes the Contact Center channels. The AI agents are paid for by use via Copilot credits. Implementation and support depend on the size of the project, so we give you a realistic figure once we know your requirements.

Which AI features are included?

Copilot summarises cases and conversations, drafts replies and suggests knowledge articles. In addition, Microsoft offers AI agents for case management, recognising customer intent, maintaining the knowledge base and evaluating service quality. Which features are available depends on your licence, country and language.

Can our customers submit and track requests themselves?

Yes. With a customer portal built on Microsoft Power Pages, customers create requests, add attachments, follow the status and find answers in your knowledge base. A chat agent can answer common questions and hand over to your team when needed.

Does it work with our shared service mailbox?

Yes. Dynamics 365 Customer Service connects to Exchange, so emails to your service address are turned into cases automatically, and replies are sent from the same address. Your customers don't notice any change.

Can Customer Service be connected to Business Central or another ERP?

Yes. Dynamics 365 Customer Service works with Business Central and Dynamics 365 Finance & Supply Chain, and can be connected to other ERP systems via APIs and Power Platform connectors. Service staff then see orders, deliveries and invoices directly in the case.

How long does an implementation take?

A service team that starts with email, a standard case process and few integrations can be working in Dynamics 365 Customer Service within a few weeks. Portals, phone channels, ERP integration and migrating data from an old ticket system add time. Most projects go live in stages, one team or channel at a time.

Ready to take the next step with Dynamics 365 Customer Service?

Let's discuss your service processes, challenges and goals. In a short introductory call, we'll explore how Dynamics 365 Customer Service can support your team and identify the most sensible next step for your business – with no obligation.