Laptop loses its charging connection.
Select the recorded device if known. State the office, whether work has stopped, and whether another charger was tried. Attach a clear picture only if it helps explain the connection problem.
Help desk ticket form
Report what happened, where work is affected, and what you already tried. Show device fields for equipment problems and software fields for application issues, without asking employees to diagnose the fault.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Explore with sample data. Adapt fields, views, and workflows for your team.
Two useful reports ask for different details
Expense application rejects an existing approved login.
Name the application, describe the affected task, and provide the non-sensitive error text. Distinguish a broken existing login from a request for new access.
Ask questions that help the next support decision
Summary and description
Use a short symptom in the summary and reproducible context in the description. “Cannot submit expenses after selecting a project” tells the handler more than “System not working.”
Impact and urgency
Ask how many people are affected and whether work can continue. The calculated priority makes those answers useful without asking every requester to choose “urgent.”
Device or application context
Use the appropriate category fields. A device lookup brings its asset identity into the case; a software issue asks for the affected system instead.
Supporting evidence
Collect a screenshot or error message only where it helps. Give requesters a clear privacy instruction and avoid collecting personal or confidential information unnecessarily.
The form is the start of the ticket
A ticket is created
The app generates a ticket number and retains the reported context. The requester does not manually invent an ID or set the final resolution.
Support takes ownership
Assignment rules or triage determine the next handler. The support team records responses, waiting reasons, and resolution through linked updates.
Collect useful evidence without collecting secrets
An error message or a photo of a damaged connector may save a follow-up conversation. Tell employees to remove passwords, access tokens, customer records, and unrelated personal details before attaching a file. Make evidence optional when a description is enough. For urgent interruptions, accept the core report first so the support team can respond, then add further information to the same ticket rather than requesting a second submission.
Using the help desk form
Must employees know the asset tag?
No. The affected-asset selection is optional in the example. Ask for the device context the employee can provide and let support establish the authoritative asset link when necessary.
Should every field be required?
No. Require the information needed for first triage, such as the symptom, category, location, impact, and urgency. Device, software, and evidence fields depend on the problem.
Can employees attach screenshots?
Yes. Explain what is useful and ask them to remove passwords, access tokens, and unrelated personal information first. Attachments should support diagnosis, not replace a clear description.
How is priority determined?
The example uses the affected scope and whether work is blocked. A whole-location stoppage is urgent; a one-person issue where work can continue has lower priority.
Can the requester edit the resolution?
The issue form is for reporting context. Support outcomes are maintained through the handling records and installed permissions, not as an employee-entered resolution choice on intake.
Choose the next step for your team
Make the next support conversation more useful
Open the issue form and adapt the questions to the problems your employees actually report.