IT gets requests by chat, by email and by a tap on the shoulder. Each one arrives without the device, the error or the urgency. I want every request to carry those three facts, so the first reply can be an answer, not a question.
Before the form is open
I pick one place for requests and tell everyone. The link goes into the chat topic, the intranet and the email signature. I also decide what counts as an emergency and give a phone number for it. A form is not a phone call.
While it is open
Staff describe the problem, name the device and say how much it stops them. The exact error box matters most, because the words of an error often lead straight to a fix.
A person's AI can ask: "What is the problem?" Then "Which device is it?" Then "Can you still work?" It shows the answers and sends them only after a yes. See agent-fillable forms.
After the request
I sort the CSV by work impact first and category second. I reply from my own email, and notify_email can send me a notice for each new request. This works as an IT request form for small teams. It does not number tickets or track status.
Broken things in the building belong in a work order request. Outside IT firms can fill in a vendor onboarding form first. More tools are in IT and operations forms.
Questions
Can people see the status of their request?
No. The form only collects requests. It does not number tickets or show status. Reply by email, or pass each request to a ticket tool with a signed webhook.
Why ask for the exact error message?
Search and AI chat tools work best on the real words. The first fix often appears when the message is pasted in, and the box saves IT a round trip.
Can an AI agent send requests for staff?
Yes. A person can hand the form to their own AI. It asks for the missing details, shows the answers and sends only after a yes.