--- title: "What to Include in a Support Request?" slug: "what-to-include-in-a-support-request" description: "Details what to include when writing a ticket to help resolve it." tags: ["Customer Support", "Support Tickets", "Zendesk"] status: "update" updated: 2026-11-16T16:06:07Z published: 2026-11-16T16:06:07Z canonical: "ims-handbook.cenosco.com/what-to-include-in-a-support-request" --- > ## Documentation Index > Fetch the complete documentation index at: https://ims-handbook.cenosco.com/llms.txt > Use this file to discover all available pages before exploring further. # What to Include in a Support Request? A complete ticket gets resolved faster. Please remember to include the following when you submit a request. ## For every ticket - One issue per ticket. If you have two unrelated problems, submit two tickets. - A clear summary and description of the issue. - Steps to reproduce it and what you expected to happen instead. - Screenshots or a screen recording showing the issue. See [Taking Screenshots](/v414/docs/taking-screenshots) or [Screen Recording](/v414/docs/screen-video-of-issue). - The names of any affected assets: FLOC, Equipment, Schedule, or CML/TML. See [Providing Scope to Support](/v414/docs/providing-scope). - Your criticality: how urgent this is for you. Support sets the ticket’s priority separately, based on impact on scope. See [Ticket Priority and Response Times](/v414/docs/get-support). ## By ticket type | Support / Question | Bug | Feature request | | --- | --- | --- | | Relevant import/export/source files | Relevant import/export/source files | Clear description of what should be added and where | | Description of the expected result | Detailed steps to reproduce | Explanation of the purpose | | Screenshots supporting the description | Description of the expected result | Summary of the value this would bring | | | Screenshots or a recording showing the expected result is not happening | | > [!NOTE] > Note > > Missing a file or screenshot? Reply to your ticket with it or send us an email at [support@cenosco.com](mailto:support@cenosco.com) Functional Location