Keep the conversation beside the customer record
A support agent opens a customer case and finds a saved email that explains an earlier decision. The message is there, but reading it means downloading a file, switching applications, and then returning to the case.
An embedded preview gives that saved correspondence a place inside the CRM. Doconut Viewer SDK provides document viewing for .NET applications, including email formats, so developers can add a message preview to the screen where the work already happens.
If you use OnlineDocumentViewer.com to inspect individual files, the SDK is the next step to explore when you want viewing inside your own product. This article focuses on a CRM integration for archived email files.
Start with MSG and EML attachments
Doconut's supported file catalog includes MSG and EML email files. That makes them useful candidates for a first preview workflow: a saved message attached to a contact, an opportunity, or a support ticket.
Keep the scope clear in the interface. A saved-message preview helps someone read an existing file. Mailbox synchronization, sending replies, and matching messages to customer records are separate application features.
Consider a warranty case with a customer's original request and a later clarification. The CRM can keep both files attached to the case and let the agent open each one beside the case history. The agent can then return to the same record without having to locate the attachment again.
Design a small, complete preview flow
Start with one place in the CRM where archived messages already appear:
- List the saved messages using recognizable filenames and the customer or case context.
- Let the user select a message to open in an embedded preview.
- Keep the case name and a clear return action visible around the viewer.
- Show a useful message if the file cannot be opened, with a way to return to the attachment list.
The CRM should resolve which stored file belongs to the selected record and whether the current user can access it. Doconut supplies the viewing component; your application supplies the relationship between the message, the customer, and the person opening it.
Decide separately how the CRM will present files attached to a saved email. Include that path in your evaluation if users need it, rather than treating a readable message body as proof that the whole case workflow is complete.
Pay attention to email-specific rendering
Archived messages can vary in encoding, layout, and how they reference images. Doconut's format configuration reference documents email settings for message, subject, and body encoding, date time-zone presentation, and rendering quality.
It also provides an option to skip remotely referenced images. Decide how that setting should fit your application's handling of external email content, then test the result with representative messages.
These choices deserve attention early. A message that opens successfully still needs to display its subject and body legibly, and the dates shown should make sense in the CRM's surrounding timeline.
Evaluate with a realistic set of messages
Use approved sample files that reflect the correspondence your team receives. A compact evaluation set might include:
| Sample | What to inspect |
|---|---|
| A short plain-text message | Readability and the basic open-and-return flow. |
| An HTML message with a table | Layout at the actual preview-panel width. |
| A message containing accented characters | Subject and body encoding. |
| A message referencing external images | Behavior under your chosen image policy. |
| A longer saved conversation | Navigation and the ability to keep case context. |
Check the preview inside the actual CRM layout. A wide standalone viewer can look comfortable while the same message feels cramped beside a customer summary.
Measure loading behavior with your expected files and infrastructure. Keep access rules for source files and rendered output aligned with the CRM's permissions.
Bring email preview into your product
A useful first release can be modest: one attachment list, one embedded message preview, and a reliable return to the customer record. That gives your team a concrete workflow to assess before adding more document types.
Explore Doconut Viewer SDK for the available integration options, then visit the Doconut download page to begin an evaluation with your MSG and EML samples. The goal is to make saved correspondence easier to use where customer decisions are already being made.