Guides
Dynamics 365 Customer Service case process: see where each case waits
Connect Dynamics 365 Customer Service to Duaer. It reads when each case was opened, first responded to and resolved, so you see where cases wait and for how long.
What does Duaer read?
- Each case is a case: Opened, Responded (when the first response KPI succeeded) and Resolved, with the priority, origin and owner.
- The steps match the service ticket template; canceled cases are left out.
How do you connect it to Duaer?
- Register an application in Microsoft Entra and create a client secret.
- In the Power Platform admin center, add an application user for the organization with this application and a security role that reads cases or opportunities.
- In Duaer, create a Dynamics 365 Dataverse API credential with the organization host (such as acme.crm.dynamics.com), the tenant ID, the client ID and the client secret.
- As an owner or admin, open Data sources, select Add source, choose Dynamics 365 Customer Service under Service ticket, choose the credential, select Check connection and confirm.
How often does it read, and how much?
Each run reads the records changed since the last one; a first read starts two years back and finishes over several runs. A step is never written twice. Read only.
What are the limits?
- The tables, entities and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
Questions
What if no first response SLA is set up?
Cases without a first response KPI get Opened and Resolved only.
In this section
Add a process source in Duaer
A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.
ProcessSee the process in your data and generate workflows in Duaer
Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.
ProcessProcess findings and SOP conformance in Duaer
Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.
Follow-throughServiceNow ticket process: see where each incident and requested item waits
Connect ServiceNow to Duaer. It reads the states each incident or requested item goes through from the audit history, so you see where tickets wait and for how long.
Follow-throughZendesk ticket process: see where each ticket waits
Connect Zendesk to Duaer. It reads when each ticket was opened, first assigned, first replied to, solved and closed, so you see where tickets wait and for how long.