Skip to main content
Tickets, Replies, and Notifications

Use email notifications without losing ticket history

2 minute read Updated 2 months ago Customer-safe guidance

Use email notifications without losing ticket history

Summary: Ticket email is a notification and conversation path. Keep the DSE ticket number in the subject and reply within the same thread so updates remain attached to the correct request.

AudienceDSE customers and authorized contacts
Procedure3 guided sections
Checklist13 specific actions
ReviewedJuly 16, 2026
Visual walkthrough4 visual references for this procedure
Illustrated DSE email ticket workflow.
Illustrated production email-to-ticket workflow; all records are fictional.
Numbered step path for Use email notifications without losing ticket history.
Mobile-readable step map matching the guided sections in this article.
Verification and closeout guide for Use email notifications without losing ticket history.
Mobile-readable verification, escalation, and handoff checkpoints for this procedure.
Annotated DSE walkthrough for Use email notifications without losing ticket history with three numbered red callouts.
Sanitized, production-faithful walkthrough. Follow the numbered red boxes and arrows to confirm context, complete the action, and verify the result.
01Recognize a ticket message
  • The message identifies the DSE Support Center and normally includes a ticket number or ticket context.
  • Confirmation messages acknowledge ticket creation; later messages may contain technician replies, status notices, or access links.
  • Check spam and quarantine when an expected notice is missing.
  • Verify the sender and destination before opening a link or attachment.
02Reply safely
  • Use Reply rather than composing a new unrelated message.
  • Keep the ticket identifier and existing subject intact.
  • Remove unrelated recipients and old sensitive content before sending.
  • Answer the technician questions and describe any new impact or test result.
  • Confirm the reply appears in the portal conversation when the update is important.
03Avoid duplicate tickets
  • Do not send the same issue repeatedly to several support addresses.
  • Do not start a second email thread because the first response is pending.
  • Use a new ticket only for an unrelated issue or when DSE instructs you to do so.
  • Reference related ticket numbers when two issues affect the same site or event.

Content owner: DSE Service Operations · Production review: July 16, 2026

Need a person?

Open a service request with the details you have.

Include the site, affected device or user, exact error, when it started, urgency, and screenshots when available.

Contact DSE Support →
Continue learning

More guidance from the same support category.

3 min read Open a new support ticket

Summary: Sign in with a verified client account, choose the closest public help topic, and submit one complete request ...

 2 min read Check ticket status and reply to DSE

Summary: Use the email-and-ticket-number status tool or sign in to review an authorized request, read DSE updates, and ...

 2 min read Choose the right help topic and describe business impact

Summary: Choose the closest topic shown on the production form and describe impact factually. DSE confirms department, ...

 2 min read Add contacts, collaborators, and ticket notices

Summary: Use the requester and collaborator controls to include only people who are authorized and need to participate ...

Please Wait!

Please wait... it will take a second!