Introduction
Customers often use email when a support request doesn't require an immediate conversation. They can describe an issue, attach supporting information, and respond when convenient. For the service organization, however, receiving a message is only the beginning. The message must enter Dynamics 365 Customer Service, become trackable work, and reach a representative who can act on it.
An email intake flow connects several components. A queue provides the support address and organizes incoming work. Its mailbox uses server-side synchronization to create email activities in Microsoft Dataverse. Automatic record creation can turn those activities into cases, while queues and routing determine where the resulting work goes. Each component has its own configuration and health signals, so an effective design also defines how to validate the complete flow.
Consider an organization that publishes support@contoso.com for customer questions. The functional consultant must decide:
- Which incoming messages Customer Service tracks.
- Whether each message should remain an email work item or create a case.
- How the system handles unknown senders, replies, and messages sent to more than one support address.
- Which queue receives the work and how representatives are assigned.
- How administrators identify the stage at which a message stops processing.
These decisions affect data quality, duplicate cases, representative workload, and the continuity of customer communication.
Follow one email intake flow
This module follows incoming support email from the queue address to assigned work. You examine the relationship among the queue, queue mailbox, email activity, queue item, case, workstream, and routing records. You also compare two supported designs: creating and routing a case from an email, and routing the email activity itself as a record.
The module assumes that you understand Customer Service cases, queues, and the fundamentals of unified routing. It focuses on how those capabilities connect for email intake rather than repeating their detailed configuration.
After completing this module, you can:
- Explain how incoming support email becomes trackable Customer Service work.
- Prepare and validate a queue mailbox for email processing.
- Design automatic case creation behavior for common email scenarios.
- Select between routing cases and routing email records.
- Diagnose failures across synchronization, case creation, queues, and routing.