ARTICLE · DYNAMICS 365 · CUSTOMER SERVICE

Ticketing and helpdesk with Dynamics 365 Customer Service

In short: Dynamics 365 Customer Service is a complete ticketing system. Every request becomes a case, queues collect tickets per team, SLAs watch the deadlines, and the knowledge base answers both service reps and customers. Tickets can come from e-mail, a customer portal, SMS, chat, Teams or a phone call. It pays off most when customer service works with the same customer data as sales and Microsoft 365 is already in place.

In short

  • Ticket = case: with an owner, deadline, history and resolution, linked to the customer record.
  • Queues and routing: tickets are collected per team; with an Enterprise licence unified routing assigns them automatically by availability, capacity or skill.
  • SLAs and entitlements: first response and resolution deadlines with warnings, and the customer’s contractual allowance.
  • Channels: e-mail, portal, SMS, chat, Teams, phone – the real-time channels come from Dynamics 365 Contact Center.
  • Internal IT helpdesk too: the same ticketing for your own employees’ requests.

Author: Norbert Madarász, Managing Director and Partner · Updated: 14 November 2026

How does ticketing work in Dynamics 365?

  1. Intake: whatever the channel, the request becomes a case and lands in the right queue.
  2. Assignment: the team lead or unified routing assigns it to the right person.
  3. Resolution: the rep sees the customer history and knowledge articles next to the case and replies by e-mail, SMS or chat from there.
  4. Escalation: when the deadline approaches, the SLA warns; the expert is pulled in via Teams chat, straight from the record.
  5. Closure: the resolution is recorded, the customer is notified, optionally with a satisfaction survey.

The feature breakdown by licence (Professional, Enterprise, Premium) and list prices are covered in our Dynamics 365 Customer Service article.

Channels: e-mail, portal, SMS, chat, Teams, phone

ChannelHow it becomes a ticketWhat to watch
E-mailserver-side synchronization connects the mailbox to Dynamics 365; an automatic record creation rule turns the e-mail into a case, and replies are matched to the existing case via the e-mail headersthe queue address must be in To or Cc; an address in Bcc is not processed
Web form, customer portalthe customer logs the ticket and sees its statusa Power Pages portal, together with the knowledge base articles
SMSthe Dynamics 365 Contact Center SMS channel (Azure Communication Services, Twilio or Infobip), or an integration with your own SMS provideroutbound messages start from a Power Automate flow; group SMS is not supported by the channel
Chat, social channelson Contact Center channels (chat, WhatsApp, Teams and others) the conversation is linked to the ticketreal-time channels need a Contact Center licence
Phonethe call becomes a case and the transcript is stored on the recordsee our article on Teams telephony

According to Microsoft Learn, the Contact Center SMS channel currently works with Azure Communication Services, Twilio and Infobip; the old Telesign channel was retired in October 2024. If the company already works with a local SMS provider, that can be connected too: a plug-in or API integration sends and receives the messages, and the SMS is stored as an activity on the ticket timeline.

On the phone channel, Teams telephony and call recording: Teams Phone and Dynamics 365 Contact Center. On the customer portal: customer portal with Power Pages.

Teams in customer service

From the ticket the rep starts a Teams chat with an expert, or links an existing chat to the record, so internal coordination stays with the ticket. According to Microsoft Learn, the former “swarming” (preview) feature was retired on 8 February 2026, and Microsoft recommends the embedded Teams chat instead. In Contact Center, Teams can also be set up as a customer channel.

Standalone helpdesk software or Dynamics 365?

CriterionStandalone helpdesk toolDynamics 365 Customer Service
Customer dataits own customer list, needs integration with the CRMthe same customer, contract and history as in sales
Rolloutfast, with ready-made templatesneeds analysis and configuration, but the process fits the way the company works
Customisationwithin the vendor’s limitsown tables and columns, Power Automate, plug-ins, Power Apps
Channelsdepends on the vendore-mail, portal, and with Contact Center chat, SMS, phone, Teams
Better whensmall team, simple e-mail ticketing, no Microsoft CRMDynamics 365 or Microsoft 365 is already in place and service is linked to sales, contracts or field service

If ticketing comes with sales, contract management or custom processes, the shared data model makes Dynamics 365 cheaper in the long run than two systems and an integration between them. On AI agents (Copilot Studio), see our Copilot Studio article.

Rollout step by step

  1. Analysis: channels, teams and queues, SLAs, permissions, knowledge base owner, existing helpdesk data.
  2. Licensing: Professional, Enterprise or Contact Center – decided by the channels and the need for automatic assignment.
  3. Configuration: queues, routing, SLAs, e-mail synchronization, automatic ticket creation, Teams.
  4. Integration: SMS provider, telephony, customer portal, existing systems; migration of tickets from the old tool.
  5. Testing and training, then go-live and ongoing support.

Power Automate flows and custom apps are built as part of our Power Platform development. For companies in the DACH region we work in German or English as a nearshore partner.

Frequently asked questions

Can Dynamics 365 Customer Service be used as a ticketing system?

Yes. Every request becomes a case, with queues, assignment, SLA deadlines, a knowledge base and a customer portal; tickets can be created from e-mail, the portal, SMS, chat, Teams and phone calls.

How does an e-mail become a ticket?

Server-side synchronization connects the mailbox to Dynamics 365, and an automatic record creation rule creates a case from the e-mail. Replies are matched to the existing case via the headers. The queue address must be in the To or Cc field.

Can we send and receive SMS from a ticket?

Yes: the Dynamics 365 Contact Center SMS channel works with Azure Communication Services, Twilio or Infobip, and your own SMS provider can be connected via an integration. Messages appear on the ticket timeline.

Do chat and phone need a separate licence?

The real-time channels (chat, SMS, phone, Teams as a customer channel) come from Dynamics 365 Contact Center, which has to be licensed alongside Customer Service. Details are in our Customer Service article.

Can Dynamics 365 be an internal IT helpdesk?

Yes: employee requests become cases in the same way, with queues and SLAs. If the company only needs internal IT ticketing, it is worth comparing with a standalone tool as well.

Can tickets be migrated from the old helpdesk?

Yes, through data migration: customers, open and closed tickets, knowledge articles. During the analysis we decide what moves over and what stays in an archive.

Let’s talk about your project.

Tell us what you are planning and we will get back to you within a few days.

Get in touch

Cookie settings

Choose what you consent to. We remember your choice for 6 months; change it any time via “Cookie settings” in the footer.

Privacy notice