Projects, quotes, invoices, purchase references, and agreements
Summary: Business requests move faster when the ticket identifies the company, site, project or reference number, requested outcome, deadline, contact, and approval context.
AudienceDSE customers and authorized contacts
Procedure3 guided sections
Checklist8 specific actions
ReviewedJuly 16, 2026
Visual walkthrough4 visual references for this procedure
01Identify the request
- Company, site, project or job name, and customer contact.
- Quote, invoice, purchase order, agreement, ticket, or other reference number.
- Whether the request is a new estimate, revision, approval, status question, billing question, renewal, or closeout item.
- Required date and the business event driving that date.
02Attach supporting material carefully
- Attach the relevant approved scope, marked-up drawing, purchase reference, or invoice page when authorized.
- Identify the exact line, quantity, site, or date in question.
- Remove payment-card, bank-account, tax-identifier, employee, and unrelated customer information.
- Do not treat a ticket reply as contract approval unless the authorized DSE process says it is sufficient.
03Keep technical and commercial work clear
A service outage and a quote or billing question may need separate tickets because they have different owners and priorities. Reference the related ticket numbers so DSE can connect the context without mixing the workstreams.
Need a person?
Contact DSE Support →
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.