A short service request can still contain enough detail to help the right person respond. At a public counter, the difference between 'the network is down' and a clear description of the affected task can change where troubleshooting begins.
Describe the work that stopped
Include the location, the application or device involved, the time the issue was noticed, and whether other staff can still complete the same task. Explain what the person expected and what happened instead. Do not paste passwords, sensitive records, or unnecessary personal information into the ticket. Follow the organization's approved channel for any supporting material that needs restricted handling.
Make the next action visible
Add a contact who is available to help reproduce the issue and note any public-service deadline. The service team should acknowledge the report and make ownership clear, especially when more than one provider may be involved. If a workaround exists, record its limits so the requester knows whether normal work can continue or requires supervision. Close the request with a description the reporting employee can understand.
Practical takeaway
Use a simple request form with room for context. Better starting information helps staff investigate without making the public-facing employee become a technical specialist.