Skip to main content

Request progress

Ticket Status, Ownership, and Timing

Production tickets use Open, Resolved, Closed, Archived, and Deleted statuses. Replies, assignment, scheduling, and dependencies provide the rest of the workflow context.

On this guide
  1. Customer-relevant statuses
  2. Response and completion timing
  3. Finish and verify the customer action
Browse all guides →
1

Customer-relevant statuses

  1. Open means the request is active and may be in triage, assigned work, scheduling, vendor work, parts, approval, or waiting for information.
  2. Resolved means DSE has recorded a resolution or completed the requested work, subject to any remaining confirmation or closeout.
  3. Closed means the support conversation and administrative closeout are complete.
  4. Archived and Deleted are administrative retention states and normally do not represent active work.
Back to top ↑
2

Response and completion timing

  1. DSE confirms the applicable department, priority, schedule, SLA plan, agreement, and business impact during triage.
  2. A response target is not the same as a completion estimate.
  3. Parts, site access, customer approvals, vendors, project scope, and scheduling can change completion timing.
  4. State any deadline and business impact on the ticket and ask DSE to confirm the plan.
  5. Do not rely on a generic help article as a contractual service commitment.
Back to top ↑
3

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 ↑

Visual references

Open any image to see it full size. Annotated images use numbered callouts to guide you.

Illustrated DSE ticket lifecycle and timing workflow.Open full size ↗
Visual 1Illustrated production ticket lifecycle. All records are fictional.
Illustrated DSE My Requests ticket list.Open full size ↗
Visual 2Related workflow: Illustrated signed-in customer example. All names and ticket records are fictional.
Annotated DSE walkthrough for Ticket Status, Ownership, and Timing with three numbered red callouts, boxes, and arrows.Open full size ↗
Visual 3Annotated 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.
Before you finish
  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. Reviewed July 16, 2026. Examples and visuals use fictional data.

Please Wait!

Please wait... it will take a second!