Skip to main content
DSE Support Center
DSE Customer Helpdesk

Open a Ticket by Email

Clients can also open a support ticket through the verified production mailbox helpdesk@detection-systems.com.

Email support

Open a Ticket by Email

Clients can also open a support ticket through the verified production mailbox helpdesk@detection-systems.com.

Production address https://helpdesk.dsesecurity.com/

Confirm HTTPS and the exact domain before entering account or ticket information.

Visual walkthrough

Open any visual for a full-size reference

The annotated screenshot uses numbered red boxes and arrows. Read callouts 1, 2, and 3 in order, then return to the written steps below for the complete procedure.

Illustrated DSE email-to-ticket workflow. Open full size
Visual 1 Illustrated production email-to-ticket workflow. All records are fictional.
Illustrated DSE customer support ticket form. Open full size
Visual 2 Related workflow: Illustrated example based on the signed-in production ticket workflow. All records are fictional.
Annotated DSE walkthrough for Open a Ticket by Email with three numbered red callouts, boxes, and arrows. Open full size
Visual 3 Annotated walkthrough: follow red callouts 1 through 3 to confirm context, complete the action, and verify the result. The screenshot is a sanitized training view with fictional records.

Clients can open tickets by email

Email this verified production address to create a support ticket:

1
Workflow section 1 of 5

Send and maintain one email conversation

  1. Address the first message to helpdesk@detection-systems.com and use a subject that states the site or system and symptom.
  2. Send one complete request and keep the confirmation containing the ticket number.
  3. Use Reply in the same email thread without changing the subject so the update stays on the existing ticket.
  4. Start a separate email only when the new request is unrelated to the original ticket.
  5. Never email passwords, one-time codes, private keys, API secrets, or unrelated customer information.
Back to top
2
Workflow section 2 of 5

Verified production support email

Back to top
3
Workflow section 3 of 5

What to include in the email

  1. A clear subject line that summarizes the issue.
  2. Your name, company, site, and best callback number.
  3. The affected system, device, user, camera, door, panel, workstation, or service.
  4. When the issue started and whether it is still happening.
  5. Screenshots, photos, error messages, or timestamps when available.
Back to top
4
Workflow section 4 of 5

What happens next

  1. The helpdesk creates a support ticket from your email.
  2. DSE Support reviews and routes the request.
  3. Replies from DSE will come through the ticket system.
  4. Keep the ticket number from the confirmation email for future updates.
  5. Reply in the same email thread so updates stay on the existing ticket.
Back to top
5
Workflow section 5 of 5

Finish and verify the customer action

  1. Wait for the confirmation page, updated conversation, email, or account message before repeating the action.
  2. Confirm the customer, company, site, DSE-###### ticket, and visible status are the ones you intended.
  3. Save the confirmation or reply on the same ticket when more information is needed.
  4. Contact DSE immediately if account or ticket visibility includes unrelated customer information.
Back to top
Final verification

Before you leave this guide

  1. Confirm context. Recheck the DSE domain, signed-in account, company or site, ticket number, device, and request type shown on screen.
  2. Confirm the result. Perform one harmless verification and make sure the visible status matches what you expected.
  3. Keep the reference. Save the DSE-###### ticket number, confirmation, or other safe reference needed to continue the same conversation.
  4. Stop on a mismatch. Do not repeat a high-impact action. Preserve a safe screenshot, note the time and exact error, refresh once, and update or open the correct DSE ticket.

Content owner: DSE Service Operations. Production reviewed July 16, 2026. Examples and visuals are customer-safe and use fictional data.

Please Wait!

Please wait... it will take a second!